In the article, in the upper right corner is a picture of a Red Cross truck. You know what my first thought was? Run into it and absorb it, full health!
I don't know if you meant to come off this way, but it sounds like you're not backing up the newspaper.
Fuck that. When it comes to things like this, it's everybody's problem who believes in free speech. I am by no means a warmonger, but if these people want to attack free speech, I don't care who's free speech they're attacking there's nothing else I want my tax dollars going to more than making sure NOBODY in the world fears violence in response to speech. And before anyone else says it, yeah, I want everyone to fear violence in response to violence. Double standard? No. Just like on the playground, "They started it!"
They have hot water heaters that heat it as it flows now. As long as now is the last 30 years or more... Anyway, pretty much cuts out the need for any complicated control equipment.
To be fair, graphics quality isn't like network throughput. You can't really say, "this screenshot is 20% better than that one." Things like bump-mapping and dynamic lighting may make only a small improvement in image quality but requires, to pull a number out of my ass, 3x the processing power.
Also, the bloated or slow code is a tradeoff. Maybe they traded it to get proper error handling or graceful degradation or to make it more easily extensible (unlikely). Maybe they traded it to get it into your hands a year earlier (likely). Even if you don't realize it, you are seeing a benefit from these tradeoffs (unlikely), unless you're dealing with a crap company (likely).
Re:Video Games
on
Demise of C++?
·
· Score: 2, Interesting
That's funny. I've written over 15,000 lines of C++ code over the last year in my spare time, and run it all through valgrind. Haven't had a memory leak yet. Using RAAI and the STL, I can't even think of a way I could get a memory leak... maybe if I leaked whole objects, but I apply the same discipline throughout my programs that I apply to memory allocation (of which I do very little).
As for buffor overflows, once again the STL helps a lot. For the rest of it, a little discipline goes a long way. Buffer overflows are a lot harder to reliably check for with automated tools, but I've gone over the code looking for them, and haven't found one yet. It's not that hard to program in a way that makes this stuff almost impossible, it's just not a lot of fun. My solution to that is to program the not very fun stuff in a real general and safe way so that I can reuse it and never have to write it again. Keeps you going if you know that when you're done you're done.
for (vector< double, My_alloc<double> > p = v.begin(); p!=v.end(); ++p) cout << *p << endl;
Should be:
for (vector< double, My_alloc<double> >::iterator p = v.begin(); p!=v.end(); ++p) cout << *p << endl;
Is what I originally meant to post... now if you mean reading the syntax... yeah, I know. You'll have a hard time finding a C++ programmer that really likes the syntax.
for (vector > p = v.begin(); p!=v.end(); ++p)
cout >::iterator p = v.begin(); p!=v.end(); ++p)
cout *p endl;
Hot damn, somebody get me a cookie, I found a mistake in Bjarne Stroustrup's code!
True, I'm not a big fan of it's default install location, but you can almost certainly change that. Well, since it's distributed in source form, even if it's not a config option it'd probably be pretty easy to change even if every path is hardcoded. You have to add a few new users, but pretty much every service on your machine should have its own locked down user. You have to install daemontools, but that's just a dependency, nothing new to us UNIX folks.
As for a constant stream of errors... chances are pretty good you messed something up. Not for nothing, but there's a reason that qmail hit 1.03 and stopped. The install and config process could use a bit of work, I'll admit that. It's not that bad though, and as it is if you successfully get qmail up and running it's almost as good as giving an IQ test to anyone who wants to run a mail server.
Slashdot Mirror
In Soviet Russia, I can think of a few ways I'm going to abuse you!
In the article, in the upper right corner is a picture of a Red Cross truck. You know what my first thought was? Run into it and absorb it, full health!
Let's hope I never see one on the freeway.
I don't know if you meant to come off this way, but it sounds like you're not backing up the newspaper.
Fuck that. When it comes to things like this, it's everybody's problem who believes in free speech. I am by no means a warmonger, but if these people want to attack free speech, I don't care who's free speech they're attacking there's nothing else I want my tax dollars going to more than making sure NOBODY in the world fears violence in response to speech. And before anyone else says it, yeah, I want everyone to fear violence in response to violence. Double standard? No. Just like on the playground, "They started it!"
Sure, because who give a shit about herpes and syphillis as long as it's not AIDS?
People fuck constantly, in every decade. If you're not doing as much as you'd like, do more. Wear a rubber.
They have hot water heaters that heat it as it flows now. As long as now is the last 30 years or more... Anyway, pretty much cuts out the need for any complicated control equipment.
Fun at work involves free cake and mandatory socialization.
Fun outside of work involves women jumping out of cakes and voluntary copulation.
You decide.
To be fair, graphics quality isn't like network throughput. You can't really say, "this screenshot is 20% better than that one." Things like bump-mapping and dynamic lighting may make only a small improvement in image quality but requires, to pull a number out of my ass, 3x the processing power.
Also, the bloated or slow code is a tradeoff. Maybe they traded it to get proper error handling or graceful degradation or to make it more easily extensible (unlikely). Maybe they traded it to get it into your hands a year earlier (likely). Even if you don't realize it, you are seeing a benefit from these tradeoffs (unlikely), unless you're dealing with a crap company (likely).
--ESR
... "Social Responsibility," I want to reach for my gun.
Hold the lighter sideways?
Well, yeah, but only if your local resivoir is made of orange juice.
It's benign and malicious. Malign means to villify, or to damage their reputation in some way.
I am intrigued by your ideas and would like to subscribe to your newsletter.
What the fuck guys God damn it.
Or just put a lit cigarette in there on a plate and save yourself an hour.
I knew there was a reason I didn't like Python.
That's funny. I've written over 15,000 lines of C++ code over the last year in my spare time, and run it all through valgrind. Haven't had a memory leak yet. Using RAAI and the STL, I can't even think of a way I could get a memory leak... maybe if I leaked whole objects, but I apply the same discipline throughout my programs that I apply to memory allocation (of which I do very little).
As for buffor overflows, once again the STL helps a lot. For the rest of it, a little discipline goes a long way. Buffer overflows are a lot harder to reliably check for with automated tools, but I've gone over the code looking for them, and haven't found one yet. It's not that hard to program in a way that makes this stuff almost impossible, it's just not a lot of fun. My solution to that is to program the not very fun stuff in a real general and safe way so that I can reuse it and never have to write it again. Keeps you going if you know that when you're done you're done.
The “mirror finish” is on the other side of the glass.
for (vector< double, My_alloc<double> > p = v.begin(); p!=v.end(); ++p)
cout << *p << endl;
Should be:
for (vector< double, My_alloc<double> >::iterator p = v.begin(); p!=v.end(); ++p)
cout << *p << endl;
Is what I originally meant to post... now if you mean reading the syntax... yeah, I know. You'll have a hard time finding a C++ programmer that really likes the syntax.
Oh, poetic justice, I hate you.
for (vector > p = v.begin(); p!=v.end(); ++p) cout >::iterator p = v.begin(); p!=v.end(); ++p) cout *p endl; Hot damn, somebody get me a cookie, I found a mistake in Bjarne Stroustrup's code!
It's a limey way of saying salt-shaker.
How does qmail eat your computer?
True, I'm not a big fan of it's default install location, but you can almost certainly change that. Well, since it's distributed in source form, even if it's not a config option it'd probably be pretty easy to change even if every path is hardcoded. You have to add a few new users, but pretty much every service on your machine should have its own locked down user. You have to install daemontools, but that's just a dependency, nothing new to us UNIX folks.
As for a constant stream of errors... chances are pretty good you messed something up. Not for nothing, but there's a reason that qmail hit 1.03 and stopped. The install and config process could use a bit of work, I'll admit that. It's not that bad though, and as it is if you successfully get qmail up and running it's almost as good as giving an IQ test to anyone who wants to run a mail server.
He's saying that men act dumb around women, just replace dumb with -20IQ and women with XX.
Maybe you just haven't been around... humans... much, but both that joke has been around since they painted "For Better or for Worse" on cave walls.
Don't worry. Whether you blow her up or not, one of the two of you definitely has the gene.