Insults are the domain of the Democrats, have some couth. Republicans don't generally use insult as a substitute for rational thinking, that's a Democratic play.
"Heart rules the head", IOW emotional thinking, is what Democrats do.
Oh, and because there are no examples of the other party being like that at all.
Holy shit, dude.
This whole R versus D thing is highly destructive to intelligent discussion, especially when adding generalizations and ad-hominem.
and anything else "nuclear-related" that isn't at a power plant should be included in any statistical analysis to predict the probability of the next Chernobyl.
Each accident must have occurred during the generation, transmission, or distribution of nuclear energy. That includes accidents at mines, during transportation by truck or pipeline, or at an enrichment facility, a manufacturing plant, and so on.
Back in the day when I just started digitizing my CD's, if you'd asked me if I wanted some third party to have read/write access to my digital music library, I would have called you nuts.
I bought it, it's mine, and I don't need anyone to manage it for me, thank you very much. I still feel that way.
Now people are keeping the only copies of their music on devices that they don't control, running software they don't control.
And they want us to listen when they complain? Craziness.
Yet, you fail to give any explanation at all as to why bottom-posting is better. I think I clearly explained why I preferred top-posting. This was long before MS had an email client.
But your answer is just, "Because... Microsoft! BLARG!". You're exactly the kind of wignut I was talking about. You scream about why top-posting is wrong, but can never give any good reason why.
It's common email convention now, at least in my experience - when you respond to someone, you put your response on top, so as the conversation chain grows, the order is the most recent (and therefore the most pertinent) to the oldest, descending. So you don't have to scroll through pages just to see the last reply.
Back in the day, on newsgroups, if you did that you'd get absolutely SCREAMED at for "TOP POSTING", because it was WRONG.
From the guardians of all that is right and wrong.
although for all but the top maybe 10% of coders that's probably more important than anything. You're rank and file are just implementing biz logic after all. But don't forget that the ability to learn and adapt goes _down_ as you get older. It just does, and there's plenty of research to show this. An experienced programmer can crank out code he's already written faster, but so what. He's gonna want to work fewer hours and have more benefits. On the low end I can not only work those young guys half again as hard and pay them half as much. They cost less to give medical insurance for to boot. On the high end their ability to learn makes up for their lack of experience.
The reason you were taught to respect your elders is they were smart enough to know they weren't needed anymore and you'd need an emotional reason drilled into you when you were mentally vulnerable or you'd kick 'em to the curb.
Wow, seriously? Pro-tip: go anonymous if you just want to troll.
On the off chance you actually mean that, I'm not going to even bother explaining to you what's wrong with your line of thinking. You don't understand software development at all.
I agree that how one arrives at the social and economic structure of Star Trek is left to the imagination, but some of the presumably enabling elements, namely, the technology, are shown front-and-center. What will happen when everyone has access to a replicator that can make all the necessities of life - food, shelter, clothing - in as much abundance as anyone would ever need?
Maybe that will result in disaster the likes of which would strain the imagination... but maybe not.
Whatever the outcome, I'm pretty sure such technology would render the notions of 'capitalism' and 'communism' somewhat useless. Star Trek's socioeconomic ideas don't seem to be so out there as to be implausible.
Since it's pretty much a fact that you can work longer and harder when you're young. And it's not like experience is all that important in a brand new field. I understand why the working class is against it. We all get old but very few of us can stop working at 40. But I sorta wish we working class folks could be more honest about it and just admit we're protecting our own interests. There's absolutely nothing wrong with that but we act like we're doing something disdainful...
Programming isn't like shoveling coal - working harder and longer usually results in worse output. And experience can be a very strong productivity multiplier.
If you had any tech experience at all you'd know this.
WatchMojo, one of the most popular channels of YouTube with over 12 million subscribers, has been hacked. Subscribers of one of YouTube's most popular channels, WatchMojo [...]
Forget beauty, whatever you or the next person thinks it is. Being that obese means that her children, if she has any, will be left without a mother rather early.
It's like smoking, or free-solo climbing. Sure, you can do it, it's a free country. But if you have people that love you and don't want you to die young, it's really not OK.
Not that I like or condone the language, but the old VB6 (and.NET WinForms) front-end designers (aside from missing CSS-like styling) remain better than what MS offers now... WPF, which is a total mess in terms of unnecessary complexity, or anything AT ALL targeting the train wreck we call HTML.
I'm talking in terms of applications where someone's trying to actually perform useful work, not "content consumption" / etc.
And don't give me that straw-man argument that you can't achieve good SoC without MVVM / MVC / M** and point to something from coding horror as an example.
-nothing comes even close to java in terms of stability. I will happily debug a war created in 2002 and figure out ways to work around old jdk issues.
It's sad that thick client gets completely ignored in the discussion.
I have a 100KLOC+ WinForms application written in.NET that I completed in 2003. It ran on WinNT machines with 64MB RAM, and it still runs today, just as well as it did originally, on Windows 7. Nobody has ever needed to work around any "issues". It just works.
The problem with code quality is that it is subjective. Some people (aka architecture astronauts) love complex, multi-tiered code with multiple classes and tons of inheritance.
Bite your tongue. You show me an architect that uses tons of inheritance and I'll show you a paste-eater.
Unnecessary complexity is the greatest sin you can commit in engineering. Quality is NOT subjective.
Slashdot Mirror
of how my grandfather would want it to work.
I remember when people were talking to him, he'd pointedly remove his hearing aids and look the other way.
He didn't give a damn, but he was the only one in the house the kids and the dogs would listen to.
Insults are the domain of the Democrats, have some couth. Republicans don't generally use insult as a substitute for rational thinking, that's a Democratic play.
"Heart rules the head", IOW emotional thinking, is what Democrats do.
Oh, and because there are no examples of the other party being like that at all.
Holy shit, dude.
This whole R versus D thing is highly destructive to intelligent discussion, especially when adding generalizations and ad-hominem.
Please get off Slashdot.
about rampancy.
-
about rampancy.
Liberal: "I want someone who'll fight for me."
Conservative: "I want someone who'll leave me the fuck alone."
Dividing everything into 'liberal' versus 'conservative' is highly corrosive substantive discussion.
And you could easily switch those quotes and have them work, by the way.
Each accident must have occurred during the generation, transmission, or distribution of nuclear energy. That includes accidents at mines, during transportation by truck or pipeline, or at an enrichment facility, a manufacturing plant, and so on.
Back in the day when I just started digitizing my CD's, if you'd asked me if I wanted some third party to have read/write access to my digital music library, I would have called you nuts.
I bought it, it's mine, and I don't need anyone to manage it for me, thank you very much. I still feel that way.
Now people are keeping the only copies of their music on devices that they don't control, running software they don't control.
And they want us to listen when they complain? Craziness.
Yet, you fail to give any explanation at all as to why bottom-posting is better. I think I clearly explained why I preferred top-posting. This was long before MS had an email client.
But your answer is just, "Because... Microsoft! BLARG!". You're exactly the kind of wignut I was talking about. You scream about why top-posting is wrong, but can never give any good reason why.
People eat McDonald's. They eat that, they'll eat anything.
to fight theocracy.
Under the terms of the agreement, Warner Bros. is banned from failing to disclose similar deals in the future
It's common email convention now, at least in my experience - when you respond to someone, you put your response on top, so as the conversation chain grows, the order is the most recent (and therefore the most pertinent) to the oldest, descending. So you don't have to scroll through pages just to see the last reply.
Back in the day, on newsgroups, if you did that you'd get absolutely SCREAMED at for "TOP POSTING", because it was WRONG.
From the guardians of all that is right and wrong.
I'd very much like to see a moderating system rating the editors.
although for all but the top maybe 10% of coders that's probably more important than anything. You're rank and file are just implementing biz logic after all. But don't forget that the ability to learn and adapt goes _down_ as you get older. It just does, and there's plenty of research to show this. An experienced programmer can crank out code he's already written faster, but so what. He's gonna want to work fewer hours and have more benefits. On the low end I can not only work those young guys half again as hard and pay them half as much. They cost less to give medical insurance for to boot. On the high end their ability to learn makes up for their lack of experience. The reason you were taught to respect your elders is they were smart enough to know they weren't needed anymore and you'd need an emotional reason drilled into you when you were mentally vulnerable or you'd kick 'em to the curb.
Wow, seriously? Pro-tip: go anonymous if you just want to troll.
On the off chance you actually mean that, I'm not going to even bother explaining to you what's wrong with your line of thinking. You don't understand software development at all.
Well... maybe you are a manager.
I agree that how one arrives at the social and economic structure of Star Trek is left to the imagination, but some of the presumably enabling elements, namely, the technology, are shown front-and-center. What will happen when everyone has access to a replicator that can make all the necessities of life - food, shelter, clothing - in as much abundance as anyone would ever need?
Maybe that will result in disaster the likes of which would strain the imagination... but maybe not.
Whatever the outcome, I'm pretty sure such technology would render the notions of 'capitalism' and 'communism' somewhat useless. Star Trek's socioeconomic ideas don't seem to be so out there as to be implausible.
Since it's pretty much a fact that you can work longer and harder when you're young. And it's not like experience is all that important in a brand new field. I understand why the working class is against it. We all get old but very few of us can stop working at 40. But I sorta wish we working class folks could be more honest about it and just admit we're protecting our own interests. There's absolutely nothing wrong with that but we act like we're doing something disdainful...
Programming isn't like shoveling coal - working harder and longer usually results in worse output. And experience can be a very strong productivity multiplier.
... what are you doing here?
If you had any tech experience at all you'd know this.
WatchMojo, one of the most popular channels of YouTube with over 12 million subscribers, has been hacked. Subscribers of one of YouTube's most popular channels, WatchMojo [...]
The amount of data that Microsoft has purchased, and will be able to harvest on a continual basis, has just increased by orders of magnitude.
Orders of magnitude? No.
For example, magazines and advertisements are targeted to the end of the week, so that people have more time for shopping dreams in the weekend.
Huh? Wouldn't delivery at the beginning of the week give people more time?
And what is this "shopping dreams in the weekend"? Is that a Finnish thing?
because it would show that the Great Filter (such as a planet-killing industrial accident) is not in front of us.
Forget beauty, whatever you or the next person thinks it is. Being that obese means that her children, if she has any, will be left without a mother rather early.
It's like smoking, or free-solo climbing. Sure, you can do it, it's a free country. But if you have people that love you and don't want you to die young, it's really not OK.
Not that I like or condone the language, but the old VB6 (and .NET WinForms) front-end designers (aside from missing CSS-like styling) remain better than what MS offers now... WPF, which is a total mess in terms of unnecessary complexity, or anything AT ALL targeting the train wreck we call HTML.
I'm talking in terms of applications where someone's trying to actually perform useful work, not "content consumption" / etc.
And don't give me that straw-man argument that you can't achieve good SoC without MVVM / MVC / M** and point to something from coding horror as an example.
-nothing comes even close to java in terms of stability. I will happily debug a war created in 2002 and figure out ways to work around old jdk issues.
It's sad that thick client gets completely ignored in the discussion.
.NET that I completed in 2003. It ran on WinNT machines with 64MB RAM, and it still runs today, just as well as it did originally, on Windows 7. Nobody has ever needed to work around any "issues". It just works.
I have a 100KLOC+ WinForms application written in
You want stability, don't target a browser.
The problem with code quality is that it is subjective. Some people (aka architecture astronauts) love complex, multi-tiered code with multiple classes and tons of inheritance.
Bite your tongue. You show me an architect that uses tons of inheritance and I'll show you a paste-eater.
Unnecessary complexity is the greatest sin you can commit in engineering. Quality is NOT subjective.
China has 4 people for every 1 in the US. That means all other things being equal, labor costs in China will be 1/4 that in the US on average.
Ugh math / economics fail gets +5 insightful.