>May be you are more lazy _THAN_ the guy that learn English as a second language.
And you must be lazier than the guy that _LEARNED_ English as a second language.
>If you don't even know these two, then you are not qualify to be on slashdot.
I guess you're even less _QUALIFIED_ to be on Slashdot.
Losing your job to Bender: technological progress.
If you lost your job to Bender it means you're even lazier then the guy who accept packages at the moon amusement park
Yes, because in this vast world there is only the singular good coder and everyone else is lousy or a student.
When the exact specs only exist on two manufacturer's machines, for example, and both only offer it with Windows installed, and jack the price $40 because of it, where is my choice?
I guess you just don't have one. Those computer manufacturers have no obligation to sell you a product.
No, he was saying that if you weren't a C++ programmer that you should leave the industry as if being able to program C++ and knowing pointers and memory management was some sort of godlike skill. The people who bluster on about how they know about memory management and pointers are usually the ones who write some of the leakiest code around.
But Amazon is reprinting these books they aren't providing digital copies. So, yes, they are probably going to charge something to cover the costs of printing.
Yes, but this frontend uses about 75 megs of RAM without anything running. When it's actually doing something it uses around 175 megs of RAM. The fact that Firefox can use more on start up with no tabs open is not a positive for Firefox.
I've seen such horrible Java programs from new programmers because they are never taught ANYTHING about memory management.
Well but that can be said of programs written in any language. It's not a language or frameworks fault if you can't write good code. There is nothing inherent to Java, C#, etc that mean that your program HAS to be bloated or use a lot of memory. Most of the time it happens for the same reason you see bloated and memory leaky C/C++ program: programmer inexperience or laziness.
"don't want to deal with them"?
In all programs, yes sometimes you don't want to deal with them when you can use a language feature to simplify things. Dealing with new/deletes, etc is both a tedious task and can be very error prone as one can see by the number of C++ programs that have memory leak issues. Now this isn't to say that there aren't cases where you have to do it because of critical performance reasons.
it's perfectly fine to optimize development time, but this trend of offloading excess work onto users platform is unacceptable.
It's unacceptable to use a built-in language feature, such as auto_ptr, to help to reduce the amount of memory leaks? Huh?
The rest of your post has no relevance at all to what I was talking about. I wasn't proclaiming that one shouldn't ever manage their memory manually or that you shouldn't care about performance or the quality of your code because hardware will get faster to make up for it. You seem to be ranting at someone else or else your turning my post into some sort of strawman.
Then use a framework, like Qt, that deals with all of that for you.
Or I can just use a built-in language feature like auto_ptr which takes away most of what you used to have to do manually.
Just because you don't need to mess around with pointers, that doesn't mean everyone doesn't need to.
Great. I never made any such claim. Are you arguing against someone else with that sentence?
Yes, but since every Java and
Yes, Azureus is a crappily written program. The point though is that I've seen it running with 10+ torrents for the same amount of time as Firefox and it still uses less memory. The point was that this whole notion that only Java and
So you are both right: garbage collection that doesn't get enough data from the programmer sucks, and programmers that rely upon it suck - but auto_ptr and Boost's smart_ptr's don't belong to that category.
Yes, relying on a garbage collector that you and the GP describe which is about 10-15 years out of date would make you a sucky programmer. Fortunately for us, though, GCs have gotten much better since then.
Are any of those
The apps I am using store lots of what they are working in in local memory. One of them is a karaoke subtitle editor which holds the audio in ram, the other is a bittorrent client and one is actually a pretty bloated
First: OO.o is Java.
Bzzzt wrong. Look at the code, it's 98% or so C++. The only parts that are Java are some database access layers and some stuff for multimedia. Way to show yourself as being an idiot for repeating this oft-repeated and incorrect meme.
Second: The language has little to no bearing on the amount of RAM being used. The amount of data being stored (and how it's stored), however, does. Firefox stores a lot of images and such, which, surprise surprise, eat up RAM.
So then you've just effectively nullified your own point since you were blaming the languages on the bloat instead of the crappy programmers.
What is wanted is not the will to believe, but the will to find out, which is the exact opposite. -- Bertrand Russell, "Skeptical Essays", 1928
