Indeed. An interface is a concept on architecture level, not on language level. You can implement interfaces in _any_ language. But all those wannabe "coders" think it is the language that provides the interface. Classical case of not understanding abstraction and why it is important. No surprise there is so much badly structured code out there.
No need, I am already CTO in a company that actually does understand technology.
Incidentally, all that stuff you describe is "business coding", nothing complicated in there. Just one big mess of glue. And usually one big mess of not understanding what is actually going on. I deal with that daily.
I agree to the VM approach. Although I will be virtualizing Windows, not Linux. May as well have the good infrastructure accessing the hardware directly.
It is difficult to say which it is, but here are a couple of possible reasons:
- Linux was getting too hard to hack and the intelligence community is pushing for systemd to fix that by having a known incompetent in charge of a critical system component - Linux did not generate enough support revenue for Red Hat and this is intended to fix that (and to make sure people cannot just go to a different distro) - Red Hat wants total control over Linux and systemd is their attempt to establish that by being the single source of a central component
It may also very well be a combination of these. In any case, it is targeted sabotage. I do not think Poettering is clued in though. They are just using him as a "useful idiot".
I believe that is the case, but Poettering is not clued in. It seems likely that Linux became too hard to hack into, so something needed to be done. Putting a known incompetent with a huge ego and no understanding of security in charge of a critical central system component is just the ticket to do that. And it will not look like a sabotage attack either, because said incompetent will screw up security all by himself, whit zero understanding of how he is being used.
The nature of the campaign that systemd was pushed with gives further indication for that: Zero arguments technical merit, except on the meaningless surface. As soon as anybody tried to go into actual technical arguments that matter, emotional appeal, deriding of the person, portraying them as "backwards" and "anti innovation", etc. This just means that there were no good technological arguments, but a group with access to PsyOps techniques really wanted it to be pushed hard. And look where we are, they basically succeeded. Of course, PsyOps only works against incompetents long-term and there is still a core of the Linux community that actually understands technology, as exemplified by this award and the continuing resistance. Technological facts do not go away.
It is two things, I think a) The Debian tech-board has long since been infiltrated and subverted by Red Hat and b) You can still run Debian just fine with sysVinit. You may lose Gnome, but that is no real loss.
It will be really interesting to see what happens if they try to take away b).
I am with you here. Most websites are broken these days, because browsers will accept any crap that they can still somehow interpret. This is bad for compatibility (if the other browser has a somewhat different definition of "crap"), bad for reliability and security. It makes filtering and scanning web-pages far more complicated. It makes things not quite mainstream far harder get working. And it causes web-"developers" to mistake what a specific browser accepts for what is actually fine and correct. When you then tell them that no, their stuff is broken, they become offended because they have no clue what you are talking about.
This way, a huge mountain of technological debt has been piling up in many corporate infrastructures and in the web in general, and it becomes harder and harder to fix things, because every time you try to, some other broken things come to the surface. The only way to deal with that is to enforce the standards. Only that way can you depend on things working sanely and retain your capability to act on issues.
The problem is that Poettering has reached a level of arrogance that he is unable to learn and unable to recognize anything others have done has merit. Dunning-Kruger far left side, a.k.a. "insight resistant". The technological issues resulting from that are a mere symptom. The UNIX philosophy has stood the test of time and it is a result of a myriad of failures, some of them quite like systemd in nature. Anybody dismissing it or ignoring it is not competent to build a major piece of infrastructure. The only sane way to deal with this is to stay away from the abomination he is creating. It will collapse sooner or later and at that time only those that did not go with will not suffer.
Funny thing, SMF, while hated by many Solaris admins, does this better: You can still write conventional init-scripts and hence you can easily write services that are not dependent on the init system being SMF. Because of his ignorance, Poettering is re-inventing the wheel and doing it badly.
Oh, quite a few people can still write clean code. It is just that the FOSS community had a large influx of people with huge egos and small skills in the last decade or so. Many of them learned their trade on Windows and they think what they do is professional and normal.
Indeed. But the Rust cult does not understand that. They somehow think Rust will prevent any and all important security issues and that already shows that these people have zero understanding of the problem.
I am all for that! Rewrite systemd in Rust, get all systemd experts and Rust experts into one place and then nuke it! Might make the future significantly better.
Well, if systemd had somebody with the experience, insight and personality needed for such a job, there would be very little resistance to it. It would stay an init-system and not try to assimilate everything else. Security and reliability would be taken seriously. IT would make things less complex instead of more so. But unfortunately, what we have is Poettering with just enough smarts to do real damage, a hugely inflated ego and zero capability to learn or listen to advice.
I think there is no hope for systemd. It needs to die before this mess can be fixed. While that takes place I will stay away from it. At the moment, Debian still works nicely with sysVinit, and I expect that will not change.
I do not hate working class people. I am merely an observer in this. But judging by what these people do to themselves, it seems they hate themselves very much.
That is nobody that followed the developments for the last 10 years or so. Of course, the actual experts have been warning of this far longer, but who in politics listens to mere experts. Pathetic.
The problem with Trump is not Trump, but those that voted for him. They show that a large faction of the voting population have zero smarts and easily fall for a con-man if he is just loud enough and promises the right things. They will then proceed to ignore his failures and cheer for anything that looks like he made good on a promise, even if completely unrelated to his actions. These people ask to be defrauded and they have zero understanding of how things work. When this mindless faction reaches a size where it has a majority of votes, a country is lost. Because while Trump will go away after a maximum of 8 years, the people that voted him into office will not and they will continue to do damage until everything collapses because of their non-understanding of reality.
Not that this is without historic precedent. In fact this is how it usually goes: The ones in power (and in a democracy that is the people) lose contact with reality enough so that politics does one stupid thing after another. This seems to have not much negative effect for a while, as society has a lot of inertia. However, when the strong downwards tendency eventually becomes clear, it will be too late to stop it, just because of that inertia as well. And, of course, those that caused it will never realize what they did. The only good thing about a democracy is that the ones that brought it down _will_ be suffering the consequences as well and they were doing it to themselves. Maybe the next iteration will be a bit smarter, but I doubt it.
As C has been constantly in the top 3 languages that coder positions are offered for and C does not tie you to a SJW infected cult, this is not even a valid comparison. Rust is a hype-du-jour, with its proponents blind to its shortcomings. They are retards that still think coding is all about the language you do it in (which is about as far from the truth as you can get, and which has been known to smart people for something like half a century) and Rust is their chosen deity that can do no wrong.
When Mozilla collapses, Rust will be gone as well. It really has not many things to recommend it, but some major shortcomings including the rabid and insane Rust community.
Slashdot Mirror
Indeed. An interface is a concept on architecture level, not on language level. You can implement interfaces in _any_ language. But all those wannabe "coders" think it is the language that provides the interface. Classical case of not understanding abstraction and why it is important. No surprise there is so much badly structured code out there.
You never will be CTO/CIO in my company ...
No need, I am already CTO in a company that actually does understand technology.
Incidentally, all that stuff you describe is "business coding", nothing complicated in there. Just one big mess of glue. And usually one big mess of not understanding what is actually going on. I deal with that daily.
Yes, a lot of coding *is* about the language, and the eco system of tools and libraries...
And that is why you cannot contribute anything worthwhile to this discussion: You are _incompetent_.
Me neither. Seems to be an attempt to say something negative, but without actual understanding of what I said.
I agree to the VM approach. Although I will be virtualizing Windows, not Linux. May as well have the good infrastructure accessing the hardware directly.
Indeed. It _was_ obvious before though that they would be disappointed. It was just not obvious to them and that is the real problem here.
It is difficult to say which it is, but here are a couple of possible reasons:
- Linux was getting too hard to hack and the intelligence community is pushing for systemd to fix that by having a known incompetent in charge of a critical system component
- Linux did not generate enough support revenue for Red Hat and this is intended to fix that (and to make sure people cannot just go to a different distro)
- Red Hat wants total control over Linux and systemd is their attempt to establish that by being the single source of a central component
It may also very well be a combination of these. In any case, it is targeted sabotage. I do not think Poettering is clued in though. They are just using him as a "useful idiot".
At this time, stock Debian with sysVinit is a reasonable option. There will be some systemd cruft still around, but it will be mostly inert.
I believe that is the case, but Poettering is not clued in. It seems likely that Linux became too hard to hack into, so something needed to be done. Putting a known incompetent with a huge ego and no understanding of security in charge of a critical central system component is just the ticket to do that. And it will not look like a sabotage attack either, because said incompetent will screw up security all by himself, whit zero understanding of how he is being used.
The nature of the campaign that systemd was pushed with gives further indication for that: Zero arguments technical merit, except on the meaningless surface. As soon as anybody tried to go into actual technical arguments that matter, emotional appeal, deriding of the person, portraying them as "backwards" and "anti innovation", etc. This just means that there were no good technological arguments, but a group with access to PsyOps techniques really wanted it to be pushed hard. And look where we are, they basically succeeded. Of course, PsyOps only works against incompetents long-term and there is still a core of the Linux community that actually understands technology, as exemplified by this award and the continuing resistance. Technological facts do not go away.
It is two things, I think
a) The Debian tech-board has long since been infiltrated and subverted by Red Hat
and
b) You can still run Debian just fine with sysVinit. You may lose Gnome, but that is no real loss.
It will be really interesting to see what happens if they try to take away b).
The way of the autocrat: Silence dissenting voices. He has obviously been creating his own filter-bubble for some time now.
I am with you here. Most websites are broken these days, because browsers will accept any crap that they can still somehow interpret. This is bad for compatibility (if the other browser has a somewhat different definition of "crap"), bad for reliability and security. It makes filtering and scanning web-pages far more complicated. It makes things not quite mainstream far harder get working. And it causes web-"developers" to mistake what a specific browser accepts for what is actually fine and correct. When you then tell them that no, their stuff is broken, they become offended because they have no clue what you are talking about.
This way, a huge mountain of technological debt has been piling up in many corporate infrastructures and in the web in general, and it becomes harder and harder to fix things, because every time you try to, some other broken things come to the surface. The only way to deal with that is to enforce the standards. Only that way can you depend on things working sanely and retain your capability to act on issues.
The problem is that Poettering has reached a level of arrogance that he is unable to learn and unable to recognize anything others have done has merit. Dunning-Kruger far left side, a.k.a. "insight resistant". The technological issues resulting from that are a mere symptom. The UNIX philosophy has stood the test of time and it is a result of a myriad of failures, some of them quite like systemd in nature. Anybody dismissing it or ignoring it is not competent to build a major piece of infrastructure. The only sane way to deal with this is to stay away from the abomination he is creating. It will collapse sooner or later and at that time only those that did not go with will not suffer.
Funny thing, SMF, while hated by many Solaris admins, does this better: You can still write conventional init-scripts and hence you can easily write services that are not dependent on the init system being SMF. Because of his ignorance, Poettering is re-inventing the wheel and doing it badly.
Oh, quite a few people can still write clean code. It is just that the FOSS community had a large influx of people with huge egos and small skills in the last decade or so. Many of them learned their trade on Windows and they think what they do is professional and normal.
Indeed. But the Rust cult does not understand that. They somehow think Rust will prevent any and all important security issues and that already shows that these people have zero understanding of the problem.
I am all for that! Rewrite systemd in Rust, get all systemd experts and Rust experts into one place and then nuke it! Might make the future significantly better.
They are the traitors that fell to Red Hat infiltration.
Surprisingly, SMF, for example, can still work perfectly fine with classical init scripts. I think you mistake badly what is happening.
Well, if systemd had somebody with the experience, insight and personality needed for such a job, there would be very little resistance to it. It would stay an init-system and not try to assimilate everything else. Security and reliability would be taken seriously. IT would make things less complex instead of more so. But unfortunately, what we have is Poettering with just enough smarts to do real damage, a hugely inflated ego and zero capability to learn or listen to advice.
I think there is no hope for systemd. It needs to die before this mess can be fixed. While that takes place I will stay away from it. At the moment, Debian still works nicely with sysVinit, and I expect that will not change.
Excellent! Perfectly right on the mark.
I do not hate working class people. I am merely an observer in this. But judging by what these people do to themselves, it seems they hate themselves very much.
That is nobody that followed the developments for the last 10 years or so. Of course, the actual experts have been warning of this far longer, but who in politics listens to mere experts. Pathetic.
The problem with Trump is not Trump, but those that voted for him. They show that a large faction of the voting population have zero smarts and easily fall for a con-man if he is just loud enough and promises the right things. They will then proceed to ignore his failures and cheer for anything that looks like he made good on a promise, even if completely unrelated to his actions. These people ask to be defrauded and they have zero understanding of how things work. When this mindless faction reaches a size where it has a majority of votes, a country is lost. Because while Trump will go away after a maximum of 8 years, the people that voted him into office will not and they will continue to do damage until everything collapses because of their non-understanding of reality.
Not that this is without historic precedent. In fact this is how it usually goes: The ones in power (and in a democracy that is the people) lose contact with reality enough so that politics does one stupid thing after another. This seems to have not much negative effect for a while, as society has a lot of inertia. However, when the strong downwards tendency eventually becomes clear, it will be too late to stop it, just because of that inertia as well. And, of course, those that caused it will never realize what they did. The only good thing about a democracy is that the ones that brought it down _will_ be suffering the consequences as well and they were doing it to themselves. Maybe the next iteration will be a bit smarter, but I doubt it.
As C has been constantly in the top 3 languages that coder positions are offered for and C does not tie you to a SJW infected cult, this is not even a valid comparison. Rust is a hype-du-jour, with its proponents blind to its shortcomings. They are retards that still think coding is all about the language you do it in (which is about as far from the truth as you can get, and which has been known to smart people for something like half a century) and Rust is their chosen deity that can do no wrong.
When Mozilla collapses, Rust will be gone as well. It really has not many things to recommend it, but some major shortcomings including the rabid and insane Rust community.
We actually need to ditch people that cannot handle C. Go be a "business coder" but stay away from real programs.