Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Systemd, ten years later: a historical and technical retrospective. Parent comment
Replacement for "no problem" should run without problems.
python2 had no problems - there was a clear transition path:
1. "str" => b"str" 2. wait some time 3. "str" is u"str"
SysV, rc.d had no problems - just wait till systmed is ready.
If SysV was as bad there would be same amount of outcry as with systmed
Was it really necessary to make it painful?
Who? Somehow systemd defenders has no empathy and Lennart Poettering is a prime example. No matter right them or wrong they are perceived as threat.
Just be nice. It may hinder innovation but it helps community.
There are no comments on this comment yet.
Replacement for "no problem" should run without problems.
python2 had no problems - there was a clear transition path:
ALSA had no problems - just wait till PulseAudio is ready.SysV, rc.d had no problems - just wait till systmed is ready.
If SysV was as bad there would be same amount of outcry as with systmed
Was it really necessary to make it painful?
Who? Somehow systemd defenders has no empathy and Lennart Poettering is a prime example. No matter right them or wrong they are perceived as threat.
Just be nice. It may hinder innovation but it helps community.