"We'll protect consumers! We'll stop Nestle if they put poison in their bottled water. But there's no need for heavy handed regulation; we'll only do it if they say their bottled water doesn't have poison in it."
Has it ever occurred to you that if so very many people are, in your words, "incompetent", that perhaps it might be that the problem is with the tool, and not the people?
If finding and reading the logs requires that a manual be read, then you've done something wrong.
That said...
One of the problems systemd faces is that it took thirty plus years of "how things are done" and tossed it in the trash -- without warning, and without a good sales pitch. We sysadmins woke up one day, and suddenly the next version of redhat changed everything out from under us. There was no transitional period, no slow migration a piece at a time. A dozen and a half things were suddenly completely different, requiring us to completely retrain ourselves.
That has a tendency to piss people off, especially when those people see less wrong with the way it was done in the first place than the way it's done now.
We had better things to do with our time, and in my organization that retraining bought us... nothing. The cost, on the other hand, was and is significant. I still hear my colleagues grumbling about the latest way in which systemd has caused them some small problem... And troubleshooting those problems is time they could have spent doing something more productive.
1: Star Trek Continues has never, to the best of my knowledge, been sued by CBS. In fact, they apparently have a pretty good relationship from what I've heard.
2: Axanar was probably a scam. Do some research on the guy behind it, and then ask yourself: where did the million bucks go? They had pro-bono representation, so it's doubtful they spent anywhere near that on their short-lived defense. They produced only a few minutes of video. And they were so flagrant about violating Trek IP that they were single-handedly responsible for CBS deciding they had to clamp down on fan productions -- and CBS could have done far, far worse than they did.
You can hate on CBS for a lot of things, but at least do it for something they deserve to be hated on for... Axanar is not so clear cut, and I have no clue where you came up with the supposed ST:C lawsuit.
You have a very strange definition of "convenient."
Want to work in Westlake? Yeah, okay, I might buy that. Not to the Valley or beyond though. Hell, just driving from the Valley to Santa Monica sucked balls, and that commute is around an hour shorter than Ventura to Santa Monica.
There's a reason I left, and it wasn't just the cost of housing...
Though having grown up and spend most of my life (until recently) there, I can tell you that the air quality is far better now than it was back in the '80s.
The pro-nuclear people had plenty of time to enlighten the masses. If they didn't do a good enough job educating them, then that's on them.
It's not like preferring solar and wind sources will bring about the end of the world.
It generally makes my skin crawl when I see fellow tech folk get into the holier-than-thou "you're too stoopid to make tech decisions" mode. Very few people are truly that stupid -- and far too many of those who are, work in tech to begin with.
It isn't just about stability. I run systemd in production on hundreds of servers, and have no stability or reliability problems with it.
That doesn't mean I actually like it.
The command naming is terrible; "systemctl" and "journalctl" do not roll off the keyboard for a touch typist. The logging is a mess. I could go on......and it just happened one day. There was little visible discussion, and little benefit outside the desktop.
It's probably more that it's HE than that it's a front loader.
I have an LG top loading washer, and the average run time is ~30 minutes (though a large load can take up to ~50). It uses very little water; that actually freaked me out at first, because I was used to looking in my washer and seeing submerged clothing.
Now a top loader with an agitator probably uses a lot more water; that's old tech.
I use git for non-distributed development, and it works better than any other source control system I've used (and I've used quite a few). Has its quirks, but so do they all.
The field of programming is full of people who actively claim design patterns are just bullshit and restrict creativity, and that "any good programmer" can write correct code without all that crap.
Huh. The argument I usually hear (and agree with) is that there are too many programmers who know nothing BUT "standard" design patterns, and don't understand how those patterns are really supposed to work, or what the criteria are that will allow one to determine the appropriateness of a given pattern.
The pattern doesn't fit perfectly? Who cares! It's all I've got, so shoehorn it in anyway!
There's a reason software quality did not drastically improve with the "invention" of design patterns. Hell, if you look at modern web-related code, I'd argue that code quality is in the toilet at present. Note that quality should not be confused with functionality -- there's some pretty awesome and even revolutionary stuff out there right now, but overall, the quality of that stuff tends toward sucking.
Design patterns are, at their core, a bunch of common names for a bunch of well known ways of doing things. Useful in conversation, but treating it like the Bible is a recipe for bad code.
And when they have to live up to other people's standards, the default position is to go on the attack.
Funny. It's been my experience (as both an employee and a as a manager) that many degree holders will do the exact same thing. That's a personality and/or motivation problem, not an education problem.
Either that article was very poorly written, or the author doesn't know what they're talking about. What, precisely, do they think is going to replace clicks? 'cause "passive scrolling" is pretty vague (and doesn't seem to me to meet the goal of advertising).
I also love the idea that Google Analytics made clicks popular. Because, y'know, this couldn't possibly have been a popular metric long before Google ever came on the scene...
I guess to the hipsters, the Internet starts with Google.
Slashdot Mirror
Sounds a lot like the old bubble.
I think it had to do with communism? commies? something like that.
It involved dots, anyway.
That's because all of your American contractors aren't American. They got outsourced.
"We'll protect consumers! We'll stop Nestle if they put poison in their bottled water. But there's no need for heavy handed regulation; we'll only do it if they say their bottled water doesn't have poison in it."
Well, then. That confirms my assumption that you're just an arrogant jackass that I can safely ignore. Happy holidays!
Has it ever occurred to you that if so very many people are, in your words, "incompetent", that perhaps it might be that the problem is with the tool, and not the people?
If finding and reading the logs requires that a manual be read, then you've done something wrong.
That said...
One of the problems systemd faces is that it took thirty plus years of "how things are done" and tossed it in the trash -- without warning, and without a good sales pitch. We sysadmins woke up one day, and suddenly the next version of redhat changed everything out from under us. There was no transitional period, no slow migration a piece at a time. A dozen and a half things were suddenly completely different, requiring us to completely retrain ourselves.
That has a tendency to piss people off, especially when those people see less wrong with the way it was done in the first place than the way it's done now.
We had better things to do with our time, and in my organization that retraining bought us... nothing. The cost, on the other hand, was and is significant. I still hear my colleagues grumbling about the latest way in which systemd has caused them some small problem... And troubleshooting those problems is time they could have spent doing something more productive.
...Silk Road?
Yeah, I got nothing.
Okay, wow.
1: Star Trek Continues has never, to the best of my knowledge, been sued by CBS. In fact, they apparently have a pretty good relationship from what I've heard.
2: Axanar was probably a scam. Do some research on the guy behind it, and then ask yourself: where did the million bucks go? They had pro-bono representation, so it's doubtful they spent anywhere near that on their short-lived defense. They produced only a few minutes of video. And they were so flagrant about violating Trek IP that they were single-handedly responsible for CBS deciding they had to clamp down on fan productions -- and CBS could have done far, far worse than they did.
You can hate on CBS for a lot of things, but at least do it for something they deserve to be hated on for... Axanar is not so clear cut, and I have no clue where you came up with the supposed ST:C lawsuit.
Because flying non-stop is just too expensive sometimes.
Spoken like a true CEO.
I bet people would use it more if they'd actually remembered to furnish the place.
Oops.
You have a very strange definition of "convenient."
Want to work in Westlake? Yeah, okay, I might buy that. Not to the Valley or beyond though. Hell, just driving from the Valley to Santa Monica sucked balls, and that commute is around an hour shorter than Ventura to Santa Monica.
There's a reason I left, and it wasn't just the cost of housing...
Yup.
Though having grown up and spend most of my life (until recently) there, I can tell you that the air quality is far better now than it was back in the '80s.
The pro-nuclear people had plenty of time to enlighten the masses. If they didn't do a good enough job educating them, then that's on them.
It's not like preferring solar and wind sources will bring about the end of the world.
It generally makes my skin crawl when I see fellow tech folk get into the holier-than-thou "you're too stoopid to make tech decisions" mode. Very few people are truly that stupid -- and far too many of those who are, work in tech to begin with.
Sometimes, the masses are right.
Y'know... I'd think that would be pretty important when you're about to insert tab A into space B...
Two words: packet loss.
It isn't just about stability. I run systemd in production on hundreds of servers, and have no stability or reliability problems with it.
That doesn't mean I actually like it.
The command naming is terrible; "systemctl" and "journalctl" do not roll off the keyboard for a touch typist. The logging is a mess. I could go on... ...and it just happened one day. There was little visible discussion, and little benefit outside the desktop.
It's probably more that it's HE than that it's a front loader.
I have an LG top loading washer, and the average run time is ~30 minutes (though a large load can take up to ~50). It uses very little water; that actually freaked me out at first, because I was used to looking in my washer and seeing submerged clothing.
Now a top loader with an agitator probably uses a lot more water; that's old tech.
Your preconceptions are out of date. Nothing wrong with that, but modern top loaders clean just as well.
And front loaders have mold issues if you don't leave the door open after washing, or so I've heard anyway.
I use git for non-distributed development, and it works better than any other source control system I've used (and I've used quite a few). Has its quirks, but so do they all.
I do miss $Id$, though.
Posting to remove bad mod. Bah.
The field of programming is full of people who actively claim design patterns are just bullshit and restrict creativity, and that "any good programmer" can write correct code without all that crap.
Huh. The argument I usually hear (and agree with) is that there are too many programmers who know nothing BUT "standard" design patterns, and don't understand how those patterns are really supposed to work, or what the criteria are that will allow one to determine the appropriateness of a given pattern.
The pattern doesn't fit perfectly? Who cares! It's all I've got, so shoehorn it in anyway!
There's a reason software quality did not drastically improve with the "invention" of design patterns. Hell, if you look at modern web-related code, I'd argue that code quality is in the toilet at present. Note that quality should not be confused with functionality -- there's some pretty awesome and even revolutionary stuff out there right now, but overall, the quality of that stuff tends toward sucking.
Design patterns are, at their core, a bunch of common names for a bunch of well known ways of doing things. Useful in conversation, but treating it like the Bible is a recipe for bad code.
And when they have to live up to other people's standards, the default position is to go on the attack.
Funny. It's been my experience (as both an employee and a as a manager) that many degree holders will do the exact same thing. That's a personality and/or motivation problem, not an education problem.
You start your own company. Nothin' stopping you.
Just sayin'.
Either that article was very poorly written, or the author doesn't know what they're talking about. What, precisely, do they think is going to replace clicks? 'cause "passive scrolling" is pretty vague (and doesn't seem to me to meet the goal of advertising).
I also love the idea that Google Analytics made clicks popular. Because, y'know, this couldn't possibly have been a popular metric long before Google ever came on the scene...
I guess to the hipsters, the Internet starts with Google.