4 ms·
It's interesting that the needs of the business don't seem to factor into his analysis at all. I'll concede that sometimes there are specific cases on which yo
by otterley 16y ago
It's interesting that the needs of the business don't seem to factor into his analysis at all.
I'll concede that sometimes there are specific cases on which you need to use a new or non-mainstream language or environment. (I'm 99% certain that this business is not one of those cases.) I'll concede, too, that being on the cutting edge is pretty cool and gets you lots of hacker cred.
But if you want your business to survive the departure of the founding team, you need to consider whether you can solve the problem with a mainstream environment. If you don't, don't expect your invention (at least in its current form) to carry any legacy.
Case in point:
People may think Paul Graham is a fucking genius for selling Viaweb to Yahoo!, despite being written in Lisp, but I assure you none of his code still lives on there, not even a fork. His brilliance is as a businessman for getting Yahoo! to fork over $<lots> to him, not for the technical merits of Viaweb itself.
- eftpotrm 16y agoYahoo bought Viaweb 13 years ago. The challenges then were completely different to what they are now, as were the underlying technologies at all levels. Frankly Viaweb could've been written in the most widely used, predictable technology ever seen and I'd still expect it to have been rewritten in the last 13 years.
- otterley 16y agoSure, most things are rewritten or replaced in the very long term. But Viaweb's code didn't even last a few years.
- gridspy 16y agoYes, but it seems lately that Yahoo is where good startups go to die. Viaweb was purchased because it was successful. According to PG, it was successful because they could implement major features in a weekend.
- otterley 16y ago... and you missed the whole point of my argument. That the original author can major features quickly does not necessarily imply that an ongoing concern after the departure of the original author will also be able to implement major features quickly. Choosing your environment with your successors in mind usually increases the value of your business (assuming, of course, that your valuation has a rational basis, which tech companies aren't always good at determining).
- gridspy 16y agoYour company isn't going to be worth much if it fails to execute and falls behind your competitors. If using Java makes you 10% slower, but your code is more maintainable by Yahoo - Yahoo will buy your competitor who won market share with their superior features and quick response to customers. NB: Choose Java because it is "enterprisy"
- rayiner 16y agoYou missed the point of his argument. Consider the Crash Bandicoot folks. Sure after Naughty Dog got bought, Sony couldn't figure out how to deal with the Lisp codebase and future projects were in C++. But Lisp let them build the first major platform game on the PSX, beating Sony itself to the market, and none of the stuff afterwards would've happened without that.
- eftpotrm 16y agoSmall companies are inherently fragile though; new small companies even more so. By all means keep an eye on the future to watch for possibly tying your hands, but if that is what it takes to get you the customer base to survive, let alone build market share, RIGHT NOW then the sane business decision is to optimise for survival and do the short-term thing. Sort the long-term problem when you can and it's a real win, not because you might benefit later if you make it that far. Steve Jobs had it right on this: artists ship.
- anamax 16y ago> His brilliance is as a businessman for getting Yahoo! to fork over $<huge> to him, not for the technical merits of ViaWeb itself. You forget that he had something to sell. He explains why his choice of lisp helped him with that detail.
- chris_j 16y agoWould you mind expanding on this? All of the responses to this comment so far seem to focus on the last paragraph and Viaweb in particular, which I would guess is not the main part of your argument. You say: "...if you want your business to survive the departure of the founding team, you need to consider whether you can solve the problem with a mainstream environment." Could you go into more detail about what you mean by a mainstream environment and what advantages it would bring in this case?
- otterley 16y agoWith most startups, the (usually very small) team or individual who develops the original implementation doesn't stick around once the business has achieved some level of success; they typically cash in and leave. But if the business is going to continue to operate, the new development team needs to be capable of tending to the product, as it will need bug fixes, security patches, and perhaps be updated to scale better. If the product is built on an uncommon platform, finding new developers, especially senior ones, to tend to the product will be difficult and expensive. If a sufficient number of qualified developers cannot be found, the business may have little choice but to rebuild the product using a more mainstream technology. In the meantime, the business takes on a higher risk of continued operation if the current implementation (which is no longer maintainable) is surpassed by its competitors. TL;DR: short-term optimizations create technical debt, which screws your business in the long run.
- chris_j 16y agoThanks for expanding. It sounds like the main problem with non-mainstream languages is the difficulty of recruiting developers who know the language well enough (rather than some technical quality of a language like Clojure that makes code hard to maintain) . That is a pretty uncontroversial statement and is probably very true. The pool of Clojure developers is probably quite small at the present moment in time. Would you regard the use of a non-mainstream language to be, in of itself, technical debt?
- otterley 16y ago