| |||||||||||||
Remote desktop vs. remote displayRemote desktop vs. remote displayPosted Feb 15, 2013 10:22 UTC (Fri) by dlang (✭ supporter ✭, #313)In reply to: Remote desktop vs. remote display by khim Parent article: LCA: The ways of Wayland
If you start cutting features because "99% of the users don't need that feature", you will very quickly get to a system that has no users.
I've seen businesses do exactly this. One company had a 3 year development effort to re-write their entire codebase, along the way they had a couple dozen decisions to cut features that only 1-2% of the corporate clients they had used. The end result (which got announced with great fanfare) was a version that only 30 out of their 2000 customers could use because of the missing features.
(Log in to post comments)
Remote desktop vs. remote display Posted Feb 15, 2013 10:49 UTC (Fri) by khim (subscriber, #9252) [Link] If you start cutting features because "99% of the users don't need that feature", you will very quickly get to a system that has no users. Sure. No doubt about it. But if you'll not implement features which are needed by 99% of users because they break this oh-so-important 1% of then you'll get there much, much, MUCH faster. And this is, in fact, what happened with Linux. Do you know that bestselling laptop on Amazon right now, today is Linux-based laptop? Go and check, if you want. What? What do you mean "it's not Linux"? It sure is. It just culled some features not useful by 99% of users (such as the ability to run compiler locally) and added some features useful for 99% of users (such as the ability to watch netflix), that's all.
|
|||||||||||||