Nuclear Physics is only ~100 years old, nuclear chain reactions weren't observed until the 30s, and the first fission reactor wasn't invented until the 40s. Fusion was also first observed in the 30s and as we all know they figured out how to make a pretty good bomb out of it by the 40s. Anyway my point is, all of this stuff is relatively recent, the physics is still moving fairly rapidly, but they have figured out how to get a net energy gain out of a manageable fusion reaction so to say it's 'always' going to be 30 years away is simply unfounded cynicism.
You clearly didn't read the article. By leaning sideways the device moves side ways, it doesn't fall down and you don't compensate for it somehow. This isn't just another motorized unicycle.
I've never used or for that matter seen BeOS, but from the article and other comments I gather it's distinguished because it was built from the ground up to be a highly responsive desktop machine capable of exploiting multiple cores. Presumably that means that when you right click for a context menu the system responds immediately, as oppose to Linux and Windows where it appears eventually when the scheduler decides it can be fit in between other applications crunching numbers in the background.
Look-up table = lack of engineering foresight? The radix-4 algorithm is 33% faster than what they were using, and I for one prefer a faster processor to a processor which doesn't store any look up data. If anything this was a communication issue and management is to blame for not making sure their testers were testing enough of the right things.
A few incorrect values in a large look-up table (the source of the Pentium division bug) is obviously a data entry issue, not a lack of engineering foresight.
Well the typical bugs that affect C programs, like buffer overflows, using a dereferenced pointer, etc; along with common mistakes made in procedural programming in general like off-by-one errors are much less likely to come up in a functional language like Haskel. In a lot of cases Haskel code is simply a LOT shorter and easier to read than it's C/C++ counterpart which makes it much easier to find a problem; not much harder than finding the problem in a spec on paper.
So, no I don't think it guarantees anything, but it's a lot better than C code on its own.
And Disassociative identity disorder was previously referred to (and still is by some standards) as MPD or Multiple Personality Disorder, which in my humble opinion is quite a bit clearer.
Threading would work just as well, if not better in your scenario. Separate processes just gives you the extra boundary of protection and convenience that comes with not sharing memory.
It's just that under American/Canadian law quotes in an essay are exempt because of Fair Use (afaik). The GP said everything is black and white in the UK, but how large can a quote be of a commercial source before it's infringement? Can I copy an entire book within a quotation block; a chapter of a book; ten pages; 1 page; 2 paragraphs; 2 sentences?
Except for the massive costs involved in running an election. I think most tax payers would rather their money was spent on health care, education, road maintenance, or lower taxes than elections.
Slashdot Mirror
That uses the gecko layout engine... I don't think that counts.
Nuclear Physics is only ~100 years old, nuclear chain reactions weren't observed until the 30s, and the first fission reactor wasn't invented until the 40s. Fusion was also first observed in the 30s and as we all know they figured out how to make a pretty good bomb out of it by the 40s. Anyway my point is, all of this stuff is relatively recent, the physics is still moving fairly rapidly, but they have figured out how to get a net energy gain out of a manageable fusion reaction so to say it's 'always' going to be 30 years away is simply unfounded cynicism.
You clearly didn't read the article. By leaning sideways the device moves side ways, it doesn't fall down and you don't compensate for it somehow. This isn't just another motorized unicycle.
I'm glad I don't work where you do. Sure I'm never assigned to clean up code, but as long as I keep to schedule they really don't care if I do.
He's probably had too much experience with vulture capitalists.
Enter SELinux to prevent the app from calling said system API, or being able to do anything once it escalates?
By install you mean get bash to boot, if you're lucky?
I've never used or for that matter seen BeOS, but from the article and other comments I gather it's distinguished because it was built from the ground up to be a highly responsive desktop machine capable of exploiting multiple cores. Presumably that means that when you right click for a context menu the system responds immediately, as oppose to Linux and Windows where it appears eventually when the scheduler decides it can be fit in between other applications crunching numbers in the background.
s/trouble/Linux
Look-up table = lack of engineering foresight? The radix-4 algorithm is 33% faster than what they were using, and I for one prefer a faster processor to a processor which doesn't store any look up data. If anything this was a communication issue and management is to blame for not making sure their testers were testing enough of the right things.
A few incorrect values in a large look-up table (the source of the Pentium division bug) is obviously a data entry issue, not a lack of engineering foresight.
Achilles? (Though he couldn't win a foot race with a tortoise, so I don't know how great he was)
Well the typical bugs that affect C programs, like buffer overflows, using a dereferenced pointer, etc; along with common mistakes made in procedural programming in general like off-by-one errors are much less likely to come up in a functional language like Haskel. In a lot of cases Haskel code is simply a LOT shorter and easier to read than it's C/C++ counterpart which makes it much easier to find a problem; not much harder than finding the problem in a spec on paper.
So, no I don't think it guarantees anything, but it's a lot better than C code on its own.
Yes, but through a z-machine/infocom interpreter, such as one at the following: http://www.ifarchive.org/indexes/if-archiveXinfocomXinterpreters.html
But the article mentions a sample bias. They asked readers what the worst PC Repair shops were before they investigated.
Even if one of the parties systems are compromised, the hacker won't be able to find some key that will allow them to decode the messages.
Clearly someone doesn't want any mention that the standard was delayed.
They probably think this line from the summary is trolling too: "ending a contentious round of infighting that has delayed the standard for years."
The patch appears to have been released now
According to the mozilla wiki report of the weekly status meetings the patch will be out by the end of the week: https://wiki.mozilla.org/Firefox3.5/StatusMeetings/2009-07-15
He did
And Disassociative identity disorder was previously referred to (and still is by some standards) as MPD or Multiple Personality Disorder, which in my humble opinion is quite a bit clearer.
Threading would work just as well, if not better in your scenario. Separate processes just gives you the extra boundary of protection and convenience that comes with not sharing memory.
It's just that under American/Canadian law quotes in an essay are exempt because of Fair Use (afaik). The GP said everything is black and white in the UK, but how large can a quote be of a commercial source before it's infringement? Can I copy an entire book within a quotation block; a chapter of a book; ten pages; 1 page; 2 paragraphs; 2 sentences?
Does this mean you have to contact the author of every work you quote in an essay?
Except for the massive costs involved in running an election. I think most tax payers would rather their money was spent on health care, education, road maintenance, or lower taxes than elections.