3 ms·
Unless the blog author builds software that never crashes -- even when it get millions of hits on its first day, then he should cut them some slack. I'll put mo
by smoody 18y ago
Unless the blog author builds software that never crashes -- even when it get millions of hits on its first day, then he should cut them some slack. I'll put money on the fact that Google didn't have the same kind of traffic on their first day that Cuil did. And Google has had 10 years to get it write. Yet he expects perfection on the first day.
- d0mine 18y agos/get it write/get it right/
- AndyKelley 18y agoyou forgot a semicolon
- d0mine 18y agoI am appreciating the joke. $ echo get it write | perl -pe"s/write/right/" get it right The semicolon is not required.
- jrrl 18y agoThe blog author was one of the founders of Lycos (read: search engine long before Google) and was pretty involved in keeping it alive under stress (albeit 1990s stress, not 2000s stress).
- blogimus 18y agoToday was the first day I heard of Cuil. I don't think it is as much of a matter of writing software that never crashes, but rather a matter of protecting your site from crashing on the launch. I'm interested in their reasoning for going with a "grand opening" and subjecting the site being hammered instead of inviting groups of early adopters/beta testers and incrementally stress testing the system.
- unalone 18y agoThat's because Google lived in an era where there weren't a bunch of asshole flunkies writing about tech startups. They created a product that spread via word-of-mouth, not through press releases. People that used Google liked it, and it spread. If you launch under the pretense of being a possible Google killer - and the people making this certainly did nothing to stifle that outrageous claim - then you need to expect a ton of flack when something goes wrong. And things went wrong.