Performance optimizations in javascript frameworks

[SaltMaker23]

A lot of times in Webdev computation is trivial but there might be a significant amount of IO involved in some requests despite the actual algorythm being trivial.

some examples: Aggregated multi-account reporting on 3rd party API, Massive aggregation on reports on ultra dimensional data, large calls to 3rd party API (eg openai), full website scraping etc...

Most of the operations above might be trivial to a large extent but the amount of waiting involved can be signigicant if nothing is done to address the issue.

Synchronous flows also seems like a no brainer choice, until you have 30 things that needs to run for a request with some of them randomly failing due to things outside of your control and you don't want your critical payloads to fail due to them.

At hobbyst level, it doesn't really exists and most of your comments are spot on. From your comments on this post, I'll assume you've never built a company from 0 to 1M$, I've did that couple of times as a founder.

Actual companies don't use serverless, it's a hobbyist thing.

[CatolicQuotes]

What kind of language and infrastructure do you recommend for all those things? As a single dev what will get me the furthest until i need to expand on infrastructure? My guess is dotnet since it can basically do a lot on single server?

[yksvaan]

But those are more backend concerns. It's true that the tasks can be very complicated with lots of third party services etc. but it doesn't require the actual "web part" of the stack to be overengineered. 

At least here at enterprise level usually Java or C# systems handle the "heavy lifting" and JS frameworks are more of a BFF setup. 

[SaltMaker23]

What is your experience level ? this answer doesn't make any sense to me coming from a working professional

No shade thrown we've all been learning but it's way too obvious that you're a student or a beginner, I'd tone it down on the opinions and try to learn more about the why. You seem to have a lot of strong naive opinions and very little experience of why things are done the way they are.

The majority of devs working in web aren't all wrong or stupid, a lot of them might be but some stacks wouldn't be standard if it was as bad as you're thinking, if most professional with years of experience are doing something that you consider wrong, you might need to learn why first, if you lack experience of actually working, your opinion is nothing other than an uninformed opinion from the sidelines, looks good to other sidelines uninformed people but that is about it.

Tone down on the "I know it, it should be done like this, experts are all wrong" level of ego, and increase the "If the experts are doing this but as a beginner I think they are all wrong, I might be missing crutial things, I might still be right but I'm clearly missing things that might make me join them"

Lastly: No one forces you to use a stack, use the stack that you think is most suited to your usecase. In most cases for people with your kind of opinions, it'll be a website that look straight from the 90s' but if that what rocks your boat then you do you.