The article was a little vague about the exact process for getting certified. Since it's going to be run by TRUSTe, I imagine that this won't be for free...
Well, at least this certification only affects the software that gets distributed by AOL, Yahoo!, CNet, etc. I just wonder if this isn't the start of some sort of "trusted computing".
IIRC, graphite from pencils is dangerous to have floating around in an enclosed area. Graphite is a conductor and could harm the many electrical components inside the space capsule.
After a little googling, I found this (scroll down the page a bit to find the explaination) which explains a little more about it.
Too true. In defense of the original programmers, who would have thought that someone would purposely write bad image files in order to run arbitrary code?
On the other hand, I suppose that they could have considered the possibility of corrupted files.
Computer security methods have changed over the years. The code base just needs to catch up.
A busted window, while quite the nice irony, has no bearing here. If Ford released a car that *any* key would open and start then you'd have a comparison.
I still think it does. Once I take my car out of the garage, it becomes vulnerable to any amount of damage. Why, someone could damage my car by "keying it" with a key that's not even mine!
Uh huh. And check for stack overflow? Or do you work in Redmond?
Stack overflow is handled the same way the an out of memory error is handled - with an exception.
And then are you planning to free the storage?
Free the storage on the stack? The storage on the stack is automatically released when the function call has ended. The compiler can also increment the stack pointer as well to release the top of the stack.
How many operations do you think GC takes? Did you read the reference? Of course not.
I have not read the reference, but I do know that garbage collection has overhead associated with it. Overhead from the function call to the GC, overhead from the operating system when the program requests a block of memory, and overhead from the book-keeping that the GC must do to keep track of that memory.
Bottom line: Stack allocation is always faster, but it's not always the best option. Dynamic memory allocation is much more useful at times.
I see that you don't have an understanding of assembly code.
Every function has a stack frame. The compiler generates one for every function. It only takes one operation to allocate some memory on the stack, just decrement the stack pointer.
As far as I can see, there is nothing more efficient than one assembly operation.
I'm currently in a class that uses clickers. It's a physics class held in a large (100+) lecture hall.
The professor uses them to mostly keep track of attendance by having the students answer simple quizes. Since each clicker has it's own internal ID number, the clickers allow the professor to quickly determine who's coming to class.
I really didn't like the price ($25 used) for the clickers, but I can see why some professors have them. Besides attendance, it is a quick way of having the class take a quick quiz during class.
It's an interesting idea to convince your employees and even store managers that you are capable of doing something technically impossible, presumably with the hope that it'll trick your customers too.
The point is that some (or most?) people will believe those stories, and be deterred from copying.
Well, no. What we need is for programs to have very specific sets of permissions that they operate under. Screensavers, for instance, generally should have permissions to do nothing but write to the screen and (depending on how the screensaver system works) read from the keyboard/mouse. They shouldn't be able to read or write any files, and they shouldn't be able to connect to the network.
What if the user wants a screensaver that downloads new pictures to display from the internet?
The problem is that definitions of what a program can/should do change often.
Step one:
Get a bunch of school buses. This should be easy as hell. There's probably over two hundred just in my county (although I'm not nearby).
The New Orleans buses are underwater. I imagine that many of the buses in the area are damaged as well, if they already weren't used to evacuate people.
Step two:
Put food on the buses and drive the to New Orleans. This should take ONE DAY.
Drive on what roads? The Hurricane didn't just destroy New Orleans. A bus carrying people overturned just the other day, killing at least one. The roads are in really bad shape.
But did you look at the results? One was a post by someone named "Infinite Loop", and some of the others were explaining an old problem, and some were not about it at all.
Because that approach would take too much fuel. I believe that NASA tries to calculate a launch pattern that more or less "slings" the object in an arc that will meet up with Mars after the necessary months of travel.
I didn't read the article above, but the Los Angeles Times mentioned that HP will be selling them until they run out of stock, which should be sometime in September.
Why is it unavoidable? if a driver crashes, the OS should just block the device and continue with its work, no blue screens or kernel panics or whatever, a driver malfunction is JUST a program malfunction, if the OS does not mange fine the hardware drivers then it is not 'operating' well.
What if the video card driver fails? (which happens often when I'm pushing the graphics card) I don't want the OS to keep on going. I think some errors and malfunctions need to cause the OS to shutdown, especially if the error could cause data corruption.
At least Microsoft offers their command-line version of the Visual Studio C++ compiler as a free download on their website. Unfortunately, they don't offer an IDE.
I do agree that it would be nice if books on the subject were less expensive. Paying $60 or more for a book is a little prohibitive.
Slashdot Mirror
The article was a little vague about the exact process for getting certified. Since it's going to be run by TRUSTe, I imagine that this won't be for free...
Well, at least this certification only affects the software that gets distributed by AOL, Yahoo!, CNet, etc. I just wonder if this isn't the start of some sort of "trusted computing".
After a little googling, I found this (scroll down the page a bit to find the explaination) which explains a little more about it.
Too true. In defense of the original programmers, who would have thought that someone would purposely write bad image files in order to run arbitrary code?
On the other hand, I suppose that they could have considered the possibility of corrupted files.
Computer security methods have changed over the years. The code base just needs to catch up.
I still think it does. Once I take my car out of the garage, it becomes vulnerable to any amount of damage. Why, someone could damage my car by "keying it" with a key that's not even mine!
No, it's called MSDNAA.
I was amazed to learn that as a CS student I could download Windows XP, 2003 server, etc. for free.
One you're there, you can change all the grammer settings you want (like fragment checking).
You might want to experiement some of the more interesting grammer checking such as cliche and/or wordiness checking.
So that's why the robots in Futurama belched flames!
Stack overflow is handled the same way the an out of memory error is handled - with an exception.
And then are you planning to free the storage?
Free the storage on the stack? The storage on the stack is automatically released when the function call has ended. The compiler can also increment the stack pointer as well to release the top of the stack.
How many operations do you think GC takes? Did you read the reference? Of course not.
I have not read the reference, but I do know that garbage collection has overhead associated with it. Overhead from the function call to the GC, overhead from the operating system when the program requests a block of memory, and overhead from the book-keeping that the GC must do to keep track of that memory.
Bottom line: Stack allocation is always faster, but it's not always the best option. Dynamic memory allocation is much more useful at times.
Every function has a stack frame. The compiler generates one for every function. It only takes one operation to allocate some memory on the stack, just decrement the stack pointer.
As far as I can see, there is nothing more efficient than one assembly operation.
The professor uses them to mostly keep track of attendance by having the students answer simple quizes. Since each clicker has it's own internal ID number, the clickers allow the professor to quickly determine who's coming to class.
I really didn't like the price ($25 used) for the clickers, but I can see why some professors have them. Besides attendance, it is a quick way of having the class take a quick quiz during class.
It's an interesting idea to convince your employees and even store managers that you are capable of doing something technically impossible, presumably with the hope that it'll trick your customers too.
The point is that some (or most?) people will believe those stories, and be deterred from copying.
What if the user wants a screensaver that downloads new pictures to display from the internet?
The problem is that definitions of what a program can/should do change often.
I suppose history really does repeat itself.
The New Orleans buses are underwater. I imagine that many of the buses in the area are damaged as well, if they already weren't used to evacuate people. Step two: Put food on the buses and drive the to New Orleans. This should take ONE DAY.
Drive on what roads? The Hurricane didn't just destroy New Orleans. A bus carrying people overturned just the other day, killing at least one. The roads are in really bad shape.
A gas mask also helps protect someone against tear gas, but that doesn't stop tear gas from being useful against most people.
But did you look at the results? One was a post by someone named "Infinite Loop", and some of the others were explaining an old problem, and some were not about it at all.
I think the "vast, unpopulated areas" surround the sparsely populated areas.
Exactly. You said it much better than I.
Because that approach would take too much fuel. I believe that NASA tries to calculate a launch pattern that more or less "slings" the object in an arc that will meet up with Mars after the necessary months of travel.
The labels will list the words "sex", "language", or "violence" under the letter rating depending on what the game contains.
The video played great at 1280x720p (in Windows XP).
I am curious as well. I program in Win32, and I haven't encountered any problems with C code.
I didn't read the article above, but the Los Angeles Times mentioned that HP will be selling them until they run out of stock, which should be sometime in September.
Why is it unavoidable? if a driver crashes, the OS should just block the device and continue with its work, no blue screens or kernel panics or whatever, a driver malfunction is JUST a program malfunction, if the OS does not mange fine the hardware drivers then it is not 'operating' well.
What if the video card driver fails? (which happens often when I'm pushing the graphics card) I don't want the OS to keep on going. I think some errors and malfunctions need to cause the OS to shutdown, especially if the error could cause data corruption.
I do agree that it would be nice if books on the subject were less expensive. Paying $60 or more for a book is a little prohibitive.