Why? Because sprinters - and all pro runners - wear running shoes and they make running somewhat more efficient than running barefoot. I'd wager money on very few if any sprinters being able to do 100m in under 10 sec if running barefoot.
Exactly. But then the fluffy rehabilitation brigade are pathalogically wedded to their arrogant almost religious belief that everyone is a good person at heart and can be rehabilitated given the right circumstances. They simply won't accept that some people are born evil and need to be locked up for life or executed for the safety of the public. And many people have paid the price for that arrogance.
"In case you ever doubted what rich liberals think about you, note the above:"
Nice try , except I'm not rich or a liberal. But I do prefer to believe scientific consensus over the opinions of brainless rednecks who's highest intellectual achievement is changing the carb on their 10mpg V8s.
The knuckle dragging idiots that make up 90% of humanity on this planet can just about grasp that a huge explosion with lots of radioactivity is a very bad thing. However trying to persuade them that climate change that may or may not affect their lives in a few decades time is also a very bad thing is rather an uphill task. Mainly because they don't understand the science but also because a lot of them think its all a conspiracy by The Man (tm) to control what they do. And then of course we have the Ostrich approach to problem solving - just hope it goes away.
Cloud is just a marketing term for credulous idiots that means stored in a datacentre with redundancy and failover. "Cloud" style services have been around for 20 years, long before suckers like you even knew what a real cloud was.
... someone who doesn't follow the current orthodoxy in the Liberal religion. And lets not pretend liberalism is still merely a political and/or social stance - its religion in all but name as demonstrated by its followers who instead of debate simply resort to unpleasent ad hominem attacks (and in some cases actual attacks) on anyone who goes against their beliefs.
And no religious nutjobs - that doesn't mean I'm on your side either. I simply can't stand people who substitute brainwashed in emotion for rational thinking.
"I think compiled languages are impractical for web environments, for reasons everyone can come up with, so that rules out C and C++. "
Yes - C & C++ are complex, hard to learn and require a deeper understanding of a computer than browser documents, which pretty much rules out web "developers" being able to use them. Is that one of the reasons you were thinking of?
Mono on linux is pretty much dead so C# is more or less a Windows only language now making it a locked in dead end for developers who don't want to be tied to the MS upgrade treadmill all their working lives.
As for your other points, C++ is easy to maintain if you're competant in the language and as for hacking - remind me what happens if there's a vulnerability in a VM? Oh thats right , every single fucking program running on it is potentially screwed , thats what.
"You asked "WTF I meant", I replied and your response is "syntactic sugar". Okey dokey."
I thought you meant something fundamentally important. My mistake obviously.
"The data you're working on basically makes up almost all of the memory"
You mean just like in financials? And what?
"(a) buggering around with processes and manually sharing almost everything"
WTF are you on about "manually sharing everything"? Do you have a clue how proper shared memory actually works or have you spent so much of your life programming Windows that all you have is a rusty hammer so everything looks like a nail?
As for buggering about with them, I doubt you'd even know where to start.
"(c) writing #pragma parallel for and letting the compiler do all the difficult, tedious work."
LOL, yeah, ok , run along , I think you're late for your lecture.
Isn't part of the point of visiting a remote location such as this the fact that you're at arms length from civilisation? Or are people so fucking shallow now that climbing the worlds tallest mountain is nothing without being able to tweet about it to other vacuous morons from the top?
"Therefore if you've got qsort in the middle of function foo(), then the definition (not declaration) of the comparator passed as a function pointer has to be either before or after foo(), i.e. a long way from where the qsort is actually called."
A long way perhaps being a few lines?
"And of course they work delightfully well with threads."
Who cares, sensible coders use multi process anyway and avoid all that shit. Well, unless they're hobbled by an OS that doesn't really support it properly such as Windows.
"It turns out that your C code has lots of bugs in it of which you are unaware. I know this because you think C is a simple language."
And I know you're a lousy programmer because you think it isn't. C is a simple language - however that is not the same as saying any potential bugs in C code are simple. A subtle difference that apparently eludes you - as does learning C it would seem.
Half the problems with threads are due to unintended consequences of sharing run paths and globals/statics in the program and in libraries. If a process can only communicate with another process via specific memory addresses and it doesn't shared ANY other data or run path then the unintended consequences will be much reduced.
"e.g. you communicate over pipes or sockets - then your statement would make more logical sense"
Yes , but they're stream based , they don't really emulate thread intercommunication and are generally only useful for fairly disconnected processes , not ones that need very tight integration.
"However it provides very little opportunity for automating common programming tasks, which means that everything has to be done by hand"
There are these amazing things called "libraries" and "macros". You should check them out sometime.
"old war stories from the days of your chasing down some evil pointer bug in a C or ASM program."
I've had plenty of those - never had one that I couldn't solve.
"Basically what you said amounts to daying"
No, it isn't. But if thats what you think then you nicely proved my point about finding another vocation since you can't obviously differentiate between run of the mill bugs and bugs caused by incompetence.
"It turns out that the world has moved on and knowledge has advanced."
It also turns out that CPUs still work in very much the same way. If you want to play with flavour of the moment language paradigms there are plenty of languages out there used by 3 people and a very smart dog that will suit you fine. There's no need to throw them into the C++ soup.
"And besides, I like not having to type needlessly long and verbose things like"
I take it you've never heard of macros then. (And spare me the spawn of the devil speech , thats only spouted by people who have no idea how to use them properly)
"And the lambdas. "
Syntactic sugar that has the added bonus of making code LESS readable in a lot of circumstances and have been added to solve problems created by using functors instead of just plain old function pointers.
"The thing is that all languages start off nice and simple. The world however is never simple."
Odd how the Linux kernel is written in C then. How did they do it without all these fancy features?
C is a fairly simple language to code in and debug. If you have problems with pointers - ie memory addressing - then seriously , find another vocation or stick to HTML because programming computers is not for you.
All the advantages of multi threading (assuming you use shared memory) but few of the disadvantages. The only reason multi threading has become popular is because its been advocated by Windows coders since Windows as an OS doesn't really lend itself to proper multi process applications in the same way that Unix does. Even in 2013 Windows still doesn't support fork(). Its a bit pathetic really.
Slashdot Mirror
The problem is if you make sport a performance drugs free for all then people are going to overdose and kill themselves. Its better the way it is.
Why? Because sprinters - and all pro runners - wear running shoes and they make running somewhat more efficient than running barefoot. I'd wager money on very few if any sprinters being able to do 100m in under 10 sec if running barefoot.
Exactly. But then the fluffy rehabilitation brigade are pathalogically wedded to their arrogant almost religious belief that everyone is a good person at heart and can be rehabilitated given the right circumstances. They simply won't accept that some people are born evil and need to be locked up for life or executed for the safety of the public. And many people have paid the price for that arrogance.
Since falsifying in this case is effectively proving a negative - ie demonstrate its NOT going to happen.
Obviously the person who modded you up is as clueless as you are.
"In case you ever doubted what rich liberals think about you, note the above:"
Nice try , except I'm not rich or a liberal. But I do prefer to believe scientific consensus over the opinions of brainless rednecks who's highest intellectual achievement is changing the carb on their 10mpg V8s.
"If they were honest, why are they calling it "Climate Change" now, rather than Global Warming? "
Actually nubnuts the scientists just do the science - blame the media for all the different phrases.
Now do you actually have anything useful to contribute or is playing silly semantic games your best shot?
The knuckle dragging idiots that make up 90% of humanity on this planet can just about grasp that a huge explosion with lots of radioactivity is a very bad thing. However trying to persuade them that climate change that may or may not affect their lives in a few decades time is also a very bad thing is rather an uphill task. Mainly because they don't understand the science but also because a lot of them think its all a conspiracy by The Man (tm) to control what they do. And then of course we have the Ostrich approach to problem solving - just hope it goes away.
Cloud is just a marketing term for credulous idiots that means stored in a datacentre with redundancy and failover. "Cloud" style services have been around for 20 years, long before suckers like you even knew what a real cloud was.
"If you think "cloud" is just a rebranding of colocation or even managed hosting, you really have a lot of learning to do."
Boy, have you ever drunk the Kool Aid and then some.
"Just because it's hyped up doesn't mean there's nothing real there. Cloud hosting is a sea change."
Remind us what happened to Azure a while back....
Is it? That shows what you know about whats going on in the world could be written on the back of your single lonely braincell.
... someone who doesn't follow the current orthodoxy in the Liberal religion. And lets not pretend liberalism is still merely a political and/or social stance - its religion in all but name as demonstrated by its followers who instead of debate simply resort to unpleasent ad hominem attacks (and in some cases actual attacks) on anyone who goes against their beliefs.
And no religious nutjobs - that doesn't mean I'm on your side either. I simply can't stand people who substitute brainwashed in emotion for rational thinking.
"I think compiled languages are impractical for web environments, for reasons everyone can come up with, so that rules out C and C++. "
Yes - C & C++ are complex, hard to learn and require a deeper understanding of a computer than browser documents, which pretty much rules out web "developers" being able to use them. Is that one of the reasons you were thinking of?
Mono on linux is pretty much dead so C# is more or less a Windows only language now making it a locked in dead end for developers who don't want to be tied to the MS upgrade treadmill all their working lives.
As for your other points, C++ is easy to maintain if you're competant in the language and as for hacking - remind me what happens if there's a vulnerability in a VM? Oh thats right , every single fucking program running on it is potentially screwed , thats what.
"You asked "WTF I meant", I replied and your response is "syntactic sugar". Okey dokey."
I thought you meant something fundamentally important. My mistake obviously.
"The data you're working on basically makes up almost all of the memory"
You mean just like in financials? And what?
"(a) buggering around with processes and manually sharing almost everything"
WTF are you on about "manually sharing everything"? Do you have a clue how proper shared memory actually works or have you spent so much of your life programming Windows that all you have is a rusty hammer so everything looks like a nail?
As for buggering about with them, I doubt you'd even know where to start.
"(c) writing #pragma parallel for and letting the compiler do all the difficult, tedious work."
LOL, yeah, ok , run along , I think you're late for your lecture.
Isn't part of the point of visiting a remote location such as this the fact that you're at arms length from civilisation? Or are people so fucking shallow now that climbing the worlds tallest mountain is nothing without being able to tweet about it to other vacuous morons from the top?
"C does not support local functions."
Syntactic sugar.
"Therefore if you've got qsort in the middle of function foo(), then the definition (not declaration) of the comparator passed as a function pointer has to be either before or after foo(), i.e. a long way from where the qsort is actually called."
A long way perhaps being a few lines?
"And of course they work delightfully well with threads."
Who cares, sensible coders use multi process anyway and avoid all that shit. Well, unless they're hobbled by an OS that doesn't really support it properly such as Windows.
"Secondly, single use functions have to be defined very far away from the place that they are used"
Eh? Wtf are you talking about?
"Firstly, function pointers don't have state"
You've never heard of static variables I take it.
"Odd that they pyramids are build of stone. How did they do it without modern tech?"
Probably not the best analogy - the pyramids will still be around long after most steel and concrete buildings have rusted away or crumbled to dust.
"It turns out that your C code has lots of bugs in it of which you are unaware. I know this because you think C is a simple language."
And I know you're a lousy programmer because you think it isn't. C is a simple language - however that is not the same as saying any potential bugs in C code are simple. A subtle difference that apparently eludes you - as does learning C it would seem.
Half the problems with threads are due to unintended consequences of sharing run paths and globals/statics in the program and in libraries. If a process can only communicate with another process via specific memory addresses and it doesn't shared ANY other data or run path then the unintended consequences will be much reduced.
"e.g. you communicate over pipes or sockets - then your statement would make more logical sense"
Yes , but they're stream based , they don't really emulate thread intercommunication and are generally only useful for fairly disconnected processes , not ones that need very tight integration.
"Spawning a new thread in most Unixes takes a small fraction of the time to spawn a new process"
Look up copy on write.
"And memory sharing, locking, communication are better at the thread level."
Bollocks. And you do know you can use mutexes in shared memory, right?
"However it provides very little opportunity for automating common programming tasks, which means that everything has to be done by hand"
There are these amazing things called "libraries" and "macros". You should check them out sometime.
"old war stories from the days of your chasing down some evil pointer bug in a C or ASM program."
I've had plenty of those - never had one that I couldn't solve.
"Basically what you said amounts to daying"
No, it isn't. But if thats what you think then you nicely proved my point about finding another vocation since you can't obviously differentiate between run of the mill bugs and bugs caused by incompetence.
"It turns out that the world has moved on and knowledge has advanced."
It also turns out that CPUs still work in very much the same way. If you want to play with flavour of the moment language paradigms there are plenty of languages out there used by 3 people and a very smart dog that will suit you fine. There's no need to throw them into the C++ soup.
"And besides, I like not having to type needlessly long and verbose things like"
I take it you've never heard of macros then. (And spare me the spawn of the devil speech , thats only spouted by people who have no idea how to use them properly)
"And the lambdas. "
Syntactic sugar that has the added bonus of making code LESS readable in a lot of circumstances and have been added to solve problems created by using functors instead of just plain old function pointers.
"The thing is that all languages start off nice and simple. The world however is never simple."
Odd how the Linux kernel is written in C then. How did they do it without all these fancy features?
C is a fairly simple language to code in and debug. If you have problems with pointers - ie memory addressing - then seriously , find another vocation or stick to HTML because programming computers is not for you.
Cue angelic chorus and a halo appearing over your head.
Meanwhile the rest of us just get on with enjoying our lives...
All the advantages of multi threading (assuming you use shared memory) but few of the disadvantages. The only reason multi threading has become popular is because its been advocated by Windows coders since Windows as an OS doesn't really lend itself to proper multi process applications in the same way that Unix does. Even in 2013 Windows still doesn't support fork(). Its a bit pathetic really.