No one bothers because everyone loves their fast-as-a-snail framework in their favorite slow scripting language and they need massive infrastructure to scale it to serve less than 1k concurrent users.
Programmers have no one to blame but themselves.
However, Ultimately development teams make do with the skillset they have and saved development time is saved money. Who cares of the toolset, Most programmers forget about the business objectives ultimately. Instagram's backend was originally Django, they managed just fine for a long time. Using C++ is pretty overkill even for a simple API project and potentially a huge waste of developer time, people seem to forget developer time is expensive.
The numbers were from skimming TechEmpower's benchmarks. I don't have a horse in the race as I don't do (much) web dev but I found the disparity amusing even if the reality isn't quite so bleak due to, as you mentioned, many other factors before you even hit the application itself.
Ultimately I agree with you, I'd rather see someone use a framework they're comfortable with if it makes their life easier - but I won't lie to them and pretend it's optimal.
If I'm working on one of those products, prioritizing requests per second over any other factor is bad engineering, period. That's not to say that I wouldn't end up choosing a mature compiled language in the end, but there are plenty of reasons why I might not, and you have no right to judge without knowing my constraints.
One code base, one language, cross compilation, native binaries, static linking.
If we're ever in a position to rewrite it I'll be pushing hard for Rails or Django with simple server rendered HTML. Anything less would be doing us and our internal customers a disservice in terms of how quickly we can deliver features.
> https://alexcabal.com/posts/standard-ebooks-and-classic-web-...
> This is the web I want and love.
Worth noting that according to their article, Standard EBooks does not use javascript on their page. This might work for them, and it might work for you, but in many cases users want SPAs and interactivity (Google Maps, Google Docs, etc)
Most SPAs are anything but reliable. If you talk to most non programmers, they hate computers and software and think pretty much all software sucks.
Sure, maps and docs are not possible without client side programming, but most websites are actually not maps nor docs.
Expanding on this, I had a Dell XPS 9550 running Linux until the M1 Macbook came out. The XPS was a pretty powerful machine when I first bought it, but as always happens, hardware requirements for software increased while my hardware stayed static.
And the software whose requirements increased: websites, and specifically SPA's. It was absolutely noticeable visiting many (but not all) SPA's, with Jira being the worst offender, just how slow those websites are. It doesn't have to be much slower to just grind at you, and for you to want to finish and leave that site as quickly as possible.
Now I have a much faster desktop with a 5950x processor, and a Macbook Air M1 for when I'm moving around. I don't notice the website slowness anymore (except on reddit perhaps), and it isn't really an issue for me anymore. But I'm a software developer among other things, and I spend a lot of time on computers, so I get good hardware. We who are developers are likely an exception to the general population who will be experiencing the web as I did on my XPS, or perhaps even worse.
I hear that so much, except they don't. Most sites aren't Figma.
What we're seeing is the proliferation of apps that have been traditionally just desktop apps, but being made for the web. We have to distinguish the web as an app delivery tool (Google Docs, Figma) vs what most developers are writing. CRUD apps. And for those you can ask the server for state often.
Very thin abstractions over HTML, CSS, JavaScript and Node.js that don't separate you from what you're trying to ship to the browser: HTML, CSS, and JavaScript. No "magic" or "hacks," just a bit of plumbing to make you more productive.
Architecture is just a matter of organization. Ease with basic organization is what separates experts from laymen in any field.
Have to say, I think that's somewhat oversimplifying. Architecture is a lot more than organization. It's also a broad and deep understanding of external and internal resources, the creative design process, corporate vision, industry insight, risk analysis, project management, stakeholder politics, marketing, and technology.
It's very possible to be super organized but still end up with a discombobulated frankenstein of a project, or one that's under water on time or budget, or a design that's too niche and misses the market.
A software architect seems to be a dirty word in some parts, but it’s really just someone who has deep knowledge of various tools, services, etc, and are able to aptly design a system to serve the businesses needs without under/over-architecting.
I’m glad that I’m living in a much faster and simpler world, but I fear, for end users and developers alike, that it is an ever shrinking one.
I really can’t understand the appeal of what, to my eyes, amount to endless layers of needless complexity.
I wish articles such as this one were more common:
https://alexcabal.com/posts/standard-ebooks-and-classic-web-...
This is the web I want and love.