You see, we have several forks in the road that are presenting as choices and very quickly developers are want to choose the path well-traveled thinking that such a path will offer the least amount of effort and resistance. That might make sense initially when short-sighted objectives are being met, as in reduced cost of labor input, but ignoring good design practices by taking shortcuts with direct hard coupling of apis can produce long-term inflexibilities that will make future coding brittle and prone to breakage. (Image credit: Wikipedia.org)
Adding abstractions for apis is a good way to isolate hard coded system dependencies and using object encapsulation with abstract methods can allow polymorphic behaviors to be applied at a later date and thereby offering extensibility.
The shortest distance between two points is a straight line. Simply coupling an api (systemd) to a gui (Gnome) is an invitation for future disaster and in-built limitations. A GUI framework should be loosely coupled to the underlying system and choosing to included hard-coded system dependencies is a recipe for disaster.
But that is the current situation faced by developers who need to make a choice for how to deal with the newest Linux infrastructure changes now being phased in with systemd.
CinnArch is no more
[Edit 4/16/2013 9:00am I stand corrected. I misunderstood the dynamic with CinnArch and good fellow pointed the error of my ways out here:
Today, in similar fashion, Fuduntu announced they would also be closing their doors due to their inability to allocate needed resources to address refactoring their code in Gnome 2.34.
Others seeing the writing on the wall include Ikey Doherty, founder of SolusOS, who had his own issues with upstream developers, very recently made the decision to rebase his Distro on a new PiSi package management system in conjunction with a decision to fork Gnome3 to a new GUI called 'Consort'.
Today, +Aaron Seigo and +Ikey Doherty had a 'public' chat on Google Plus about the latest happenings. It was in response to +Katherine Noyes PCWorld story Fuduntu Linux is Closing its Doors. I have taken to calling Aaron 'The Thinker' lately and I find most of what he says intriguing and quite insightful. Here's his starting thread in reply to the Noyes story:
The ThinkerThe above is the starting comment from Aaron and here is what followed:
A comment wrote on 's reshare of the original post:
It is interesting that two of the reasons stated were Gtk+ 2 maintenance and systemd dependencies. It demonstrates two things: a) how important it is to pick the horse you bet on carefully (in this case Gtk+ 2) with a good understanding of its future (which mainly lies with the developers who maintain it .. or don't) and b) the impact that Linux middleware churn has on smaller shops.
Personally, I think that if a few of these smaller distributions set aside differences and worked together, they would stand a better chance of creating something with a solid future. Diversity is great, but there's a limit to what the ecosystem can sustain.
So, while this road well-traveled may appear to be a good choice beware of major roadwork, detours, and potholes going down that road. It may be a seemingly good ride right now but alternate routes may be advised. ;)