By “user” I mean the person who is using the application.
Using exceptions for handling unexceptional errors (like invalid user input) is a footgun. You don’t know when one might be raised, nor what type it will have, so you can easily forget to catch it and handle it properly, and then your app crashes.
A string being parsed as a date-time is presumably user input, which is potentially invalid.
Printers these days tend to be driverless, so that’s pretty much a solved problem.
And back at that time if you installed any flavor of Linux you were lucky if the OS install didn’t fuck itself over
I was using Linux religiously back then, and this is false. As long as there’s a driver for all of your hardware, it generally worked fine.
But that “as long as” is doing some heavy lifting. The usual suspects were pretty much the same as now: Broadcom, NeoMagic, and NVIDIA. Some cheap printers and modems were problematic as well, but if you paid for good hardware, it would probably work.
The wireless kind, presumably. Those always need their own firmware and therefore their own driver.
What happens when you coerce a string to a date-and-time but it’s not valid?
Where I’m from (Rust), error handling is very strict and very explicit, and that’s how it should be. It forces you to properly handle everything that can potentially go wrong, instead of just crashing and looking like a fool.
Since when did Bethesda have QA?
If you can’t afford Starfield, how can you afford a computer capable of running it?
Dynamic typing is insane. You have to keep track of the type of absolutely everything, in your head. It’s like the assembly of type systems, except it makes your program slower instead of faster.
Difficult to test == poorly designed
It’s pretty much a natural law that GUIs are hard to thoroughly test.
I take it you don’t already have a desktop you can use?
Windows is malware.
Why not use a full-size computer for all that stuff?
Wait, that’s illegal.
Apple and Microsoft support aren’t exactly awesome, either, unless you’re a big business with deep pockets. At least with Linux, the system is open, so if there is a way to solve my problem, someone has almost certainly found it already and added it to Arch Wiki or Stack Overflow or something.
This. You can’t remember the safe word because there isn’t one.
In America, the disobedient prole gets tossed in the slammer and forced to do hard labor.
Because web development sucks, web developers are always trying to reinvent web development such that it doesn’t suck, and they keep failing.
They keep failing because it’s impossible, and it’s impossible because the requirements are directly contradictory.
And they keep failing because, quite frankly, they don’t know how to succeed. Most web developers are not grizzled 50-year-olds with decades of experience and a solid understanding of things like type systems and build automation, and most grizzled 50-year-olds with decades of experience and a solid understanding of things like type systems and build automation want nothing to do with web development. Microsoft somehow managed to scrape together enough exceptional individuals to create TypeScript, but they seem to have exhausted the supply of such individuals.
Most web developers don’t even seem to fully appreciate what TypeScript does and why it’s important, let alone have the skill to write similarly sophisticated tools themselves. Consider, for example, Vite not running TypeScript type checking with every build. Vite’s developers cite compilation speed as their motivation for cutting this corner. These people clearly do not understand the importance of correctness checking.
Another example: as far as I can tell, no web application build tools track dependencies between source files for incremental compilation, nor am I aware of any standard format for compilers (TypeScript, Sass, Babel, etc) to communicate that information to the build tools invoking them (Webpack, Vite, Grunt, etc).
Every once in a while there’s a ray of hope, like TypeScript, but that’s all it is: hope. The web developer experience has never been anywhere close to the caliber of developer experience you’ll get with a language like Rust, and sadly I don’t foresee that changing any time soon.
And no, htmx is not the answer to our prayers. It seeks to fix HTML, and HTML is not what’s fundamentally broken.
The patient’s skeleton was missing, and the doctor was never heard from again.
Printers should probably be connected by USB for security reasons anyway.