If it wasn't incriminating, then why did they change it when it was exposed
A) If I found out I accidentally used a pedo logo, I'd change it too. B) If I found out alt-right nutjobs were spreading shit around the internet about my shop, I'd get off my ass to change it because I don't want my customers or employees shot by fucking morons like you.
"One nutcase" would be a guy picking a random pizza shop for a random reason. This is fake news goading a nutcase. It will probably happen again. We've been trying to warn the right this would be the result of their constant pimping, but they'll do anything to get elected, fuck the consequences.
BTW I'm apparently competent enough to patch shit now and then. That shit won't be anything systemd related, so that's one less contributer to your mess. Have fun with that.
You fail to realize that discoverability is a desireable software attribute, and systemd does not have it.
I've had very few discoverability problems working in unfamiliar territory before systemd. Mostly, I just had to ferret out the right env flags to stop debug output from being suppressed from within init.d scripts... that was less discoverable than it could have been. On systemd, discoverability is for shit.
many of the whiners seem to be complaining that they might have to learn something new.
No, I like learning new things. Learning crappy things that have no reason to be so crappy, however, is not fun, and spending a bunch of time dealing with deficiencies in systemd is not what I like to do with my time. Next time I have a reason to install on something (rare, these days) I'll definitely be checking out devuan.
For example you now have hugely complex systems just to make sure your soundcard will only be usable by users logged in locally.
Ironically, trying to work around that to allow a system daemon to use sound was one of the first things that pissed me off against the new session-based model, and in a separate incident, working around the awful stuff that has been done to audio by pulseaudio's session-based mixer management started to sour my stomach on just about anything LP has touched (well OK, prior to all that I did initially get mildly pissed until avahi finally became optional in Debian.) Now I find myself occasionally delayed dealing with systemd crap that would never have been a problem under the previous system.
This has happened to me as well. How did I determine it? By spending an hour figuring out something that would normally take me 5 minutes to figure out.
There's tons more *useless* information in the systemd journal, and all the useful logging daemons usually do tends to be turned off by whoever wrote the default service file.
I really can't see how a system where a failed service doesn't bother to tell you it failed when started by hand from the command-line got anywhere popularity-wise. Seriously. Doing a "systemctll start blah" when blah enters a failed state doesn't say anything different than when blah starts successfully. What. The. Hell.
Also, I don't appreciate having to learn a bunch of directives only useful inside systemd unit files, named apparently by someone with really bad instincts for naming things. With a shell script, I can see a command being used, and if I do not know it yet, I can read the manpage for it, and here's the trick: I can then use that command for other stuff, not just running daemons.
Granted systemd is better at "structuring" the init scripts... is you need to manipulate them programmatically that's handy. Almost. Everyone. Does. Not. Need. To.
What I got from that ad was that the particular drug causes *permanant* hair loss while other drugs do not, and this side-effect was not mentioned to caregivers/patients so they could factor it into their decision.
Another prospect once this technology is widespread would be to have side and back-mounted lights that cooperatively light the road for other drivers, which can then dim their own forward facing lights more to reduce even further the glare going into your windshield. Streetlights could get into the act as well.
I've been of the opinion for a while that really, this technology is where all the attention should be, because its potential for disaster is somewhat less than autonomous vehicles, and it allows the groundwork for autonomous vehicles to be built without putting tons of them on the road before they are really ready.
One thing though is they should be very aware of what the optimum anatomical response of a human is -- too much variability in the amount of glare might be worse than more glare at a relatively constant intensity, depending on how the eye processes things... so studies in driving simulators would seem merited.
The truth is nothing really great gets done while stoned
I would beg to differ. But I will simply point out that nothing really great gets done while skydiving, either, but we don't call people who skydive in their off-time lazy.
Yeah, been there. Still kinda there. Still wondering why managers think it is a good idea to have me half asleep with CLI windows open to mission critical boxes, though I guess in cases where said boxes are actually completely belly up, it might be better than not.
Slashdot Mirror
If it wasn't incriminating, then why did they change it when it was exposed
A) If I found out I accidentally used a pedo logo, I'd change it too.
B) If I found out alt-right nutjobs were spreading shit around the internet about my shop, I'd get off my ass to change it because I don't want my customers or employees shot by fucking morons like you.
Seriously, you need to go see a shrink.
It's agreed this was one nutcase, then.
"One nutcase" would be a guy picking a random pizza shop for a random reason. This is fake news goading a nutcase. It will probably happen again. We've been trying to warn the right this would be the result of their constant pimping, but they'll do anything to get elected, fuck the consequences.
You will be soon, when Trump betrays you.
Why would you? What ever made you think you could trust a doctor with a computer?
Good point. Wait... then why wold we trust a real estate developer and pyramid marketing purveyor to run a country again?
People who actually believe it are in the minority and are simpletons or mentally ill.
You mean, like this guy?
http://www.businessinsider.com...
It's the ones in police body armor that suck. Especially in that highly irradiated vault where you have to put on a radiation suit.
Ah, that explains it. Flash-free here for years now.
and is currently the 113rd most visited website in the world, according to Alexa rankings.
...never heard of it.
Off you go now ...
Off to devuan...
BTW I'm apparently competent enough to patch shit now and then. That shit won't be anything systemd related, so that's one less contributer to your mess. Have fun with that.
You fail to realize that discoverability is a desireable software attribute, and systemd does not have it.
I've had very few discoverability problems working in unfamiliar territory before systemd. Mostly, I just had to ferret out the right env flags to stop debug output from being suppressed from within init.d scripts... that was less discoverable than it could have been. On systemd, discoverability is for shit.
many of the whiners seem to be complaining that they might have to learn something new.
No, I like learning new things. Learning crappy things that have no reason to be so crappy, however, is not fun, and spending a bunch of time dealing with deficiencies in systemd is not what I like to do with my time. Next time I have a reason to install on something (rare, these days) I'll definitely be checking out devuan.
For example you now have hugely complex systems just to make sure your soundcard will only be usable by users logged in locally.
Ironically, trying to work around that to allow a system daemon to use sound was one of the first things that pissed me off against the new session-based model, and in a separate incident, working around the awful stuff that has been done to audio by pulseaudio's session-based mixer management started to sour my stomach on just about anything LP has touched (well OK, prior to all that I did initially get mildly pissed until avahi finally became optional in Debian.) Now I find myself occasionally delayed dealing with systemd crap that would never have been a problem under the previous system.
It's just funny that example was chosen.
This has happened to me as well. How did I determine it? By spending an hour figuring out something that would normally take me 5 minutes to figure out.
There's tons more *useless* information in the systemd journal, and all the useful logging daemons usually do tends to be turned off by whoever wrote the default service file.
I really can't see how a system where a failed service doesn't bother to tell you it failed when started by hand from the command-line got anywhere popularity-wise. Seriously. Doing a "systemctll start blah" when blah enters a failed state doesn't say anything different than when blah starts successfully. What. The. Hell.
Also, I don't appreciate having to learn a bunch of directives only useful inside systemd unit files, named apparently by someone with really bad instincts for naming things. With a shell script, I can see a command being used, and if I do not know it yet, I can read the manpage for it, and here's the trick: I can then use that command for other stuff, not just running daemons.
Granted systemd is better at "structuring" the init scripts... is you need to manipulate them programmatically that's handy. Almost. Everyone. Does. Not. Need. To.
There is no such thing as a customer anymore, only unpaid beta testers.
Hahah! You have won the Slashdot. Hats off to you.
Well, if naming automotive related companies after famous physicists is a trend, I guess Hertz just lucked back into fashion.
I wonder what the first... eh.... exciting?.... offering from "Bohr Autos" will look like.
What I got from that ad was that the particular drug causes *permanant* hair loss while other drugs do not, and this side-effect was not mentioned to caregivers/patients so they could factor it into their decision.
Still a typical ambulance chasing ad, though.
Another prospect once this technology is widespread would be to have side and back-mounted lights that cooperatively light the road for other drivers, which can then dim their own forward facing lights more to reduce even further the glare going into your windshield. Streetlights could get into the act as well.
I've been of the opinion for a while that really, this technology is where all the attention should be, because its potential for disaster is somewhat less than autonomous vehicles, and it allows the groundwork for autonomous vehicles to be built without putting tons of them on the road before they are really ready.
One thing though is they should be very aware of what the optimum anatomical response of a human is -- too much variability in the amount of glare might be worse than more glare at a relatively constant intensity, depending on how the eye processes things... so studies in driving simulators would seem merited.
Oh also:
I once went to a band-practice
..."this one time, at band camp"?
Lucky dog, he could have died... from the chocolate.
Arguing with stoners is useless.
You mean, you tend to lose the arguments.
Now. Go away.
Still here. Suck it up, buttercup.
The truth is nothing really great gets done while stoned
I would beg to differ. But I will simply point out that nothing really great gets done while skydiving, either, but we don't call people who skydive in their off-time lazy.
This one is obviously for the lark. Have a sense of humor.
Yeah, been there. Still kinda there. Still wondering why managers think it is a good idea to have me half asleep with CLI windows open to mission critical boxes, though I guess in cases where said boxes are actually completely belly up, it might be better than not.