77 karma · joined April 16, 2017
http://freedomcontroller.comI am 50/50 VIM / EMacs so the it's important for my control key to be on the home row.
I'm not sure why keyboards even have caps lock. It's rude in chat right :-) I started with Sun keyboards where control was on the home row. I guess if one spends hours typing long capitalized acronyms daily, then it makes sense.
It's personal preference in the end. I certainly wont buy another MBP - my 2016 has had 4 trips to the Apple store since I bought it for key replacements.
Also an interesting aircraft.
I wish Apple would get on with it and include Terminal.App and the FreeBSD user land and Xcode for iOS so we can start running a shell and doing interesting things with this new hardware :-)
I had to look that up.
I always look up to the fixed width font model used by IETF RFCs. They are extremely readable and searchable and last for a long time.
CAPSLOCK -> CTRL LEFT CTRL -> ESC
It's not great, but it works. The last time I had to deal with a company who put the ESC key in a weird place was back in college where we have several of these HP Apollo/720 keyboards:
https://alum.wpi.edu/~tfraser/Machines/hpapollo720.jpg
:-)
No thanks. Plus the keyboard will likely have the same issues my 2016 version has. I’ve had keys replaced 4 times already.
According to Wikipedia (https://en.wikipedia.org/wiki/United_States_military_veteran...), in 2012 there were 6,500 which seems like enough to get a slice in a pie chart.
For the record, I've eaten butter camping in the winter - long lasting dense energy source for sure :-) My favorite is Kerry Gold Irish unsalted :-)
Google doesn't take human phone calls so why should anyone else have to? And as good workers, efficiency and productivity should trump any expression of humanity we might have left in this end game of automation :-)
Is the hardenedbsd web site's security feature comparison table up to date?
Edited to remove comment about my confusion that Carolinacon14 -> 2014; not the case. It's 2018.
It's not surprising that after we made fat the demon, the supply change replaced fat with with sugar (at least in yogurts) and type 2 diabetes is now rampant.
:-)
I really appreciate the mindset that Dr. H and friends have brought to both SQLite and Fossil - that is - minimal and efficient code with very low dependencies.
I first came across fossil-scm when I was looking for a simple way to host some development repos for a small group; it is so much easier with the integrated cli/server than what I found with git. Also, I love the ease of setting up replication and the he single file format.
Keep up the good work, glad to see there is some focus on the next generation!
I'd like to second the feature request mentioned elsewhere in this thread about having some for of access control on sub-trees or files within a fossil project - but - maybe that could be accomplished by simply doing a separate project / vendor tree type pattern IDK.
Given that these attention grabbers are now weaponized, it's good to fight back; I think we benefit from periods of boredom and deep thought.
:-)