Whoever modded this down is apparently completely clueless. If you do automatic restart when demons fail because of resource starvation, you may well make the complete machine unresponsive and make it impossible to log into it too. That is a worst-case scenario.
Some things are obvious and do not need a "Futurist" to predict it. Others just got lucky. If you have 1000 morons making predictions, somebody will be right repeatedly.
I see you have no clue how to make decision competently. Well, since your approach is obviously borked, you probably also lack what it takes to see that, so I will stop arguing now as it is a waste of time.
Very much this. A restart-wrapper around any demon that is reachable from the outside or from a lower privilege level is an invitation to hack said demon. Hence, if you need that restart, it has to come with carefully designed limits, logging of what happened and alerting that gets actually listened to. Having automatic restart as an easy to use standard feature is _not_ a good idea. It is a problem because many "coders" will just use this to paper over the defects of their shoddy software. Also, when a generic restart wrapper will do and is not a security problem, many already exist that work perfectly fine and are not integrated into an init system, were they have no valid reason to be.
This functionality if systemd is just another indicator of the cluelessness of the systemd people.
A direct lie. It is not the task of an init-system to restart a crashed demon. That is what you use a restart-wrapper for and it often needs to be customized for the demon in question in order to work well. And there are already such generic wrappers (where that is enough) that work well.
Big egos that want to leave their mark. Some people (bad engineers, all of them) cannot understand "if it is not broken, do not fix it". They think that it must be _them_ that obviously can do things massively better. Incidentally, that is pretty much what drives the systemd train-wreck. (Well, for variable values of "train-wreck". It will still take a long time until the systemd-morons have degraded Linux to the level of Windows. But why should I use something worse just to support the mental masturbation of some fuckup?)
Indeed. I use it. It works and not only can I fully understand it, I can also easily modify and extend it. Of course, it does not instill the irrational happiness of being protected by an all-seeing all-knowing benevolent demon that the systemd-fanatics seem to experience in its presence. Init just works and works well. For some people that does not seem to be enough though.
Indeed. KISS rules and tools and technologies that work well should not be replaced. Then things stay nicely simple, reliable and fast and you can get the actual work done.
But when you throw every new technological fad at it, then the technology becomes a difficult problem to handle in its own right. If you do that, you have failed on the onset of your work. Yet this seems to be the typical mode web-applications are designed these days. Everything must be flashy, graphical, interactive, etc. and it must be so in new and exciting ways. I still fail to comprehend why that is. This is not a video-game, it is business software that implements a process. If you are calculating, say, mortgage rates, a basic text interface is already enough, maybe with the ability to show a picture. HTML 2.0 does that just fine. So why do they have to push 2MB (I kid you not, I saw this with a customer) of JavaScript to the client to show a simple table, not even a graph? Utter stupidity.
High IQ is a trap. Many people with it think because they are so smart, they do not need experience or actual understanding or actual learning. They end up being impressively mentally agile, but cannot produce solid solutions even for simple problems. On hard problems they often fail completely. And they typically have a selective blindness to that because they can argue anybody into the ground. High IQ, high opinion of themselves, no actually useful skills. High-IQ morons are a lot worse than low-IQ ones, because they can do real damage. And there are a lot of them.
That said, it is very nice to get well-rounded people with a high IQ. These are rare, but they will solve anything.
You must never have worked on the back-end where you have to be able to handle all the demented things the front-end "horde of incompetents" does and expects to work.
Well, "can do full stack" and "can do full stack competently" is a world of difference. Somebody for the first thing that can actually get things to work (a minimal requirement) is already hard to find. Finding somebody that can do it well, maintainable, clean and, foremost, actually understands KISS and respects it deeply is almost impossible to find. Yet unless you get that second type of person, the product that comes out of it will end up being very expensive and essentially must be thrown away after having wastes countless developer and user hours.
Of course, do not expect to find the second person to be younger to be, say, 40 years and do expect them to demand the salary of a very senior engineer. Because they are. That will be, say, something like 3..10x what your average code monkey costs. I currently do such a job for a customer from the Fortune 500 (at around 40% engagement) and they literally have to have my daily rate signed-off by senior management every time the contract is extended as it is about 2.5 times the maximum they have on their rate-card.
There are good developers and there are bad developers. Once you know and understand the programming paradigm, you should be able to work on anything from Linux kernels to JavaScript apps in browsers.
While I agree to that, maybe 1% of the coders on the market can actually do that. And I do not mean "do it well", I mean do it at all with some useful results. The following is still the sad state of affairs: https://blog.codinghorror.com/...
The front-end is basically completely FUBAR at this time. Always changing trends, always apparently good (but actually really bad) new ideas (like REST now), and everything new is expected to use them. But after a few years the framework designers lose interest and a new greatest thing is born and the old one withers and dies (very slowly). All that without any actual benefit, because business logic and business applications do not need any of that, a vt100 would actually be perfectly fine for most of them. And you do actually find those vt100's still in use. Although they are now a badly working Java Applet, instead of the original rock-solid serial terminal.
While "new" technologies and frameworks are created at a break-neck pace, but they are not decommissioned at the same pace. So the number of different technologies you have to keep running at the same time gets larger and larger. Not good. Most applications web would actually do fine with plain HTML and a bit of JS for interactivity, but that would be plain old boring and nobody would want to be boring just for the sake of actually delivering a mature stable and professionally done product. Instead it is always the next stupid thing that is supposed to solve everything a lot better than the last stupid thing.
Basically, it boils down to most coders never having heard of KISS or not understanding it at all. The utterly demented things coders do are staggering. And the utter lack of skill, insight and knowledge is the same. I recently told some people that their web application was not working with a proxy because it was not web-standard conform and they did not even understand what "RFC7230" was and why it was _their_ problem if they violated it, regardless of whether the framework they were using was doing it or not. Or application teams that expose data to the browser that they must not expose to it or the security model goes out the window. Turns out they had no idea what was getting sent to the browser. Or the senior (> 5 years experience!) web developer that I had to explain the anatomy of an URL to. The list goes on.
In the end, all this is just an expression of too many bad coders and too many bad framework designers (but with big egos!). And they all want to show off their mediocre skills because they have delusions of being masters of this game and jump of every demented new trend as they think that will make them shine. What it actually does is create a mess of inconsistent technologies were you can find all the "web application coding worst practices" because somebody with not even minimal understanding of competent coding thought it was a good idea to do something clever.
Paranoids are irrational. They always must have the maximum of control and surveillance they can get. It is a mental disease. Just look at all the people Stalin had killed because he felt threatened by them. Completely bonkers.
Well, I am not sure. Ordinarily, utter incompetence would be enough, but with the massive degree of damage they do I think at least some maliciousness or lack of caring about the customer comes into play.
Slashdot Mirror
Thanks to whoever modded this down for further demonstrating the utter cluelessness of the systemd morons.
Whoever modded this down is apparently completely clueless. If you do automatic restart when demons fail because of resource starvation, you may well make the complete machine unresponsive and make it impossible to log into it too. That is a worst-case scenario.
Some things are obvious and do not need a "Futurist" to predict it. Others just got lucky. If you have 1000 morons making predictions, somebody will be right repeatedly.
I see you have no clue how to make decision competently. Well, since your approach is obviously borked, you probably also lack what it takes to see that, so I will stop arguing now as it is a waste of time.
No need to ask any questions, the answers will be worthless anyways.
I want cloud integration, were the kernel runs in the cloud!
True. But the last thing you want in a resource starvation situation is an automatic restart.
Very much this. A restart-wrapper around any demon that is reachable from the outside or from a lower privilege level is an invitation to hack said demon. Hence, if you need that restart, it has to come with carefully designed limits, logging of what happened and alerting that gets actually listened to. Having automatic restart as an easy to use standard feature is _not_ a good idea. It is a problem because many "coders" will just use this to paper over the defects of their shoddy software. Also, when a generic restart wrapper will do and is not a security problem, many already exist that work perfectly fine and are not integrated into an init system, were they have no valid reason to be.
This functionality if systemd is just another indicator of the cluelessness of the systemd people.
That, unfortunately, _is_ the sad state of affairs.
A direct lie. It is not the task of an init-system to restart a crashed demon. That is what you use a restart-wrapper for and it often needs to be customized for the demon in question in order to work well. And there are already such generic wrappers (where that is enough) that work well.
Big egos that want to leave their mark. Some people (bad engineers, all of them) cannot understand "if it is not broken, do not fix it". They think that it must be _them_ that obviously can do things massively better. Incidentally, that is pretty much what drives the systemd train-wreck. (Well, for variable values of "train-wreck". It will still take a long time until the systemd-morons have degraded Linux to the level of Windows. But why should I use something worse just to support the mental masturbation of some fuckup?)
Indeed. I use it. It works and not only can I fully understand it, I can also easily modify and extend it. Of course, it does not instill the irrational happiness of being protected by an all-seeing all-knowing benevolent demon that the systemd-fanatics seem to experience in its presence. Init just works and works well. For some people that does not seem to be enough though.
Well, maybe. Of course, if you have only one data-point, you cannot make a good decision anyways.
Indeed. KISS rules and tools and technologies that work well should not be replaced. Then things stay nicely simple, reliable and fast and you can get the actual work done.
But when you throw every new technological fad at it, then the technology becomes a difficult problem to handle in its own right. If you do that, you have failed on the onset of your work. Yet this seems to be the typical mode web-applications are designed these days. Everything must be flashy, graphical, interactive, etc. and it must be so in new and exciting ways. I still fail to comprehend why that is. This is not a video-game, it is business software that implements a process. If you are calculating, say, mortgage rates, a basic text interface is already enough, maybe with the ability to show a picture. HTML 2.0 does that just fine. So why do they have to push 2MB (I kid you not, I saw this with a customer) of JavaScript to the client to show a simple table, not even a graph? Utter stupidity.
High IQ is a trap. Many people with it think because they are so smart, they do not need experience or actual understanding or actual learning. They end up being impressively mentally agile, but cannot produce solid solutions even for simple problems. On hard problems they often fail completely. And they typically have a selective blindness to that because they can argue anybody into the ground. High IQ, high opinion of themselves, no actually useful skills. High-IQ morons are a lot worse than low-IQ ones, because they can do real damage. And there are a lot of them.
That said, it is very nice to get well-rounded people with a high IQ. These are rare, but they will solve anything.
You must never have worked on the back-end where you have to be able to handle all the demented things the front-end "horde of incompetents" does and expects to work.
PHP causes dementia. Probably best stay away from it ;-)
I fully agree on learning new things though.
Well, "can do full stack" and "can do full stack competently" is a world of difference. Somebody for the first thing that can actually get things to work (a minimal requirement) is already hard to find. Finding somebody that can do it well, maintainable, clean and, foremost, actually understands KISS and respects it deeply is almost impossible to find. Yet unless you get that second type of person, the product that comes out of it will end up being very expensive and essentially must be thrown away after having wastes countless developer and user hours.
Of course, do not expect to find the second person to be younger to be, say, 40 years and do expect them to demand the salary of a very senior engineer. Because they are. That will be, say, something like 3..10x what your average code monkey costs. I currently do such a job for a customer from the Fortune 500 (at around 40% engagement) and they literally have to have my daily rate signed-off by senior management every time the contract is extended as it is about 2.5 times the maximum they have on their rate-card.
There are good developers and there are bad developers. Once you know and understand the programming paradigm, you should be able to work on anything from Linux kernels to JavaScript apps in browsers.
While I agree to that, maybe 1% of the coders on the market can actually do that. And I do not mean "do it well", I mean do it at all with some useful results. The following is still the sad state of affairs: https://blog.codinghorror.com/...
The front-end is basically completely FUBAR at this time. Always changing trends, always apparently good (but actually really bad) new ideas (like REST now), and everything new is expected to use them. But after a few years the framework designers lose interest and a new greatest thing is born and the old one withers and dies (very slowly). All that without any actual benefit, because business logic and business applications do not need any of that, a vt100 would actually be perfectly fine for most of them. And you do actually find those vt100's still in use. Although they are now a badly working Java Applet, instead of the original rock-solid serial terminal.
While "new" technologies and frameworks are created at a break-neck pace, but they are not decommissioned at the same pace. So the number of different technologies you have to keep running at the same time gets larger and larger. Not good. Most applications web would actually do fine with plain HTML and a bit of JS for interactivity, but that would be plain old boring and nobody would want to be boring just for the sake of actually delivering a mature stable and professionally done product. Instead it is always the next stupid thing that is supposed to solve everything a lot better than the last stupid thing.
Basically, it boils down to most coders never having heard of KISS or not understanding it at all. The utterly demented things coders do are staggering. And the utter lack of skill, insight and knowledge is the same. I recently told some people that their web application was not working with a proxy because it was not web-standard conform and they did not even understand what "RFC7230" was and why it was _their_ problem if they violated it, regardless of whether the framework they were using was doing it or not. Or application teams that expose data to the browser that they must not expose to it or the security model goes out the window. Turns out they had no idea what was getting sent to the browser. Or the senior (> 5 years experience!) web developer that I had to explain the anatomy of an URL to. The list goes on.
In the end, all this is just an expression of too many bad coders and too many bad framework designers (but with big egos!). And they all want to show off their mediocre skills because they have delusions of being masters of this game and jump of every demented new trend as they think that will make them shine. What it actually does is create a mess of inconsistent technologies were you can find all the "web application coding worst practices" because somebody with not even minimal understanding of competent coding thought it was a good idea to do something clever.
Paranoids are irrational. They always must have the maximum of control and surveillance they can get. It is a mental disease. Just look at all the people Stalin had killed because he felt threatened by them. Completely bonkers.
Why do you pay for roads that everybody can use and some may be using more than you? Is this a serious question?
Well, I am not sure. Ordinarily, utter incompetence would be enough, but with the massive degree of damage they do I think at least some maliciousness or lack of caring about the customer comes into play.
The correct word is "incompetently" and lacking independent review. Good old MS, screwing the customer even when they do not profit from it.
That is a great one!