Bug#727708: Spotify position in support of systemd in the default init debate

On Fri, Jan 17, 2014 at 5:37 PM, Thorsten Glaser <tg@mirbsd.de> wrote:

Noa Resare dixit:

>- We believe that systemd will have the stronger community momentum moving
>forward when it comes to seeing close integration between modern init
>system features and upstream projects.

I believe that this is precisely a reason *against* choosing systemd,
as it leads to monoculture, vendor lock-in (even more than we already
have), replacement of UNIX with FLOS, and caters to Poettering fans.

In short: if you want systemd, you can do that in a Debian Pure Blend
or something else, IMHO…

bye,
//mirabilos (DD but speaking his own opinion)

(these opinions are my own, and not cleared with Spotify leadership)

I believe that examples can be found in the history of Free Software of both extremes. Personally I think that the current java stewardship by Oracle is an example where monoculture and vendor lock-in is a real problem, and there are examples where competing solutions to the same problem has needlessly diverted resources that would have made either solution substantially better.

My conclusion is that the risks of vendor lock-in and monoculture inte case of systemd are smaller than the cost of losses due to duplicate efforts. I understand that you are not a fan of Lennart, but I believe that he has proven that given his frame of reference (bringing new kernel features to end users trumps compatibility with less feature rich environments) he is a person that listens to technical arguments. The better solution from a technical point of view tends to win over the over it's politically more convenient counterpart.

/noa

Spotify Free Software coordinator, strategist and possibly even evangelist. I/O Tribe.