329 karma · joined June 5, 2014
[ my public key: https://keybase.io/sukima; my proof: https://keybase.io/sukima/sigs/p_xMUMbEohTq3s3PJJfqHVAdVw_1U8gdMnM-9eYaYQ0 ]
But I am the only developer in a team of >100 who does.
Well, people hate graphical interfaces - not only do they LOOK scary, they give weird unhelpful error messages and… you have to click everything with a tiny pointer like you are fishing in muddy waters. Ugh.
I really liked the idea that a JS class could represent a custom element. But the need to know when something should be rendered or not and knowing what to update was always a large ask and the reason VirtualDOM like libs were made. In this case I leveraged the ideas of tracking changes by means of tracked proxies which result in memoized function calls. Thus a Component can be split into two simple responsibilities: DOM update code and noting when something tracked is changed.
The big win here is that VanillaJS can leverage the idea of auto-tracking in that only one tracked thing needs decorating and any call stack that touches that one thing will be auto-recomputed when needed.
Much of the complaints about checkout have been split to other commands in newer versions. Does this make Git still invalid in your opinion?
How is this different than web pages or GUI apps? Everyone is different and a button that does one thing in one app/page does something different in another.
Have you tried to read GUI help files? They are written for 5 year olds and provide nothing you need as a dedicated user. Have you had to inspect the DOM of a website to try and intuit what something does it does not do?
Least with command line apps usually you have a --help or man page.
This lead me to wonder (and unsuccessfully answer via google-fu): What is the difference between [jison](https://zaa.ch/jison/docs/) and [nearley](https://nearley.js.org) and when would I use one over the other?
It is created using TiddlyWiki
Fun fact no one has ever actually scanned the code... ever! Maybe if I was a cafe but not for house guests.
An amazing amount research on vit-d collected into a digestible web site.
[1]: https://www.iclever.com/products/BK05-Tri-Folding-Bluetooth-... [2]: http://www.blink.sh/
Oh wait, I just described CSRF!! Zoom, here is your egg. Now promptly smash it on your face; thank you.
However my vim set up maps jk, kj, jj, and kk to Esc to in reality it is safe to just mash those two keys and one of the maps will work.
I am curious what scenarios the designers of the plan drove then to not trust that the human in the seat really has no idea what they are doing. Was the ignoring the wishes of the pilot and attempt to prevent a crazed irresponsible and unlicensed idiot from doing something? These are trained humans why does the computer totally ignore there efforts?
Jk for the win!!! (Also jj works well to).
I also set my mapleader to <Space> you would be surprised how useful that is. Not to mention , (comma) is a valid and useful vi movement key.
To what extent does analog encoding fall under the illegal threshold?
I once felt it was weird till I dove in and looked at the underlying data model. Then It struck me and all the awkwardness evaporated and the commands actually make sense to me now.
I love that this straw-man argument pops up in every thread I read about editing text or IDE debate.
As someone who leverages SSH in their average work day I can explain my personal reasons. Let me be clear; this is likely not the way you work but it is how I work. I am not defending the merits of this for you but that they warrant my approval. If any debate is to be made in this it is that all users have a choice and those who prefer SSH should have every right to use it irregardless of any unemphatic assertions to the contrary.
I have a Linux desktop that has two very nice and pretty monitors. Given a choice I would wish my development to take place on that machine. However, the development I do is on a work computer that happens to be a small Mac Laptop (I don't get to choose the hardware I must develop on). Of all the different methods to edit files I found that SSH into the laptop from the Linux box to be the most efficient and eloquent solution while still keeping the work information on the work computer. I edit in Vim. I test with the browser running on the Mac. I can clearly see and manipulate the source on the pretty monitor while seeing the results on the little LCD screen.
Pairing like this is a huge win. Instead of Forcing a pair partner to wait for me to Alt-Tab the right screen they can connect via SSH (tmate.io) and on their end have their terminal on one monitor and the Zoom / screen share on the other. This way they can edit or watch and see the result without any ask to Alt-Tab. I can read the code while they look at the result. It is truly asynchronous code-pairing.
I remember back in the VRML/SecondLife heyday where you could pick an avatar that was another gender. I still do that. But the emphasis for voice chat in modern games and MMORPGs make it far more difficult. A low gruff voice does not bode well coming from a feminine avatar. Catches too many off guard.