This is the central issue. I can agree with many things, many things are true, even things that are obviously contradictory in many aspects.
But change by itself means nothing... absolutely nothing... if you don't identify correctly the root problems of your woes.
And most of the root problems of the Linux world, IMHO, is NOT in the code. Why this and that!?.. well, is it correctly identified ?... than what are the solutions ? ... and most pertinent of all, why can't everybody push in the SAME DIRECTION to solve the most afflicting woes ?
That is the correct approach IMHO... change per se, can only mean change to nowhere, or for worst...
Example; what are the REAL correct reasons for UEFI ? ... what are the solutions ? ... just for the sake of argument as i pointed elsewhere, what will happen if something like UEFI 2 happens (exclusive encrypt hardware) ?
the rest can be like chichens without head, that go in circles before drop to the side...
Posted Mar 9, 2013 20:00 UTC (Sat) by Wol (guest, #4433)
[Link]
And what if that's the WRONG DIRECTION?
That is one of FLOSS's *S*T*R*O*N*G* points - that we quite happily throw massive engineering resource at multiple possible solutions before we settle on the correct one (that is, if there even IS a correct one!)
That is the PROBLEM with the MS approach - there is only one solution, and if it's the wrong one, tough. For example, imho Word is crap. Pretty much all word processors are trying to copy Word. In other words, it is almost impossible now to find a word processor that is capable of industrial strength work - they're all aimed at people who don't know how to type!
One size does NOT fit all.
Cheers,
Wol
SAME DIRECTION
Posted Mar 11, 2013 12:43 UTC (Mon) by dgm (subscriber, #49227)
[Link]
> That is one of FLOSS's *S*T*R*O*N*G* points - that we quite happily throw massive engineering resource at multiple possible solutions before we settle on the correct one (that is, if there even IS a correct one!)
That's only a benefit if we can finally agree on a correct one, and drop those that do not add much value. Want to bet Canonical will NOT drop Mir, even if it proves to be an inferior solution? Hint: BZR, Upstart.
The problem is not that Canonical develops an alternative. That's fine, even for Kristian Høgsberg (Wayland's architect and main developer). They could be doing it as a side project, like Wayland is. Instead Canonical is endorsing it, unleveling the play field and creating an artificial barrier for Wayland (or any other) to enter. I despise profoundly saying that, but in that sense Canonical is not better than Microsoft.
But let's wait and see. Maybe this time they will do the right thing.