4 ms·
Another year, another chance for all involved to learn the important rationality skill of recognizing sunk costs and opportunity costs, and give up when giving
by cousin_it 9y ago
Another year, another chance for all involved to learn the important rationality skill of recognizing sunk costs and opportunity costs, and give up when giving up is the best option.
http://lesswrong.com/lw/gx/just_lose_hope_already/ http://lesswrong.com/lw/gx/just_lose_hope_already/
- melling 9y agoPerl 6 was announced in the year 2000. 18 years is a long time. It should be a case study for software developers. I don’t know if they should give up. Haven’t looked at Perl 6 in about 5 years. The best thing the community could do would be to turn the language into the solution to a particular problem: Web development, machine learning, etc Sure, anyone could build everything from scratch, but that’s usually not a good idea.
- rwmj 9y agoWhy? Open source developers can work on whatever they want.
- hinkley 9y agoI went to OScon in something like 2009 or 10 and someone working on the python interpreter they were gonna share with Perl got on stage and showed how the roadmap and their velocity wouldn’t have Perl 6 done until 2016. This kind of crazy has been identified in the ecosystem for a while.
- perlgeek 9y agoIf Perl 6 were a centrally managed and funded effort to create a popular language, I would a agree that the one who funds it would look at adoption numbers and time spent, and declare it sunk cost, and try to achieve their objectives through other means. But everybody who's working on Perl 6 does it because they enjoy it, learn by doing it etc. Why should they declare it a failure? Usage numbers are slowly, slowly creeping up, and working with and on Perl 6 can be real fun. If I'd work on it regardless on how much of my previous time I invested in it, why should I even consider sunk costs?