6 ms·
I think the ironic thing about Spolsky's example is that, in the end, it worked. It eventually gave birth to Firefox. So I think there are many lessons to be le
by hn_throwaway_99 7y ago
I think the ironic thing about Spolsky's example is that, in the end, it worked. It eventually gave birth to Firefox. So I think there are many lessons to be learned about how to do a rewrite, how to message it, how to do it in a way that it doesn't stop other forward progress. But if a rewrite fails, that doesn't necessarily mean that not doing a rewrite would have been any more successful in the end, and that's the trap I think people fall into.
- regularfry 7y agoDoing the rewrite definitely tanked the company. That's a fairly low bar that "not doing a rewrite" has to get over to be a better option.
- paulryanrogers 7y agoMicrosoft giving away IE for free probably had more to do with Netacape's downfall than the rewrite alone.
- regularfry 7y agoBeing unable to respond won't have helped.
- goto11 7y agoHow many people actually paid for the Netscape browser in the first place? Was selling the browser ever a viable business model? Netscape could have developed different ways of getting money, like ads on the start page or default search engine. But such schemes could only have worked if they had retained a large market share, which they jeopardized with the rewrite.
- hinkley 7y agoI was always a little irritated to see a boxed copy of Netscape in stores, but it did solve the 'how do I get my initial web browser?' problem for people who had no idea what "FTP" is. So I'd say that for the majority of people (the 90% who were not tech people), they bought it once. Once they got later in the adoption cycle that would have dropped off, and the moment IE shipped that would immediately trend to zero. Netscape was free because Mosaic was free, and Mosaic was free because of the National Science Foundation. (As for getting your initial browser, IIRC you could send away for copy of Mosaic on 2 floppies for the cost of shipping and media, but that could take weeks)
- LanceH 7y agoI think ISP's probably did more for distributing browsers at the time.
- andyjpb 7y agoThe Netscape business model was largely about selling their FastTrack Sever (for "eCommerce") and per-seat browser licensing to for-profits. They had a reputation for giving away betas and pre-release copies on their FTP servers.
- goto11 7y agoJoels article was written in 2000 and Firefox 1.0 was eventually released in November 2004. In the meantime they lost almost all their market share. They eventually won some of it back, but this was probably only because Microsoft had stopped all development of IE and disbanded the IE team. Usually you can't count on you competitors stopping all development for half a decade. Obviously you can rewrite from scratch and end up with a fine product, since the original version of the was developed from scratch. The question is if you can accept losing all customers and wasting years of effort.
- btilly 7y agoThere is still more to the story though. When Netscape went under and open sourced their code, they had to rip out all of the proprietary bits. The result? What they had didn't actually run! It wasn't a question of rewriting working code. It was a question about whether the better path forward was to try to fix what they had and didn't understand, or whether to rewrite into something that they understood. In other words, Joel set up a straw man argument.
- goto11 7y agoThey could just rewrite the components which they didn't own, then. They would have to do that anyway. I'm not sure what you mean with "didn't understand". It was their own code. They could just read it.
- oldandtired 7y agoTo write "It was their own code. They could just read it." misses a great deal about code bases. The first and foremost is that the vast majority of working code bases do NOT have sufficient internal documentation to actually understand whys and wherefores of that code base. The specific reasoning for doing something or using a specific technique or why the magic numbers, etc., are often not put into any form of accessible documentation. This is just a fact of life. Documenting such things can be very tedious and often thought of as not being needed because the code is "obvious". Yet to someone coming in to do work on it in six months let alone six years, it is vital missing information. {Edits spelling mistakes - should have checked before submitting}
- hinkley 7y agoI think this is the siren song of putting a clever architectural decision front-and-center in the code. "Everything is an X." What happens when it turns out not everything should be an X, or worse, X ends up being harmful? How do you refactor such a system when the biggest mistake is pervasive? [Edit: I have done it 2-3 times, but I'm not entirely sure I could adequately explain how I did it, which means I should still be asking that question.]
- deleted 7y ago[deleted]