566 karma · joined July 2, 2017
SVN -> Git -> jj
Would prefer to use Kotlin or Clojure.
Using bookmarks would not fit here, because I have no intention to access the tabs in future (e.g. a year from now) again.
In the end vertical tabs are nice and I hope I like the new tab groups too (the previous official tab group addon got killed by Mozilla and 'destroyed' my workflows at the time).
Let's see, maybe Mozilla is on the path to something great yet again by being more innovative.
https://package.elm-lang.org/packages/mdgriffith/elm-ui/late...
Fixing CSS would be nice.
"How to replace a string in Gerbil Scheme?"
... and when done, please port SQLite too :)
What I really want is a GUI that works like a command-line, but with rich media and mouse support. Instead of 100% key input I would sometimes like to click and add/remove/filter data.
The terminal is so useful, still it's strange we tolerate up to this day all it's shortcomings.
Right now hundreds of thousands American Tesla owners are in their one month free trial FSD month and drive around with it on all kind of streets and weather conditions. There is no one else beside Tesla that is capable of doing this (no, not even Waymo).
Watch a Tesla FSD 12.3.4 video, then one of Mercedes and see for yourself.
I'm not so sure that this would work. The goal of your employer is to keep you working.
If the workforce participates to much, you could run into the Tesla problem, a.k.a. your early employees become millionaires and stop working (in case of Tesla because of company stocks).
Depends on the type of work you do. In my last job almost all communication was remote via video call (except a meeting with the CEO every two weeks). Commuting just to sit in front of a computer to talk to others made no sense -> I lost way too many hours of my life to driving needlessly around.
I'm all for meeting in person, if there is a clear benefit. Otherwise it's like with all the other bullshit, stop doing it!
http get https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.zip | gunzip | from csv | sort-by USD | first | get Date
I tried a lot of shells and that's what I ended up with.
Every time some feature is added, it's like putting some weights into the backpack of >>every<< developer that will interact with that part of the system in future. Some actions add more, others less, but you have to be careful. Too much weights will slow down the team/company to a point where no meaningful work can be done anymore. To reach a goal you have to add tech debt, but some feature add way more than others. Ideally tech debt is accumulated in isolated areas that do not interfere with other parts of the system.
So many buzzwords in one sentence