brnewd

I think this has more to do with the kind of software you write in JavaScript than something inherent to the language or ecosystem. Often JS is used to write web related stuff targeting the browser or other api's which have a fast pace of change. Versus a system level utility in GO that can go untouched for years on end.

I think it's mostly personal preference. I don't like significant whitespace, the type system, overall language ergonomics. It just doesn't fit my mental model. My point was more, if you have to use a language you don't like, you will end up with complaints as given by the OP, eg: "JS sucks".

I think your issue is having to use a language/runtime you're not productive/happy in. I switched from PHP to Node.js of my own choosing and loved TypeScript everywhere and a Java like runtime vs a state less execution model. I found the npm ecosysteem much richer and accessible than Packagist / Composer. However if I was forced to write in Python, I would have similar complaints.

I use a stepper while working on my laptop, outdoor in the garden. When trigging a compilation/build I do a couple of situps or pushups. Standing up while working keeps me active and alert. I get more work done sitting down, but love the outdoor sessions better, especially for work that doesn't require extensive typing.

I would love to swap Pulumi for Ansible, but it's cloud-only for the most part.

I'm still firmly in the Bootstrap camp. It's boring, well understood by the average website visitor. Allows for rapid development and thereby time to market. I tried Tailwind once, but found the added complexity not worth the trouble. I guess it all hinges on the type of project(s) and runway.

I think many love the promise of a distributed database, but in practice there is a real speed and feature set compromise to make.

Every now and then you get these horror stories. Is it time to round robin between multiple PSP's? I switched to daily payouts to prevent accumulation at the PSP level.

I paste in the url bar and copy again as clear text.

If you use high level abstractions like authjs, you better use the happy path or it becomes a time sink. I think for authentication and authorization, use single purpose, well established libraries like bcrypt and passport.js and write the glue logic yourself. Sign up flow and authentication are too important to make concessions on.

I use Node.js/TypeScript for all my scripting needs. Together with pm2 which can auto-generate a systemd service if it needs to run as a service on boot. Coming back to a strongly typed project / script is actually really beneficial to refactor or extend.