1 |
On 04/06/14 15:21, Tanstaafl wrote: |
2 |
> On 6/3/2014 1:08 PM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
3 |
>> On Tue, Jun 3, 2014 at 11:48 AM, Tanstaafl |
4 |
>> <tanstaafl@×××××××××××.org> wrote: |
5 |
>>> On 6/3/2014 11:10 AM, Canek Peláez Valdés <caneko@×××××.com> wrote: |
6 |
>>>> Maybe. The thing is, this is going to keep happening, as more and more |
7 |
>>>> infrastructure migrates towards systemd. Perhaps a news item everytime |
8 |
>>>> it happens is unrealistic? |
9 |
> |
10 |
>>> Weren't you the one saying that those of us who were voicing |
11 |
>>> concerns that |
12 |
>>> systemd proponents were ultimately wanting to FORCE systemd on |
13 |
>>> everyone were |
14 |
>>> just scare-mongering conspiracy theorists? |
15 |
> |
16 |
>> Who is "forcing" anything? |
17 |
> |
18 |
> I was specifically referring to your comment that: |
19 |
> |
20 |
>> The thing is, this is going to keep happening, as more and more |
21 |
>> infrastructure migrates towards systemd. |
22 |
> |
23 |
> That comment right there - specifically the word *infrastructure* - |
24 |
> screams to me 'we intend to take over the world'. |
25 |
> |
26 |
> And yes, as devs get lazier (decide to rely on systemd rather than |
27 |
> build it to work independently of the init system), this will in fact |
28 |
> result in *users* (read: those lacking the skills to code every |
29 |
> program out there to work without systemd) eventually being *forced* |
30 |
> to switch to systemd. |
31 |
|
32 |
You can still install GNOME without systemd from Portage using the |
33 |
USE="openrc-force" (which needs to be unmasked using |
34 |
/etc/portage/profile/use.mask line like |
35 |
-openrc-force) |
36 |
|
37 |
And nobody is ever forced to do anything within Open Source, you always |
38 |
have the option to contibute code, or donate money to get someone |
39 |
else contribute the code |
40 |
|
41 |
Calling volunteers who work without paycheck lazy is just bad behavior |
42 |
|
43 |
> |
44 |
> That is simply the reality. You can ignore it if you like, but it |
45 |
> doesn't change it. Forced is forced. |
46 |
> |
47 |
>> That's what you and many others don't seem to understand: systemd is a |
48 |
>> *BETTER* implementation for basically *ALL* the hodgepodge of |
49 |
>> "solutions" that we had before in our plumbing layer. |
50 |
> |
51 |
> Time will tell, and you may even be right. The problem is, average |
52 |
> users really don't have a way to prove this to themselves, all we see |
53 |
> is the wailing and gnashing of teeth as stuff constantly *breaks* that |
54 |
> *never* broke before. |
55 |
> |
56 |
|
57 |
Nothing has been broken so far yet. People are just facing hard |
58 |
realities and noticing some packages have been abandoned for years, even |
59 |
before systemd became popular as it is now. You can't blame systemd, |
60 |
upower, and other developers for ditching such outdated code and |
61 |
using what they like as they code it for their application. |
62 |
|
63 |
- Samuli |