4 ms·
So what should we have used? Rails? Just that little matter of it not being so invented yet. Given that we knew C++, and were smart enough to build with reuse i
by gaius 13y ago
So what should we have used? Rails? Just that little matter of it not being so invented yet. Given that we knew C++, and were smart enough to build with reuse in mind, and needed far, far fewer $40,000 servers (and the REAL cost, co-lo space), it wasn't just reasonable, it was genius!
Speaking of genius, that leads me neatly onto: are things really cheaper? I am thinking of this story, even in '99 I'd have balked at $20k/mo in hosting charges alone http://www.theregister.co.uk/2013/02/15/heroku_marketing_misstep_draws_customer_anger/ http://www.theregister.co.uk/2013/02/15/heroku_marketing_mis...
- 3pt14159 13y agoASP pre dot net is what you should have used. It was perfect for web apps and way faster to develop in than C. I am 100% serious. I worked at a startup back then (one of the few that survived) and that was what we used.