3 ms·
Would you not agree that the web is becoming more "real time". People demand webapps to update as they view them - ajax,comet,getNextBuzzword(). Those demands p
by axod 17y ago
Would you not agree that the web is becoming more "real time". People demand webapps to update as they view them - ajax,comet,getNextBuzzword(). Those demands place a higher load on servers, especially when you scale to large number of users.
- swombat 17y agoFor sure, but 99% of apps never scale to "large numbers of users". And when they do, they usually have the time to figure out how to do so without downtime. Often, that may involve rewriting part or all of the backend in a lower level language. If that's needed, so be it - but to do it before you have any performance problems is just premature optimisation.
- axod 17y ago>> "99% of apps never scale to "large numbers of users". " Maybe because they don't get past the scaling issues ;)
- fauigerzigerk 17y agoJudging by the number of blog posts, articles and books about scaling this or that Ruby/Python/PHP framework, people seem to be very busy with "premature" optimisation right from the start, exactly _because_ those frameworks and languages are so horribly inefficient. Why would I want to run and manage and design for a server cluster just because each and every Rails process needs to load the entire language runtime, the framework and all the libraries using 100MB of RAM for no application functionality at all? Not doing all that work is premature optimisation?