One of our clients codebase, once almost completely PHP, now officially contains more JS than PHP code. I don't know if we should celebrate or cry.

celebrate while crying

@Ubbe it is frontend, we still use PHP in the backend exclusively

@AleCx04 Or cry while celebrating.

tears of joy. LMAO

Just remember to sacrifice 4 gigs of RAM every month to Brendan's shrine.

@lamka02sk than it really depends if the JS is bloat or things that are better suited in backend but moved to front-end anyway. Yeah than cry.

If it's a well designed webapp (and yes I mean application at heart not let's make everything SPA) than a really consistent API like JSON:API or GraphQL and even well crafted REST API can reduce a lot of back-end complexity and turn it into a safe high performance database

Instead of crafting the highly dynamic UI server side I see the advantage of doing a lot of it client side and JS being a larger code base. Cheers!

The thing is though that you see those projects always do everything client side. So pages or parts that are not really part of the app like marketing, contact, terms are all JSified. This makes it unnecessarily hard on the client.

Def cry

@hjk101 all JS is bloat by definition

@mundo03 how so?

I would cry in that case.