Precisely, it’s bad architecture not a bad language.

You can make bad architectures in any language you like!

The only truly bad language is JavaScript. ;-)

Is it a breeze to work with and seamlessly supports SSR, isomorphic code, and type safe library and data sharing, because it uses the same language on the client and server, and does it inspire joy and delight because it's fun and easy to work with like SvelteKit? Since not, then why bother with PHP? Because the alternatives are so much better.

In no way is PHP better than JavaScript, and the simple fact that JS runs natively in both the front and back end is astronomically more important than a point-by-point comparison of language features that PHP loses anyway.

https://x.com/Rich_Harris/status/1844744999272935596

Rich Harris @Rich_Harris:

A few takeaways from this remarkable data:

1. Yes, SSR matters. SvelteKit users sometimes get frustrated that it's too SSR-centric, and we have plans to address that in the next major version. But SSR is the default for a reason! Our ultimate responsibility is to end users

Ben McCann @BenjaminMcCann:

Some data from Google (big thank you to @rick_viscomi and @imkevdev !)

Client-side-only SPAs are extremely detrimental to latency as they add a network round-trip before rendering begins.

You can win at LCP by making it harder to build client-side apps