Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "unfinished projects"
-
Who’s better at releasing unfinished/half baked projects that are eventually killed in the span of 5 years or less?
In this corner, weighing in at 264 killed projects, undefeated in search engine industry - Google!
And, in this corner, weighing in at 73 killed projects, the murdered of Nokia, Windows RT and soon to (probably) be Surface Duo and Windows 11 on ARM - Microsoft!
I personally think it’s Microsoft - when they do, they kill it in a spectacular way.9 -
Do you want to know why all the popular open source projects have less-than-optimal, sometimes really dirty code?
It's because their developers ditched all the unnecessary stuff to just get the damn thing done. When I choose an open source dependency, I don't need unfinished stuff. I need a stuff that works and has all the features I need from the very start. If it works, I don't care about code quality in my deps.
This is the reason why dirty, rushed stuff with a great idea behind it gains popularity. PHP, Git, jQuery, the list is quite large.
While you've been busy polishing your files hierarchy, these guys already shipped their product, gained adoption, and their userbase doesn't need your product anymore.
This is applicable only for true open source, not "it's developed by a full-time team of principal developers and the CTO is fucking Kent Beck, it costs $1m per month but yea we have it on github".3