Sure having a modern infrastructure that is able to process thousands of requests per second is better than something that can only do a few hundred, but if you strip out a bunch of excess requests, you will process less per user, and thus reach the same level of scale on a less efficient stack.
The most important part is people paying you money.
Modern startup culture is full of inefficiencies + silly trappings (nice offices, drive to hire people, make things more complex, take more money from investors to stave off figuring out taking money from customers)
An entire app can be build in a single js file (with only one dependency... and it's 150 or so dependencies and sub dependencies).
It's noteworthy when tech projects are successful and simple, because in the industry there is a widespread tendency to try and replicate what "the big guys" are doing, and often times what they're doing is extremely convoluted.
In other words, it is significant when projects buck this trend, because it goes against the mistaken belief that the only way to be "web scale" to replicate some of the most complicated tech stacks out there, making it worth calling out. Significant being a synonym for noteworthy in case that needs to be clarified...
HN being an example of this doesn't somehow make every other example not noteworthy either if that was what you tried to say?
-
This concept has come up so many times I am, again, surprised anyone who is in the same tech industry as me does not realize it's a thing:
https://blog.bradfieldcs.com/you-are-not-google-84912cf44afb...
https://programmerfriend.com/not-google/
https://link.springer.com/chapter/10.1007%2F978-3-030-31646-...
Especially on Hacker News, a place where an immense amount of gnashing of teeth has happened over what the latest complicated tech stack that people convince themselves they need to make software that scales.
But to the point specifically, " It’s not surprising to find successful projects run with a simple stack." - you are spot on. The "successful" HN crowd appears to favour overengineering or obscure tools, point which shows 90% are armchair philosophers who daydream of running a business, building a 0 to 1 start-up, and other things office workers imagine when they think building a webapp using GO, or Haskell will result in anything else but a line on a CV for yet another slave away job (potentially an open source project that no one wants too).
Not very representative of the entire real world of development.