Comment Re:We only use JS now? (Score 4, Insightful) 294
...and the server is just used for database work.
And that mentality is precisely why so many web applications suck farts off dead chickens for performance and scalability.
The first step to designing a scalable application is designing a scalable and flexible database model. The database is not an "afterthought", it is the heart of an application.
The code which accesses the database can be tweaked and fiddled, but once you've created your database, it becomes very expensive to change it in the future because of the costs of changing not just the code, but creating and testing database migration scripts to move the data to a new model.
But you go pat yourself on the head that you're a 'leet programmer because you know a scripting language.
And then hang your head in shame when you realize that JS runs in the browser and is only a presentation layer, not the application itself. Only a fool puts the business logic in the client if they have any understanding or concern for transaction consistency and application reliability. You have to assume the presentation client is going to break half way through processing something and leave the database in an inconsistent state if you put the business logic in the front end.