> Point #2 is very weak, because the alternative to slow sites is spending time optimizing them which may waste human time.
Ehhh the easiest way to get fast sites is combining a fast language and framework. There's like 3 orders of magnitude difference in performance between something like Django and Vert.x
I've seen code slow enough (PHP, 10 req/second) that running enough capacity consumed like 15% of the engineering budget. That could have easily been .1%.
Since developers dont care about hosting cost most of the time, they keep using horrifically inefficient frameworks. I rarely see super slow code because people get called out in code reviews for doing really stupid stuff. It's always the slowness of frameworks that's been a problem IMO.
Not everyone agrees with that. A lot of people think the efficiency of writing code in favorite language X makes up for the added hosting cost. I just don't believe it with how many choices are available now. Maybe that was true 5-10 years ago. Now we have a good 5 languages with maybe 40 frameworks that run less than 3x slower than C. That's really really fast. Enough that you could run anything under top 500 sites with a single machine.
Static CDN hosted react/angular SPA with a speedy backend can serve a stupid amount of traffic even on AWS free tier.
As an Enterprise SEO with over 15 years experience I don't really give any F&%!'s about your favourite language
What I need is something that is faster than the competition, is properly built to minimise usage of our crawl budget and is flexible enough to add new content quickly can properly handle site migrations can implement hreflang for say a dozen locales.
Reasonable requirements. Scary to think the majority of developers don't know anything about performance. The majority I talk to don't even know what http2 is!
Super popular REST libraries like Flask, Django, and Rails don't even support it!!
That's why choosing the right language and framework is super important from the beginning. It's easy to choose something slow as mollases and get left in the dust with constant performance problems
Ehhh the easiest way to get fast sites is combining a fast language and framework. There's like 3 orders of magnitude difference in performance between something like Django and Vert.x
I've seen code slow enough (PHP, 10 req/second) that running enough capacity consumed like 15% of the engineering budget. That could have easily been .1%.
Since developers dont care about hosting cost most of the time, they keep using horrifically inefficient frameworks. I rarely see super slow code because people get called out in code reviews for doing really stupid stuff. It's always the slowness of frameworks that's been a problem IMO.