4 ms·
Well said. It's too bad some people seem to believe down-voting the truth will make their cognitive dissonance go away. > They're wrapping themselves in the GP
by pdkl95 11y ago
Well said. It's too bad some people seem to believe down-voting the truth will make their cognitive dissonance go away.
> They're wrapping themselves in the GPL
...while encouraging a development style that isolates processes so they use IPC when they should be simply linking to a library and making a function call. Systemd depends heavily on dbus, because it ties developers into this model.
This enables a rather convenient way for freeloading propriety software to use GPL code, without having to be subject to the requirements of GPL code. If you get some package to provide their services over dbus, you only have to "use" the software instead of linking against a library.
Even ignoring systemd's bad design that tightly couples together services that worked fine as separate specs for decades, and even ignoring the terrible "we don't give a crap if we break your environment for no reason" attitude that is common among systemd's authors, this end-run around the GPL is a very good reason to avoid systemd.
Now, I'm sure some people in this thread think I'm making crap up, being paranoid, or similar. To those people I say: when are you going to start paying attention? This is obvious when you look at the Linux community over the last 20 years. Stop being distracted by technical features instead of investing in your future. Are you going to be happy when all distros are de facto variants of Red Hat? Some of you might be, but if you're going to ignore the vast majority of Linux and Unix, could you at least fork the project instead of dragging the rest of the community down with you?\
- the_why_of_y 11y agoSo let me get this straight - you are arguing simultaneously that systemd's DBus APIs should be library calls, and that systemd should be less tightly coupled? Please tell me this is a parody?
- e12e 11y agoYou're aware there are a number of different libc-implementations one can choose from, right?
- anonbanker 11y agoin case he/she isn't, I'll just mention musl and uClibc.
- anonbanker 11y agoI love that you ignored the point of his argument: that systemd is an end-run around the GPL, in order to make it more accessible for proprietary malware.
- jhkjhk 11y agoBut BSD init is more horrible in this regard: by using shell script, it is easy to incorporate proprietary code into an otherwise copyleft product. The proponents of the "UNIX philosophy" that try to define the latter as writing lots of independent tools that can be combined in shell scripts, are probably just trying to make sure they also can work around the GPL in the future too. That's why the gcc compiler suite doesn't provide ways for other applications to access its AST via stdout: it could be used to code completion in emacs, but also to write proprietary gcc addons that manipulate the AST and work around gcc's GPL license.