eltimablo

There’s also the added CPU overhead from using JavaScript for everything to contend with.

I disagree. I think it’s often mistaken for derision when in reality it’s a request for a better description of the use case.

In my world we prioritize one. And that not the one.

Then I’m really glad I don’t live in that world.

If you can’t see that writing readable code is part of the means to that end, I don’t know what to tell you. If nobody can maintain the codebase because it’s a mess of spaghetti logic and 20-deep dependency trees (I’m looking at you, every JavaScript project I’ve ever seen), the end product is going to suffer while also making every single engineer working on it want to leave.

This is not a controversial take in professional software development.

Funny, it sure seems like “maintainability should not be a priority” is a pretty controversial take to me.

What an utterly blind, self-centered view. Write good, readable code so you can actually maintain it and so your coworkers don’t want to kill you.