Task manager shows you working set size. The working set will be trimmed when you minimize the app or call SetProcessWorkingSetSize() to trim it yourself manually (thats what the OS does when you minimize something). Additionally if the system needs the memory it will decrease the working set as necessary. So that isn't necessarily memory usage per se, you could think of it as iTouch 'touched' 15MB of memory (whether it involved DLLs being loaded, runtime engines such as Java or.NET bootstrapping, and accessing large resources). Apps that are skinned (such as Trillian) usually have a much higher working set size than normal, this is part of the reason (and don't get me started on Trillian's quality).
This is what I understand, someone may know more...please correct me if I am wrong somewhere.
Not many routers support it yet, but supposedly WPA is going to be a step above WEP. I'm wondering if anyone has actually tried using it yet? I'm running 64-bit WEP here and the inherent insecurity of the protocol makes me leery.
How elitist can you get? The technology is just a means to an end, not an end of itself. The fact that more people use and appreciate PCs now is a testament to the improvements in usability engineering.
This seems obvious, but I'll bite. How about instead of taking all that crap with you by default, you *only* bring what you'll absolutely need. If you have your laptop with you, for example, do you really need your iPod? Or a PDA? Practically everyone carries a cell phone around nowadays, so I unless you have a riced out one, I don't think the cell phone is as much of a problem as the other big ticket items.
If you must carry it all around, I suggest concealing it in a similar manner as you did with the iPod earphones. Be careful of where you flash your toys around. If, for example, you take your iPod to lunch with you, then when you get up to grab a handful of napkins, stick that sucker in your pocket, not in your bag. Be cautious, but not paranoid. And, it should go without saying, but if you're worried about muggers, don't walk around with headphones on.
Even though he mentions Linux as a possible solution in providing DIY telcos, it doesn't automatically make his points legitimate, much as the editors would love you to believe. It appears that yet again he is off in lala land.
One more established form of media just disparages another because it doesn't understand it, or because it fears it. It's a shame, because average newspaper readers inevitably equate, "IRC = bad," and continue to spread the hearsay when it comes up in conversation.
What are they smoking, anyways? The web is anything but a well-policed suburb. If anything, it's a middle school that is in perpetual recess. They just know if they were to apply these same arguments to the web that people would not stand for their bullshit.
Once again, social acceptability shows itself to be completely arbitrary.
Well said. C++ being misunderstood doesn't affect my perception of the language. It is a "kitchen-sink" language that has a TON of depth. It has a lot of idiosyncrasies, and can be extremely unforgiving in the wrong hands. Despite it seeming like a confused, multi-paradigm high/low level language, I like the amount of choice it offers me, I feel more expressive. On the other hand, Java's conscious design policy to scale the language down to the absolute minimal subset that average programmers can use is insulting.
I am also looking forward to the D language as a simplified, GC'd C++.
I downloaded Eclipse and the C++ tools but couldn't get anything like VS.NET's IntelliSense -- is it not supported for Eclipse? I use VS.NET 2003 regularly, but it has this aggravating tendency to freeze up for 5-10 seconds at a time very occasionally. That, and my project broke the IntelliSense, too.:)
You've given me one case where print statements are better than a debugger. OK, that still doesn't prove that debuggers are worthless, as the original poster implied.
Ah yes, those damn errors in hardware are surely remedied by printf! Plus, there's tons of buggy hardware floating around that invalidates formal methods! And whose blasted compiler writers sure aren't very good, we might as well write our own compiler! Who needs mathematical proofs of correctness when we can have printf's strewn everywhere? And I'm sure its completely impossible to use BOTH formal methods and printf's!
I fail to see how stack traces are self-healing software. The program still crashes, self-healing implies that it would somehow get around the error and continue execution at some point.
Ah, nothing like claiming that your way of approaching something is the only way. A debugger is just a tool. Like any other tool it can be bad if it is misused, and it isn't appropriate for every situation. I find a debugger invaluable for jumping into someone else's code and seeing exactly what is happening step-by-step. Debuggers can be great if you suspect buffer overflows and don't have access to more sophisticated tools that would detect it for you. Just yesterday I used a debugger to modify values in real-time to test code coverage.
Inserting printf statements into the code is probably not logging - usually if you are debugging they are destined for removal anyway. I use a logging system that shows the asynchronous, high-level overview of events being dispatched and then can use the debugger to zero in on the problem very quickly without recompiliation. In addition if a test machine screws up I can remotely debug it.
If you want to throw out debugging because Linus isn't a fan of it, be my guest. But I'm not a fan of wasting time, and injecting print statements into the code plus recompiling is a waste of time and ultimately accomplishes close to the same thing as debugging. Any decent IDE will let you slap a breakpoint down and execute to that point quickly. But I assume someone will come along and tell me that IDEs are for the weak as well.
Slashdot Mirror
As expected, they list gimp as an equivalent to Photoshop. I'm guessing the author doesn't deal with that pesky reality much.
And michael passes it on as if it were news! The circle is complete!!!
Being a researcher is far more fulfilling than sitting in your parents basement posting on Slashdot about how Linux is ready for the desktop.
This is probably the ultimate /. circle jerk there is.
How about upgrading your userid to be something non-DBZ? ;)
Now we can all talk about how our favorite operating system would NEVER have something like this happen! I love this site!
Why in hell would MS be behind this when .NET is ramping up to full steam? At least try to make sense when you post something!
Oh wait, this is Slashdot.
Task manager shows you working set size. The working set will be trimmed when you minimize the app or call SetProcessWorkingSetSize() to trim it yourself manually (thats what the OS does when you minimize something). Additionally if the system needs the memory it will decrease the working set as necessary. So that isn't necessarily memory usage per se, you could think of it as iTouch 'touched' 15MB of memory (whether it involved DLLs being loaded, runtime engines such as Java or .NET bootstrapping, and accessing large resources). Apps that are skinned (such as Trillian) usually have a much higher working set size than normal, this is part of the reason (and don't get me started on Trillian's quality).
This is what I understand, someone may know more...please correct me if I am wrong somewhere.
Not many routers support it yet, but supposedly WPA is going to be a step above WEP. I'm wondering if anyone has actually tried using it yet? I'm running 64-bit WEP here and the inherent insecurity of the protocol makes me leery.
How elitist can you get? The technology is just a means to an end, not an end of itself. The fact that more people use and appreciate PCs now is a testament to the improvements in usability engineering.
This seems obvious, but I'll bite. How about instead of taking all that crap with you by default, you *only* bring what you'll absolutely need. If you have your laptop with you, for example, do you really need your iPod? Or a PDA? Practically everyone carries a cell phone around nowadays, so I unless you have a riced out one, I don't think the cell phone is as much of a problem as the other big ticket items.
If you must carry it all around, I suggest concealing it in a similar manner as you did with the iPod earphones. Be careful of where you flash your toys around. If, for example, you take your iPod to lunch with you, then when you get up to grab a handful of napkins, stick that sucker in your pocket, not in your bag. Be cautious, but not paranoid. And, it should go without saying, but if you're worried about muggers, don't walk around with headphones on.
Even though he mentions Linux as a possible solution in providing DIY telcos, it doesn't automatically make his points legitimate, much as the editors would love you to believe. It appears that yet again he is off in lala land.
Yes, but that requires that they leave their parents basement. :)
Why not a contest to see who can devise the best space-related contest, complete with rules. I think it would be positively groundbreaking!
One more established form of media just disparages another because it doesn't understand it, or because it fears it. It's a shame, because average newspaper readers inevitably equate, "IRC = bad," and continue to spread the hearsay when it comes up in conversation.
What are they smoking, anyways? The web is anything but a well-policed suburb. If anything, it's a middle school that is in perpetual recess. They just know if they were to apply these same arguments to the web that people would not stand for their bullshit.
Once again, social acceptability shows itself to be completely arbitrary.
Well said. C++ being misunderstood doesn't affect my perception of the language. It is a "kitchen-sink" language that has a TON of depth. It has a lot of idiosyncrasies, and can be extremely unforgiving in the wrong hands. Despite it seeming like a confused, multi-paradigm high/low level language, I like the amount of choice it offers me, I feel more expressive. On the other hand, Java's conscious design policy to scale the language down to the absolute minimal subset that average programmers can use is insulting.
I am also looking forward to the D language as a simplified, GC'd C++.
I downloaded Eclipse and the C++ tools but couldn't get anything like VS.NET's IntelliSense -- is it not supported for Eclipse? I use VS.NET 2003 regularly, but it has this aggravating tendency to freeze up for 5-10 seconds at a time very occasionally. That, and my project broke the IntelliSense, too. :)
Real programmers don't believe they have to do arbitrary things because "Elwood P Dowd" said so.
Let the condescending remarks about operating systems begin!
You've given me one case where print statements are better than a debugger. OK, that still doesn't prove that debuggers are worthless, as the original poster implied.
There goes your karma forever for implying that C is unnecessarily low-level. That is, saying nothing of implying that Unix isn't a perfect OS.
What tripe.
Ah yes, those damn errors in hardware are surely remedied by printf! Plus, there's tons of buggy hardware floating around that invalidates formal methods! And whose blasted compiler writers sure aren't very good, we might as well write our own compiler! Who needs mathematical proofs of correctness when we can have printf's strewn everywhere? And I'm sure its completely impossible to use BOTH formal methods and printf's!
I fail to see how stack traces are self-healing software. The program still crashes, self-healing implies that it would somehow get around the error and continue execution at some point.
Ah, nothing like claiming that your way of approaching something is the only way. A debugger is just a tool. Like any other tool it can be bad if it is misused, and it isn't appropriate for every situation. I find a debugger invaluable for jumping into someone else's code and seeing exactly what is happening step-by-step. Debuggers can be great if you suspect buffer overflows and don't have access to more sophisticated tools that would detect it for you. Just yesterday I used a debugger to modify values in real-time to test code coverage.
Inserting printf statements into the code is probably not logging - usually if you are debugging they are destined for removal anyway. I use a logging system that shows the asynchronous, high-level overview of events being dispatched and then can use the debugger to zero in on the problem very quickly without recompiliation. In addition if a test machine screws up I can remotely debug it.
If you want to throw out debugging because Linus isn't a fan of it, be my guest. But I'm not a fan of wasting time, and injecting print statements into the code plus recompiling is a waste of time and ultimately accomplishes close to the same thing as debugging. Any decent IDE will let you slap a breakpoint down and execute to that point quickly. But I assume someone will come along and tell me that IDEs are for the weak as well.
Could have fooled me, it seems like everyone here sits around and whines about everything on Earth. :)