Why Did ArchLinux Embrace Systemd? (2016)

Re:Why Did ArchLinux Embrace Systemd? (2016) by geggam on Monday October 21, 2019 @02:29PM (#21315573)

I think C requires more of people. Granted I am no C expert but having worked in the industry a couple decades I have made conclusions based on observations.

As a sysadmin I wrote a small kernel module to trigger a panic on a certain condition hoping to capture some info in a dump several years ago.

Today I cant find sysadmins who can use a CLI properly.

The goalposts have moved inwards IMO

Not sure its bad thing either but it makes for interesting comparisons

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by bitwize on Monday October 21, 2019 @02:40PM (#21315730)

It's kind of like back in the day Emacs was considered a programmer's tool. Yet secretaries not only used it, they learned how to configure it to their liking in Lisp! (If you tell a normie they are "customizing" the editor rather than "programming" it, they won't even realize it's hard!)

These days, people calling themselves professional developers with years of experience won't even touch Emacs.

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by NotATroll on Monday October 21, 2019 @03:55PM (#21316546)

Plenty of people still use Emacs.

I picked it up several months ago after using Jetbrains IDE's for quite a long time, and honestly haven't felt the need for any of what Jetbrains brought to the table.

Mostly thanks to LSP.

If you're not a Java developer, Emacs is perfectly fine as a configurable extensible editor. With the additional caveat that its lack of multithreading can get in the way sometimes.

[ Parent | on HN ]

Re:Why Did ArchLinux Embrace Systemd? (2016) by bitwize on Monday October 21, 2019 @06:06PM (#21318005)

I use Emacs, but at my last few jobs I was just about the only one.

[ Parent | on HN ]