Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Developers were more in tune with the entire tech stack down to silicone. Today you’d be “unreasonable” for asking such a thing.


The entire stack down to silicon exploded multiplied by 3 or 4 in that time.

Vectorization, more cache levels, branch prediction, multiple cores and processors, gpu, virtual machines, (operating systems, but they didn't change much, I only let the placeholder for the layer), containers, but all that in the cloud, distributed databases, frameworks written in a language that need to be compiled to a language that is actually implemented by a web browser in the client (we are far better on compatibility between browsers, but much libraries or practices keep stuck in the past).

I haven't touched shift in practices that make it far worse.

That make it more unreasonable.


I am not asking, it will be the only way from now on if companies don't want to waste more money and time.

Because the option to parse stack traces from the programming language itself, it will destroy what ever built on or for microservices


Yeah because back then the tech stack was:

php apache mysql linux

it was so small we could put it into an acronym.

Meanwhile in 2024 you could barely begin to even describe any individual layer of the stack with so few words. You'd be out of breath before even beginning to finish describing React.

(btw it's silicon, not silicone).


Good ole PAML stack :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: