I preordered a 360 over a month ago, and was required to pay upon ordering. Turns out that instead of filling the preorders, the reseller instead held an event where they sold 360:s to random people. Don't know when they'll start concentrating on filling orders, but since they already have the money, I'm guessing they're not in a hurry. If you're from Sweden, I suggest you avoid shopping at Webhallen...
This kind of reminds me of the "This land is your land"-debacle. Woody Guthrie, who originally wrote the song, used the following copyright:
This song is Copyrighted in U.S., under Seal of Copyright # 154085, for a period of 28 years, and anybody caught singin' it without our permission, will be mighty good friends of ourn, cause we don't give a dern. Publish it. Write it. Sing it. Swing to it. Yodel it. We wrote it, that's all we wanted to do.
Still, somehow the above copyright notice was revoked, and after Guthries death, the song passed into ownership of a record label, that claims ownership to it.
I am a strong beliver in the capitalist system and right to own property, but that right _must_ include the right to give property away.
It _is_ a less critical bug. All modern linux systems have the same 'bug' by design, and not only for 16-bit applications. The consensus is that this is not worth fixing. (To execute an arbitrary file, even one on a fs mounted noexec, simply use ldlinux.so to launch it)
I really wish all the lamers who complain about dupes would give it a rest. Yes Slashdot does on occasion run actual dupes, but 90% of the so called 'dupes' are simply the latest developments in an ongoing event. I truly wish more newspapers and other media would be as dedicated to giving you the complete story and not be as obsessed with breaking news.
I'm sure you can. But to ship 100 million such boxes, you'd have to take a dump five times every day for 55,000 years. That would take some serious dedication.
Further, Sony made people pay for the PS2, at least $100 on average.
If you manage to create 100 million of your 'turdboxes', and make people pay $10 billion for them, then you can start comparing yourself with the Sony marketing department.
Read the part of my post about Firefox promising two even bigger exploits? It was a JOKE, and a comment on just the type of behaviour you mention. Seeing how I got moderated to oblivion for my post, you don't seem to be the only one who missed the point, though.
This is simply more paid propaganda from Microsoft. They release this new and exciting flaw on the same day Firefox 1.5 is supposed to be released, simply as a way to steal the Mozilla foundations thunder(bird). It won't work, though, because among the many new and exciting features in FF 1.5 is a whole host of new security bugs, two of which will even be rated 'Megasuperultra critical' which is two whole levels above the 'Extremely critical' rating of the flaw in IE.
Thinking some more on this subject, I realized that all objects have a reference to them passed to another method (the constructor) on creation, so using your simple rules, not a single object would ever be allocated on the stack. And there is no way around that without using at least some simple escape analysis, since a constructor may pass on a reference to the newly created object to some other method.
The thing is, it is _very_ common to pass a reference to an object to another method, so nearly all objects are allocated on the heap. But most methods that take an object reference as an argument don't actually keep any copies of it after the method returns, meaning many objects that are allocated on the heap using your 'purely mechanical decision' could actually be allocated on the stack. But figuring that out requires escape analysis, which is both expensive and error prone, which is why Java is only getting it now, in the latest preview releases of Suns JDK.
Escape analysis is by no means easy. And it is also the case that it is easy to see that an object can not escape, it is much harder to proove it. But on the other hand, escape analysis can sometime work succesfully in cases where manual coding without using the heap would be very cumbersome, such as when using autopointers or similar, when inlining blocks of code in different contexts, some of which require heap storage, etc.
Rising oil prices would not improve the economy. People are (mostly) rational, they would not drive so much if the cost driving was not offset by the benefits. People drive twenty minutes to buy stuff at Walmart instead of going to the local store because the sum of the cost of gas, the value of the extra time taken to drive a longer distance and other factors is smaller than the price difference. You are correct in saying that if gas prices where higher, this balance would shift towards doing things locally. You would have to buy things in the much more expensive local stores. The drive to take your children to hockey practice becomes to expensive, etc.. If commuting is expensive, the number of available jobs at an acceptable distance from your home will decrease, meaning the likelyhood that you will find the 'right' job decreases. So your economy and your quality of life will decrease in several important ways. This is all basic market economy - the market will find the optimal balance by itself.
That said, there may be hidden costs not taken into account by the market, such as environmental damage and the transient nature of some natural resources. There may be some rather large economic costs associated with the use of oil as an energy source. It can be argued that the market does not sufficiently take such factors into account and that it is motivated to correct this by adding an additional oil tax. But don't think that increasing the oil price will be _good_ for the economy, because it won't.
There are two reasons why lazy initialization is almost always the better solution:
Not all classes are used. Why pay a memory and performance penalty for having e.g. the Java2d API installed if your application never uses it?
Startup time will suffer. A 3 second startup penalty for only the bare minimum runtime, and probably much more for any non-trivial application is a huge deal.
The advantage of doing eager initialization is predictability, and in the case where almost all classes get initialized sooner or later (which would be very rare considering the size of the Java API) a slight performance increase.
Maybe some kinds of games would benefit from this, but almost all other applications would benefit from more lazy initialization, not less.
I love it. I swear people take these things way too seriously. I get the feeling that the vast majority of people on slashdot are computer geeks with no social skills, hence the inability to get a joke.
I thought it was pretty funny as well, but it is well known that irony doesn't travel well over the Internet, so the author probably should have phrased things differently.
It is not yet know if the Revolution CPU will be based on the PPE design or the POWER4 design, though the Ars article makes it seem likely it will be PPE-based. But either way, it will with a 100% certainty be a custom made chip, just like the PS3 and 360 PPEs differ. IBM do this all the time, the 970 (G5) CPU is a stripped down POWER4, for instance.
Since it looks like the Revolution will be _much_ easier to develop for, because of it's old-school design with few cores and a lot of cache, the first generation of Revolution games might look noticably better on the revolution than on the 360 or PS3.
I think you are way to high strung, you seem to think anything relaxed and non-pretentious looks amateurish. Remember, most of the open source movement is built on code written by people in their spare time, just for fun.
This sounds like a good candidate for 'Tonights Top-Ten list'.
Aaaaand the number one Copyright infringement made by IBM is..../* Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. */
I've read that the Glibc heap implementation will also be implementing functionality similar to the guard pages in OpenBSD malloc. Should help shake out quite a few memory allocation bugs...
Seeing how OpenSSH, pf and several other 'OpenBSD Spinoffs' have made it to Linux and other Unix-like operating systems, I'd have to say that at the very least, OpenBSD is by far the most interesting project in the BSD world for non-BSD:ers.
Are you saying that the driver model is not a part of Windows? Or that the templars forced Microsoft to use that driver model? Because otherwise, the driver model is a core part of the OS design, and if it is unstable and errorprone, then that makes the OS total garbage.
Slashdot Mirror
I preordered a 360 over a month ago, and was required to pay upon ordering. Turns out that instead of filling the preorders, the reseller instead held an event where they sold 360:s to random people. Don't know when they'll start concentrating on filling orders, but since they already have the money, I'm guessing they're not in a hurry. If you're from Sweden, I suggest you avoid shopping at Webhallen...
I love it. It puts the power over the consumers eyeballs even more firmly in the hands of the consumer.
That said, I doubt very many consumers will use this very often.
This kind of reminds me of the "This land is your land"-debacle. Woody Guthrie, who originally wrote the song, used the following copyright:
This song is Copyrighted in U.S., under Seal of Copyright # 154085, for a period of 28 years, and anybody caught singin' it without our permission, will be mighty good friends of ourn, cause we don't give a dern. Publish it. Write it. Sing it. Swing to it. Yodel it. We wrote it, that's all we wanted to do.
Still, somehow the above copyright notice was revoked, and after Guthries death, the song passed into ownership of a record label, that claims ownership to it.
I am a strong beliver in the capitalist system and right to own property, but that right _must_ include the right to give property away.
It _is_ a less critical bug. All modern linux systems have the same 'bug' by design, and not only for 16-bit applications. The consensus is that this is not worth fixing. (To execute an arbitrary file, even one on a fs mounted noexec, simply use ldlinux.so to launch it)
I really wish all the lamers who complain about dupes would give it a rest. Yes Slashdot does on occasion run actual dupes, but 90% of the so called 'dupes' are simply the latest developments in an ongoing event. I truly wish more newspapers and other media would be as dedicated to giving you the complete story and not be as obsessed with breaking news.
I'm sure you can. But to ship 100 million such boxes, you'd have to take a dump five times every day for 55,000 years. That would take some serious dedication.
Further, Sony made people pay for the PS2, at least $100 on average.
If you manage to create 100 million of your 'turdboxes', and make people pay $10 billion for them, then you can start comparing yourself with the Sony marketing department.
Read the part of my post about Firefox promising two even bigger exploits? It was a JOKE, and a comment on just the type of behaviour you mention. Seeing how I got moderated to oblivion for my post, you don't seem to be the only one who missed the point, though.
:(
I still think my OP was funny, though.
This is simply more paid propaganda from Microsoft. They release this new and exciting flaw on the same day Firefox 1.5 is supposed to be released, simply as a way to steal the Mozilla foundations thunder(bird). It won't work, though, because among the many new and exciting features in FF 1.5 is a whole host of new security bugs, two of which will even be rated 'Megasuperultra critical' which is two whole levels above the 'Extremely critical' rating of the flaw in IE.
Thinking some more on this subject, I realized that all objects have a reference to them passed to another method (the constructor) on creation, so using your simple rules, not a single object would ever be allocated on the stack. And there is no way around that without using at least some simple escape analysis, since a constructor may pass on a reference to the newly created object to some other method.
The thing is, it is _very_ common to pass a reference to an object to another method, so nearly all objects are allocated on the heap. But most methods that take an object reference as an argument don't actually keep any copies of it after the method returns, meaning many objects that are allocated on the heap using your 'purely mechanical decision' could actually be allocated on the stack. But figuring that out requires escape analysis, which is both expensive and error prone, which is why Java is only getting it now, in the latest preview releases of Suns JDK.
Escape analysis is by no means easy. And it is also the case that it is easy to see that an object can not escape, it is much harder to proove it. But on the other hand, escape analysis can sometime work succesfully in cases where manual coding without using the heap would be very cumbersome, such as when using autopointers or similar, when inlining blocks of code in different contexts, some of which require heap storage, etc.
You might want to read up on this page for some human interaction hints.
I disagree. My question would be 'How often do you hear about a langauge pack for (insert OSS program of choice)?
Remember, all publicity is good publicity, and Slashdot gives quite a lot of publicity to Microsoft, less and less publicity to open source software.
Rising oil prices would not improve the economy. People are (mostly) rational, they would not drive so much if the cost driving was not offset by the benefits. People drive twenty minutes to buy stuff at Walmart instead of going to the local store because the sum of the cost of gas, the value of the extra time taken to drive a longer distance and other factors is smaller than the price difference. You are correct in saying that if gas prices where higher, this balance would shift towards doing things locally. You would have to buy things in the much more expensive local stores. The drive to take your children to hockey practice becomes to expensive, etc.. If commuting is expensive, the number of available jobs at an acceptable distance from your home will decrease, meaning the likelyhood that you will find the 'right' job decreases. So your economy and your quality of life will decrease in several important ways. This is all basic market economy - the market will find the optimal balance by itself.
That said, there may be hidden costs not taken into account by the market, such as environmental damage and the transient nature of some natural resources. There may be some rather large economic costs associated with the use of oil as an energy source. It can be argued that the market does not sufficiently take such factors into account and that it is motivated to correct this by adding an additional oil tax. But don't think that increasing the oil price will be _good_ for the economy, because it won't.
The advantage of doing eager initialization is predictability, and in the case where almost all classes get initialized sooner or later (which would be very rare considering the size of the Java API) a slight performance increase.
Maybe some kinds of games would benefit from this, but almost all other applications would benefit from more lazy initialization, not less.
It is not yet know if the Revolution CPU will be based on the PPE design or the POWER4 design, though the Ars article makes it seem likely it will be PPE-based. But either way, it will with a 100% certainty be a custom made chip, just like the PS3 and 360 PPEs differ. IBM do this all the time, the 970 (G5) CPU is a stripped down POWER4, for instance.
Since it looks like the Revolution will be _much_ easier to develop for, because of it's old-school design with few cores and a lot of cache, the first generation of Revolution games might look noticably better on the revolution than on the 360 or PS3.
He's a hu-man, he is using hexadecimal numbers. That would be 100001 years old in your native binary.
I think you are way to high strung, you seem to think anything relaxed and non-pretentious looks amateurish. Remember, most of the open source movement is built on code written by people in their spare time, just for fun.
This sounds like a good candidate for 'Tonights Top-Ten list'.
/* Copyright 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. */
Aaaaand the number one Copyright infringement made by IBM is....
The crowd goes wild!
Time for a reality check, I think. Googles honeymoon is over, Slashdot is lambasting them.
I've read that the Glibc heap implementation will also be implementing functionality similar to the guard pages in OpenBSD malloc. Should help shake out quite a few memory allocation bugs...
Seeing how OpenSSH, pf and several other 'OpenBSD Spinoffs' have made it to Linux and other Unix-like operating systems, I'd have to say that at the very least, OpenBSD is by far the most interesting project in the BSD world for non-BSD:ers.
Are you saying that the driver model is not a part of Windows? Or that the templars forced Microsoft to use that driver model? Because otherwise, the driver model is a core part of the OS design, and if it is unstable and errorprone, then that makes the OS total garbage.