From: Michal Suchanek Date: 2010-10-05T17:42:09+09:00 Subject: Re: how can we make a ruby compiler On 5 October 2010 07:10, Clifford Heath wrote: > Tony Arcieri wrote: >> >> ... FOR SPEED! For example, you're a company on the >> scale of Facebook who has written a large web site in a dynamic language >> and >> suddenly realize you could be saving a lot of money on servers if your app >> ran a lot faster. Source translation to C++ is a potential way to go > > And in all the world, there are how many companies that have a > web site that large (in traffic)? Maybe not even one other. > And they could afford to rewrite the site in whatever language > they chose, instead of relying on a dodgey translator to give > them an unreadable result. > > I can't believe how many people use the old "but what if we > become as large as Facebook?" argument to drive their technology > choices. Like the number of places using NoSQLs to produce sites > that are even less reliable than they used to... The lack of reliability is not caused by using a less traditional database but by programming errors either in the site itself or the tools it uses. Some databases not associated with NoSQL such as MySQL tend to be very unreliable. Using new and experimental technology is not always a good idea but using old and known broken technology is never so and many people do that anyway. Thanks Michal