Systemd 256.1 Fixes "systemd-tmpfiles" Unexpectedly Deleting Your /home Directory

[Slartifartblast]

here is an interview with Linux

?

Syntax error

[Mo6eB]

Fuck this shit, I'm out. I don't want to run Linux on any desktop ever again, I'm done.

[slalomsk8er]

Well, good for you. I hope your tools and mindset have evolved since then.

I, too, used to sprinkle comments around the codebase. I still do in languages that are not very good or structured. In the languages we use at work we do explicitly NOT add comments to the code. They are practically forbidded to use. Here, we follow coding guidelines that are enforced with static analyzers and different linters in the compiling pipeline different metrics so we can not write obscure code. Furthermore, we name the functions and methods, variables and other stuff after what they do so we need no comments because the description is already there, in the function name. Additionally we are developing fully test driven, which in effect means all the tests describe how the code has to behave and our scenario tests therefore test if the code behaves exactly as our customer described how it should behave. In effect this means all requirements are written in code. Any chance to the code is guaranteed to be checked if requirements are still fulfilled.

Comments aren't here to document, how and what but to write down why!
Some of my comment have a few words plus ticket numbers, links to documentation or a short write up about stuff I had to research in them.
In the last couple of decades a lot of this also moved from comment into VCS commit messages but I'm coming back to adding more why comments directly into the code as I'm getting older.

[slalomsk8er]

Fuck this shit, I'm out. I don't want to run Linux on any desktop ever again, I'm done.

I'm also never got cozy with Fedora but this is why different distributions exist - some even forgo systemd

[mrg666]

I don't trust the "intelligence" of open source "developers", nor their "integrity".

The best lies are the ones that have a decent portion of truth in them.

The best scams and hoaxes are the ones that are done right in the open.

The best thieves steal while you are looking at them and convince you to help them,

Open source is a scam and always has been,

The first programming class i ever took was more than 40 years ago, I took a class in BASIC and I remember the first day the instructor told us the most important thing is to always comment your code, because no one is going to know what you are trying to do and you are not going to remember if you have to revisit it down the line.

If you want to see how half-assed open source development is and how big a scam it is, here is an interview with Linux where he is talking about the lack of kernel documentation:

https://youtu.be/bAop_8l6_cI?t=2275

This is the garbage that you and other put their trust in.

World runs on Linux and the code is open out there. You are so obviously stupid to claim something so obviously wrong. Seek help, seriously.

[lowflyer]

Fortunately systemd is optional and completely open source. Fortunately it's very easy to remove it completely or to switch to another alternative ...

[fotomar]

Fuck this shit, I'm out. I don't want to run Linux on any desktop ever again, I'm done.

Well, M$ hiring the systemd guys to extingush has worked on this guy.

Try Deuvian, Void, Artix, etc. and you'll have none of this nonsense.

[intelfx]

World runs on Linux and the code is open out there. You are so obviously stupid to claim something so obviously wrong. Seek help, seriously.

Haven't you heard? This guy is a Certified™ UNIX™ Sysadmin™ with a university degree™!

I bet he is just so much salty that his education and career investments turned out to be completely worthless that he's got sodium poisoning. You know, when you spend time and money to partake in the sacred knowledge, and then it turns out the sacred knowledge (and the subject of such knowledge) is just an obsolete piece of junk completely supplanted by something freely available as a commodity, it tends to mess with your world view.

[woddy]

I've been successfully running my business for 26-27 years with desktop GNU/Linux with no problems. Long before much RH, Intel or MS money were involved [except that MS money was propping up lawsuits against GNU/Linux]. Which good old days are you speaking of when you were somehow unable to get GNU/Linux to do productive work for you? Sounds a lot like you were failing due to a skill issue, unless you are referring to the period prior to Torvalds adopting the GPL in February 1992 which brought in all the GNU development to build it into a useful OS.

I agree, but open source or free software means anyone can use it and contribute.
To me if Microsoft, RedHat, Intel, SUSE etc. they invest makes me happy, software today is very different from what it was 20 years ago and GNU/linux needs everyone's contribution.
After all this is the essence of free software!
People are always complaining about something...

[sophisticles]

I, too, used to sprinkle comments around the codebase. I still do in languages that are not very good or structured. In the languages we use at work we do explicitly NOT add comments to the code. They are practically forbidded to use. Here, we follow coding guidelines that are enforced with static analyzers and different linters in the compiling pipeline different metrics so we can not write obscure code. Furthermore, we name the functions and methods, variables and other stuff after what they do so we need no comments because the description is already there, in the function name. Additionally we are developing fully test driven, which in effect means all the tests describe how the code has to behave and our scenario tests therefore test if the code behaves exactly as our customer described how it should behave. In effect this means all requirements are written in code. Any chance to the code is guaranteed to be checked if requirements are still fulfilled.

This is the definition of half-assed and is lousy coding practices.

Can you tell me what software your company produces so I can avoid it?

Not kidding about this, it is absolutely disgraceful that your company would forbid commenting the code, it sounds like most programmers at your company and most managers couldn't pass an intro to comp sci class at summer boot camp.