---------
Here’s a list of changes and additions that I certainly never needed (or wanted): Ruby 1.9 hash literals Refinements %i literals Rational/Complex literals (2/3r, 2+1i) Endless ranges (1..) Safe navigation operator (&.)
156 karma · joined March 19, 2017
---------
Here’s a list of changes and additions that I certainly never needed (or wanted): Ruby 1.9 hash literals Refinements %i literals Rational/Complex literals (2/3r, 2+1i) Endless ranges (1..) Safe navigation operator (&.)
My laptop is always ssh-ed (mosh provides the "always" aspect) into one of the others anyway. It's stuck with 8GB of RAM which is often a bottleneck, especially since Docker holds onto a couple gigs and Chrome tries its hardest to get the rest. Portability is necessary but not sufficient to addrrss my computing needs.
What I find invaluable is the super quick ramp-up after context switching, especially if whatever pulled me away turned out to be more work/time than expected.
I don't think it's necessarily readability holding me back from Haskell, but I do find Clojure to be highly readable which really helped me get up to speed with it quickly. I'm curious what you find more readable about Haskell.
In P6, 1..10 is exactly the range you'd expect, while ^ is used to exclude either end of the range. For example, 1..^11 is the same as 1..10, as is 0^..^11 (can't say I've ever needed that, but I could see a couple of possible uses).
This also carries over into range syntactic sugar. ^10 is shorthand for 0..^10, and as a result ^@list.elems is a list of valid indices of a list.
I personally find Rust's syntax noisier, but it's a small issue.
My solution to that issue is "just" alternate bindings which obsolete both the standard and vi navigation keys. At the home row, I have the arrow keys on my right hand and a "nav cluster" of my own devising (page up/down, tab left/right, workspace left/right) on the left.
Definitely not for everyone, but a possible way to have your cake and eat it too.
I use a 48 key keyboard (an OLKB Planck) which massively cuts down on hand travel and typing strain. Arrow and navigation keys, a numpad, all the function keys, every symbol I use whem programming, and various OS controls (volume, media controls, screen brightness, etc.) are all easily reachable without changing the position of my hands. I also chose to program all the modifier keys to work both as normal when held down and in a similar fashion to sticky keys when just tapped. For example, holding down shift and typing a letter works as normal, but hitting shift followed by a letter accomplishes the same result, meaning that capital letters and punctuation don't really interrupt the flow of typing or require chording.
I also have rather resistive keyswitches (nominally 185g, ~170g in actuality) which was of ergonomic benefit to me. I wouldn't expect it to help most people, but it helped me learn to type without bottoming out the switches. Starting out, the heavier springs caught me before reaching the bottom. Now I type in a much gentler fashion, even if peak force is greater than on a standard keyboard.
Moving down to 48 keys can seem intimidating, but I adjusted rather quickly. It only took me about a couple weeks to become comfortable with the layout changes (staggered keys to a grid layout and Workman instead of QWERTY). I believe that part of the reason it was such an easy transition was because I changed the layout whenever I had trouble adjusting to it. I had wanted to place the underscore on the same key as F in a QWERTY layout to make typing snake_case identifiers easier, but kept hitting the adjacent equals key instead. I could have pushed through it, but I embraced what my brain clearly felt was right whenever a similar thing happened and picked up the layout much quicker than I expected.
Another common concern is losing competence with a normal keyboard or standard layout, but at least in my case that hasn't been an issue. I can switch back and forth between a 2013 Macbook QWERTY keyboard and my customized one with no issues, and I often switch from QWERTY to Workman on my laptop depending on how much I'm writing. Occasionally I'll switch layouts mid-sentence when I realize I'll be going into more depth than I expected.
>DHKE was one of the first public-key protocols, which allows two parties to exchange data securely, so that is someone sniffs the communication between the parties, the information exchanged can be revealed.
I don't think that information being revealed through passive observation is a selling point of DHKE.
My old school district has one middle school and one high school, and pushed out the one of the best teachers I've ever had. That said, an organic chemistry class was offered, thanks entirely to the efforts of another great teacher.
I never had any real choices in my grades 6-12 education so, to me, being in a position to choose a school with a curriculum catering to one's interests and talents does seem to be a privilege many people take for granted.
Embedding vim-style editing in an IDE or less extensible editor might get you 90% of what you want from Vim, but that 10% can be a dealbreaker depending on your workflow. Without easy extensibility, you might not be able to get that last 10% at all.
I'd say evil starts out a little better, maybe 95% out of the box, but now you have all the power of emacs to make up that last 5% and then start to go even further if you're not content then.
This loses the important nuance that them swooping in and slapping a price tag on their own use of the implementation doesn't deprive anyone of access to the original on the same terms they were able to access it.
No one has lost anything in this scenario.
>The problem with this is that it disincentivizes the sharing mentality.
Personally, I feel arguing over how people make use of freely shared knowledge does more harm a culture of sharing than usage of said knowledge, even when that usage pushes right up to the bounds of what is allowed under whichever license.
† The google feed seems to have a consistent lag upon switching to it from the home screen (double tap on the multitasking button is normal) that the animations hide. It loads somewhere around 150ms slower than most applications, even taking longer than the first launch for unused apps.
I know, right? This 'evil' thing is going places.
Come to think of it, I don't think autocorrect would catch this anyway.
I recently rolled my own (verg tiny and specific) build/deployment system for a project. Initial prototyping was a breeze, but once I had things more or less nailed down, I started adding types and, for example, was able to leverage the type system to make sure it can only be deployed listening on IP addresses in the private range. The next step is to rig up some sort of Zerotier integration to ensure I only make it available on my private networks.