Seriously, read his blog instead of your assumption I'm making shit up. He has a "vision" for linux and it's very much desktop focused which is where some of the conflict comes from resulting in those "not a bug" situations that I'm not just parroting. It's somewhat annoying to get flamed every time I suggest that it is less than perfect.
And using systemd to manage user services instead of foisting it off to a dozen different desktop frameworks makes sense in principle.
Until it hits something other than desktop computer space where a malicious user or just one trying a few things out messes things up seriously for many others - hence not getting the idea of a *nix system or even multiuser systems. If the implementation can avoid that problem, then fine, but if it's not doing that just yet and IMHO it's a feature that shouldn't be in a stable release until it can.
How about this one, out of the 10,000+ "engineers" working for Apple how many of them are going to know about this patent before filing, and how many of those are going to not need quotes around "engineer" and thus have done some first year physics as part of earning the title? I think you'll find single digits for the former and almost certainly zero for the latter. In this case with 2 GHz there are very special problems associated with having the sort of amplitude required to charge a phone faster than it's battery runs down and it's a very safe bet that every engineer has got enough of an idea about how microwave ovens work to know about those special problems. Above poster, I'm sure you are aware of those problems yourself but you just didn't consider it enough before posting.
Ever heard of self-depreciating humour? Yes this place is a sausage-fest and I am also male - so? The kiddies who go on about IT as if they are lumberjacks and it's far too tough a job for anyone without a dick are worth laughing at. They don't get the irony that it wasn't so long ago that only girls were allowed in the high school typing classes and only boys were allowed in the metalwork classes.
Without NASA there is nobody to pay for "private space" apart from communications satellites, and that's hardly enough to keep the lights on. Any "private space" company without military funding would be doomed. It's appears to be one of those situations where there is far too little return for a purely private model to work. It's worth mentioning that NASA didn't build the lunar lander, Grumman built the lunar lander. It's been "private space" ever since we ran out of captured German V2 rockets and started paying Chrysler and a pile of other companies for things to go into space.
Because mentioning a woman in IT triggers far too many snowflakes who will moan about how it's manly men's work to sit inside an office and type on a keyboard - no place for women at all.
implementing a minimum-wage increase throws some of the poorest of poor out into the unemployment line to starve
Bullshit. That's like those old arguments about workers compensation or an ability to sue for damages encourages workers to permanently disable themselves. You've been infected by poisonous political rhetoric that was old and worn out more than a century ago.
Perhaps you should consider more carefully your appeals to authority. A model limiting itself to nothing but wind and solar, not even more hydro let alone anything else, is not meant to be taken seriously alone. It's a thought experiment designed to illustrate the obvious situation that monocultures suck. It's not designed to prove what you have suggested at all.
All I did to "earn" those attacks from all those fanboys and yourself was to mention situations I have encountered where systemd is not perfect.
Which results in weird startup issues occasionally. I managed to hang my laptop trying to add an autostarting emacs server to my user session. Which shouldn't influence system boot, IMO, but it did
That's the kind of scope creep I was referring to elsewhere which IMHO is yet another sign that Lennart just doesn't "get" the idea of a *nix system or multiuser systems in general, but maybe I'm reading too much into it and his blog posts.
Morality is irrelevant; minimum wage is an efficiency model.
The efficiency model is to exploit the weak and desperate as much as possible so it is indeed a moral issue to draw a line beyond where exploitation cannot go.
I really don't know why you wrote so much to build a house of cards upon your faulty premise. What exactly were you trying to do with all of that? What's with the weird attack at the end?
Your own link not only utterly fails to support your claim above (100% supply for an entire day!) but is also an incredibly naive one-dimensional view of electricity generation and distribution. The world is three dimensional and we have these things called electricity distribution grids. We also have multiple types of ways to generate electricity. A strawman of limiting the number of sources and pretending that electricity is unavailable to be transmitted from another location is a unrealistic even for locations such as Hawaii let along the continental United States. Just give up your silly little game - you are not even playing it up to high school project level so why bother?
Which respected scientists predicted those scenarios?
The cover artist of TIME magazine:) On that note in 2050 people will be talking about the good old days of 2017 when we could solve just about anything with "one weird trick".
If you paid for college, especially with student loans, it was a bad investment, because you didn't learn squat about history.
This is a tech oriented site. Most of us who went to University did not learn about history there and instead picked up what we know in our own time - so it's a pretty strange insult to use.
Now Germany and Japan are economic powerhouses that contribute greatly to the world economy because humanity realized that its better to build the defeated enemies back up instead of leaving hatred to fester.
It was more to have a buffer against Stalin but the side effect was as you wrote.
Look for yourself instead of taking it from a biased source such as myself - it was not born perfect as you seem to be arguing. Oddly enough people actually have had less than a perfect experience with it.
You've been caught red handed - why whine about it?
I want facts
That is of course what I was asking for instead of your deliberately insane fantasy.
Also, please stop trying to appeal to authority on a distraction - it's not about orders of magnitude - your impossible benchmark set up to deliberately fail is the issue. How about you stop roleplaying your username?
Thank you. Something concrete. It's not something I'm likely to use since I'm a cluster guy so I was not aware of it.
We saw a part of that in the debate on the setting that kills all apps on session end. While I disagree with making that the default (at least for now), the idea that if you want something to keep running in the background you have to explicitly assign it to a background scope, so both the system and the sysadmin can see it's a background task and keep it constrained if necessary, is a good mechanism in my eyes.
Well that is something I very strongly disagree with but let's just put that down to a difference of opinion. I'll concede that that feature is by design for a purpose and not the newbie mistake by Lennart that it looks like (with the workflows in my workplace users log on remotely, kick long running jobs off, then log off so killing background tasks on logoff would be a disaster).
And most of the objections are people blindly parroting echo chamber
In my case it's been a combination of test machines and desktops having a variety of problems due to systemd (most admittedly several years ago, although the machine that wouldn't start up with a paticular mouse connected was last year and the systemd plus zfs problems were the year before) and a software vendor refusing to support their insanely expensive software if it's on a machines with systemd on it.
The project has a website. Perhaps you should stop wasting your time attacking people on the internet by taking a contrary view about a topic that you appear to know absolutely nothing about and instead actually find out something about the topic.
Now do you have an answer to the question: What is a specific situation where it is an advantage to let systemd handle resource control instead of some other way?
I hate to be overly negative, but based upon my 30 years of experience of writing software for a living, your level of education is usually inversely proportional to your skill level as an engineer.
Indeed - many engineers are very poorly skilled at being technicians. For example some years back despite being utter crap at welding I was testing and certifying weld joints among other things. It was a different skillset to welding. I'm only working with computers now because the vast majority of all those highly skilled programmers out there completely ignored the mathematics needed to do some things so would need a few years to do so tasks. So you get engineers writing really crappy code that does something, if badly, instead of having highly skilled programmers not having a clue where to start.
If you didn't graduate with a degree in software engineering then you are not really a software engineer
As others have written here there is also an "apprenticeship" path to being a professional engineer, but it's more difficult than the other way.
In a lot of cases however "software engineer" is just a HR granted title and shouldn't be considered the same way as a professional title. For example, there was a guy on this site that told everyone in his sig for about a decade that he was an engineer when it was only a HR granted title, and that guy went on to say he knew 9/11 was faked because he was an engineer and knew about buildings. He wished to be considered a professional engineer equivalent to a professional civil engineer without even being what the above poster would consider a software engineer (but I'm willing to concede people using their HR granted titles so long as they don't try to pretend IEEE or whatever considers them an engineer unless it actually does).
Slashdot Mirror
Until it hits something other than desktop computer space where a malicious user or just one trying a few things out messes things up seriously for many others - hence not getting the idea of a *nix system or even multiuser systems. If the implementation can avoid that problem, then fine, but if it's not doing that just yet and IMHO it's a feature that shouldn't be in a stable release until it can.
How about this one, out of the 10,000+ "engineers" working for Apple how many of them are going to know about this patent before filing, and how many of those are going to not need quotes around "engineer" and thus have done some first year physics as part of earning the title?
I think you'll find single digits for the former and almost certainly zero for the latter. In this case with 2 GHz there are very special problems associated with having the sort of amplitude required to charge a phone faster than it's battery runs down and it's a very safe bet that every engineer has got enough of an idea about how microwave ovens work to know about those special problems.
Above poster, I'm sure you are aware of those problems yourself but you just didn't consider it enough before posting.
Ever heard of self-depreciating humour?
Yes this place is a sausage-fest and I am also male - so? The kiddies who go on about IT as if they are lumberjacks and it's far too tough a job for anyone without a dick are worth laughing at. They don't get the irony that it wasn't so long ago that only girls were allowed in the high school typing classes and only boys were allowed in the metalwork classes.
Without NASA there is nobody to pay for "private space" apart from communications satellites, and that's hardly enough to keep the lights on. Any "private space" company without military funding would be doomed.
It's appears to be one of those situations where there is far too little return for a purely private model to work.
It's worth mentioning that NASA didn't build the lunar lander, Grumman built the lunar lander. It's been "private space" ever since we ran out of captured German V2 rockets and started paying Chrysler and a pile of other companies for things to go into space.
Because mentioning a woman in IT triggers far too many snowflakes who will moan about how it's manly men's work to sit inside an office and type on a keyboard - no place for women at all.
Bullshit. That's like those old arguments about workers compensation or an ability to sue for damages encourages workers to permanently disable themselves. You've been infected by poisonous political rhetoric that was old and worn out more than a century ago.
Perhaps you should consider more carefully your appeals to authority.
A model limiting itself to nothing but wind and solar, not even more hydro let alone anything else, is not meant to be taken seriously alone. It's a thought experiment designed to illustrate the obvious situation that monocultures suck. It's not designed to prove what you have suggested at all.
That's the kind of scope creep I was referring to elsewhere which IMHO is yet another sign that Lennart just doesn't "get" the idea of a *nix system or multiuser systems in general, but maybe I'm reading too much into it and his blog posts.
The efficiency model is to exploit the weak and desperate as much as possible so it is indeed a moral issue to draw a line beyond where exploitation cannot go.
I really don't know why you wrote so much to build a house of cards upon your faulty premise. What exactly were you trying to do with all of that? What's with the weird attack at the end?
Thanks - that kind of explains why I wasn't aware of the "global cooling" thing until the anti-science PR machine got going some time after 2000.
Your own link not only utterly fails to support your claim above (100% supply for an entire day!) but is also an incredibly naive one-dimensional view of electricity generation and distribution.
The world is three dimensional and we have these things called electricity distribution grids. We also have multiple types of ways to generate electricity. A strawman of limiting the number of sources and pretending that electricity is unavailable to be transmitted from another location is a unrealistic even for locations such as Hawaii let along the continental United States.
Just give up your silly little game - you are not even playing it up to high school project level so why bother?
And aliens built the pyramids?
A working brain. Perhaps you should apply yours to something other than attempts at deception.
The cover artist of TIME magazine :)
On that note in 2050 people will be talking about the good old days of 2017 when we could solve just about anything with "one weird trick".
It's really about morality, but from your previous posts I get that it's not your strong point.
This is a tech oriented site. Most of us who went to University did not learn about history there and instead picked up what we know in our own time - so it's a pretty strange insult to use.
It was more to have a buffer against Stalin but the side effect was as you wrote.
RUNNING ALL OF THE USA ON BATTERIES FOR AN ENTIRE DAY IS SUPPOSED TO BE A FACT?
Look for yourself instead of taking it from a biased source such as myself - it was not born perfect as you seem to be arguing. Oddly enough people actually have had less than a perfect experience with it.
Perhaps you should look at it as the updated version of a humidicrib that it is instead of what the headline is pretending it is.
That is of course what I was asking for instead of your deliberately insane fantasy.
Also, please stop trying to appeal to authority on a distraction - it's not about orders of magnitude - your impossible benchmark set up to deliberately fail is the issue. How about you stop roleplaying your username?
Well that is something I very strongly disagree with but let's just put that down to a difference of opinion. I'll concede that that feature is by design for a purpose and not the newbie mistake by Lennart that it looks like (with the workflows in my workplace users log on remotely, kick long running jobs off, then log off so killing background tasks on logoff would be a disaster).
In my case it's been a combination of test machines and desktops having a variety of problems due to systemd (most admittedly several years ago, although the machine that wouldn't start up with a paticular mouse connected was last year and the systemd plus zfs problems were the year before) and a software vendor refusing to support their insanely expensive software if it's on a machines with systemd on it.
The project has a website. Perhaps you should stop wasting your time attacking people on the internet by taking a contrary view about a topic that you appear to know absolutely nothing about and instead actually find out something about the topic.
OK - I take it all back. I reacted with anger.
Now do you have an answer to the question: What is a specific situation where it is an advantage to let systemd handle resource control instead of some other way?
Indeed - many engineers are very poorly skilled at being technicians.
For example some years back despite being utter crap at welding I was testing and certifying weld joints among other things. It was a different skillset to welding.
I'm only working with computers now because the vast majority of all those highly skilled programmers out there completely ignored the mathematics needed to do some things so would need a few years to do so tasks. So you get engineers writing really crappy code that does something, if badly, instead of having highly skilled programmers not having a clue where to start.
As others have written here there is also an "apprenticeship" path to being a professional engineer, but it's more difficult than the other way.
In a lot of cases however "software engineer" is just a HR granted title and shouldn't be considered the same way as a professional title. For example, there was a guy on this site that told everyone in his sig for about a decade that he was an engineer when it was only a HR granted title, and that guy went on to say he knew 9/11 was faked because he was an engineer and knew about buildings. He wished to be considered a professional engineer equivalent to a professional civil engineer without even being what the above poster would consider a software engineer (but I'm willing to concede people using their HR granted titles so long as they don't try to pretend IEEE or whatever considers them an engineer unless it actually does).