Meanwhile PHP quietly runs 80% of the internet by being used for WordPress.

“There are only two kinds of languages: the ones people complain about and the ones nobody uses.”

Always remember, the silicon valley ethos of “break things” wasn’t about their applications, it was about breaking industry, society, laws and your ability to oversee or regulate them.

the tests are now larger than the thing itself

Is such a weird complaint. You should aim for your codebase to be as small, simple and readable as possible, while your tests should be a specification that guarantees behavior is consistent between refactors. When you add behavior, you add tests, when you remove a behavior, you delete tests.

The size of either is independent of eachother. Small code bases that provide lots of features should be simple to read, but with a lot of tests.

Like a fungus you learn to live with

Apparently every code base I’ve ever worked on was run through this.

I never saw that, that’s legitimately funny. I’d love to be in the room when that feature was designed, and the reaction of the developer it was handed too.

I don’t know if the game is the best example of busineses making top-down design decisions, since that game was an obvious scam from the start.

Remember when people were calling this dummy the “real life Tony Stark”? Lol.

Yes, I couldn’t recommend htmx highly enough.

Web & mobile development took a wrong tern 10 million miles back, and no one wants to turn the car around and admit it.

Yes, and the people directly contributing to the project have legitimate gripes. Although, the parable of dhh is if you get on an asshole scorpions back, don’t be surprised if you get stung. Dudes been an unreasonable prick for nearly 20 years now.

My comments directed at the manufactured outrage from the tooling zealots incapable of having a mature conversation. Or even accept a difference of opinion. The number of comments that start with, "never heard of Turbo, but let me weigh in on why you’re an idiot for not liking Typescript. " is very telling…

I continue to be baffled and amused by the complete meltdown of the typescript community over the actions of a single man on a single package. The only people who have legitimate gripes are those that had been actively contributing and whose work was erased. The rest of you are acting absurdly childish. The anger and vitriol being thrown at anyone who disagrees on how to write javascript would make me embarrassed if I was associated or involved in the ts community.

Javascript.

Because my exposure to Typescript is wading through over-engineered and bloated Angular front ends that could easily (and should) be thrown out and re-written in html/ js.

But also because I exclusively write simple shit that doesn’t have a build step for the front end, because 90% of the stuff I make gains no benefit from needlessly overly complex front ends.

Oh wow, aren’t you a cranky bitch. I didn’t say you "should " do anything, I linked a tool I’ve constantly been told good things about.

I bet you’re the type to follow the docker install instructions*, arent you?

You know what they say about when you assume, you turn out to be an ignorant dipshit.

Win-debloat

I was there for the first wave of SPAs, I even learned angularJs and Knockout. It did feel like a major atep forward, being able to make highly interactive applications. However, things quickly went off the rails when the tools stopped being about managing heavy client state, and became the default for everything, even when it ment using JavaScript to build extremely basic functionally browsers did natively with html, but extremely worse(e.g. navigation). The modern Web really is a victim of hype and trends.

Unless your app needs to work offline, or you have to manage dozens of constantly changing client side data points concurrently, your site doesn’t need to be a big heavy js framework. My rule is if it looks like Google Maps, you need a SPA. if it looks like Gmail you need REST/HATEOS. and if it looks like google’s mainpage, you need a server side rendering.

At some point you might see the light, and go back to making your websites simpler, but Im not hopeful. Until then I’m building the majority of things with HTMX and alpineJs.

You couldn’t pay me enough dollars to cover the therapy caused by having to maintain the “flexible” code that added complexity and abstraction for a single use case that was never expanded to handle more.

Not testing is crazy. Once you realize you can actually refactor without ever having the fear you’ve broken something, there’s actually opportunity to make rapid improvments in structure and performance. Taking 2 minutes to write the test can save your hours of debugging. Unless you’re building a throwaway prototype, not unit testing is always the wrong choice.