"serverless" framework web shitters have sacrificed the following: -reproducibility (locked into specific software with specific packages, and specific tools) -security (everything is done client-side, in an uncontrolled environment that can send back literally anything) -speed (Modules that call modules that call functions that create a div with a white border, all client-side, mind you) -database normalization (they seem to enjoy repeating data and having empty items, just for the joy of sending json strings instead of proper queries) -code readability & debugging (a language that needs be written in another language atop a framework's functions, good luck debugging that) -falsely named RESTful APIs (they don't even know that rest is short for REpresentational State Transfer, yes they do transfer data, but does that transfer by itself represent state? usually not.) -stability (this whole pile of nonsense often fails to work propperly, sometimes even on the same machine, because of all the above)and what for? what did they gain? some additional words on their resume? what a pity."but muh magic auto-scaling", they cry. Scale your costumerbase first, fools.
>>102411007clients can always send back anything you retardthey can even skip the client and just hit your server with arbitrary requests
>>102411007> blindly using one format (giant JSON blob, with HTML embedded, HTML has HTML-encoded entities, JSON blob has javascript functions)