It’s not just a shitty disease…. It’s a shitty disease that the Social Security Administration really, REALLY does not like to pay out disability for. Mostly because, unless something has changed recently, it’s hard to prove that you actually have it because it defies easily quantifiable medical testing, among other things.
So, it would be a curse on multiple levels!
Source: I used to be an attorney who fought for people who had been denied benefits.
Almost everything the author complains about has nothing to do with JS. The author is complaining about corporate, SaaS, ad-driven web design. It just so happens that web browsers run JavaScript.
In an alternate universe, where web browsers were designed to use Python, all of these same problems would exist.
But no, it’s fun to bag on JS because it has some quirks (as if no other languages do…), so people will use the word in the title of their article as nerd clickbait. Honestly, it gets a little old after a while.
Personally, I think JS and TS are great. JS isn’t perfect, but I’ve written in 5 programming languages professionally, at this point, and I haven’t used one that is.
I write a lot of back end services and web servers in Node.js (and Express) and it’s a great experience.
So… yeah, the modern web kind of sucks. But it’s not really the fault of JS as a language.
Honestly, even with VSCode, devcontainers are kind of just ok, at best.
They are very fiddly. The containers keep running when you close VSCode (which makes sense, and sure the resource usage is minimal, but it’s damned annoying) and you have to stop them manually. Meanwhile the commands in VSCode to work with/activate the containers are not super clear in terms of what they actually do.
Oh, what’s that? Need a shell inside the container you’re working in for testing things out, installing dependencies, etc.? Well, I hope you pick the right one of VSCode’s crappy built in terminals! Because if you want to use a real terminal, you are stuck with the crappy devcontainer CLI to exec into the container. A CLI that is NOT up to date with, or even includes, all the commands for devcontainers in the editor (which is what makes working with them in other IDE/editors such a pain in the butt…).
And this gets me…. What? A container I can share with other developers, sure, but it’s very likely NOT the container we are actually going to deploy in. So…
Yeah, I’ve also had a lot of frustrations with devcontainers in Bluefin. I really like what the Bluefin project is doing. The reasoning behind it makes a lot of sense to me. But devcontainers are kind of pushed as the way you “should” be writing code on Bluefin and it’s…. not great.
They do have Homebrew and Distrobox though, which helps a lot. I have ended up doing most of my development work on Bluefin on the host system with tools installed via brew, which is kept separate enough from the rest of the file system to still keep things tidy.
Overall, I think Bluefin is great and it, or something like it, may very well be the future of Linux… but the future isn’t here just yet and there are some growing pains, for sure.
Isn’t test driven development also error driven development though?