I've always found it weird when a form admonishes you for writing spaces or dashes in e.g. a phone number or credit card number. Hey, implementation, you're a computer! Strip them out automatically on the backend if you don't like them!
Great point. It is simply lame impatient clout-chasing when someone goes out and promotes their project that is approximately as new to them as it is to the people they're promoting it to.
Talking of heavy-handed confirmation dialogs, there's a good example of this in Apple's Preview.app (PDF viewer). They made an unconfigurable change a few years ago, such that every single time you click any web link in a PDF, you have to confirm with a dialog that you want to open the link. You used to be able to just click links!
I'm sceptical of the idea that the majority of programmers are already having LLMs write the code. It reminds me of the general idea some years back among the programmer chattering classes that everyone is surely doing some level of unit-testing, whereas in the real world there were tons and tons of teams that did zero unit-testing ever.
IMHO the persistence of Model M (now Unicomp) worship is a meme. Yes a chunky Buckling Spring mechanism is a very unique and "fun" feel, but that doesn't mean it's actually good to do a lot of typing on in terms of ergonomics or speed. So what of it? It's a novelty item, not the ultimate keyboard.
I remember these guys from the glory days of the CrankyGeeks video podcast. John C. Dvorak and Sebastian Rupley had a great double-act hosting that show.
Even the later JavaFX was a tasteless exercise. I opened some apps and you could tell within 1 second that something was wrong because all the text was using fugly non-platform-native (or somehow screwed up) text rendering.
> Any body who saw a Perl programmer do over a weekend, what they would take a year to do in their language(especially Java and Python)- had a deep rooted seething envy at Perl and Perl programmers. So they went around almost on religious crusade to have Perl gone. This was done entirely to crush competition. They just didn't want other people to wield a power they didn't have. Lisp has had a similar arc of development over the decades.
Isn't that the fate of the archetypical loser? To end up on the sidelines thinking "I'm actually the smartest and most powerful, the wider world just isn't capable of appreciating it".
I saw someone recently say something like... they wished contemporary Lisp people put anywhere near as much effort into creating lots of great software with Lisp as they do extolling Lisp.
The tapestry of share buttons were certainly novel and interesting like 20 years ago. They may be lame and 99+% ignored now but it's been a slide to this state of affairs.
IIRC it seemed like that pilot was having some kind of nervous breakdown because he surreptitiously held back on the stick all the way from 38,000ft until the crash.
It's got to be somewhat depressing working on a household name product in its trashy downturn. Surely you can't have the pride in your work that an equivalent employee once would have.
I wonder about the timing in relation to the OpenAI acquisition of Astral this week. Was it a two-horse race to be acquired and then Deno got word that they were not the chosen one, and so said oh well, mass layoff it is?
BTW the Deno architects would contend that "mastering Deno" could never be a waste of time, because what you're mastering is to a large extent standards-based JS (in comparison to the APIs that came before).
Yeah, that's pretty much tailor-made to be the official resource for an experienced programmer to get an overview of C++ as it stands. Fairly slim book so it's approachable.