I'm not sure they've decided yet, but I suspect they'll decide, based on fab costs of the 1-chip PS2, pretty soon... before investing all too much in an emulator.
There's something even more important, though. Originally, the PS1 (PSX has become an overloaded term) was a typical system; a bunch of chips tied together on a circuit board. Over the lifetime of the system they reduced the component count significantly; the final revision of the PS1 had the entire system (well, except for standard external stuff) on a single chip.
This was nice; it let Sony cut down the console costs and increase the profit margin. But it allowed something even better. It allowed Sony to include an entire PS1 inside the PS2, for the cost of one (relatively small) chip. Now that the PS2 (which contains a PS1...) is on a single chip, it becomes feasible to put an entire PS2 inside the PS3, even though the architectures are (presumably) very different. It is literally two (or, I guess, three) systems in a single box; multiple CPU's, of which only one is active at a given time.
This leads, of course, to backwards compatibility which, in my opinion, is the most important think Sony has over the competion.
How often, in the last eight years or so, have you had a disk die gradually (potentially due to dead sectors)? How often have you had a disk die suddenly? I think platter space has reached the point where sector errors are negligible next to physical breakdown, and no company would risk extra support when not necessary.
iBook 600MHz, with software over/underclocking to dynamically switch in the range 200-900MHz. (Would be 1GHz, but the processor just can't handle it stably except in winter.)
Eh. 10 hours with two batteries doesn't impress me too much... I get 7 hours with one battery under ideal conditions, 6 hours under actual conditions (writing code, so edit/compile/test cycle), and 4 hours under horrendous conditions (photon tracing), on a computer that cost me less than $1000.
I guess we'll see... when I saw how trivial the opt-out webpage is, I wrote a quick script to opt out everyone at a few of my local exchanges (212-799, 212-749, 212-724).
The reason that it always lists the viewable size of a monitor next to its 'market' size these days is because of an earlier lawsuit; even 5 years ago, this practice was very rare.
Offtopic, but hey, you're a BIOS person and I'm curious. Do any modern operating systems actually use the bios' hard work any more? I got the impression that they all more or less did their own hardware detection, talked to hardware directly instead of through the bios, etc. Does the bios really play an important role in today's x86 world?
(Yes, I realize that the MS BIOS discussed would not be "let windows do everything" but rather "use TCPA to validate that only people with the Magic Key can do anything"... just asking the theoretical question, above.)
Look, troll. They're not saying that it's not a computer. They're saying that it's not a computer FOR TAX PURPOSES. The duty system apparently makes a distinction between entertainment systems and personal computer systems, and defines each by it's primary usage. So it is not a computer, for tax purposes. End of story.
Using URI's, one can identify any object (assuming a URI scheme is made to include that object; for example, ISBN numbers or LOC numbers for books; because creating a new scheme is trivial, this is not much of a limitation). With the new info: protocol, if it's done correctly (which I'm not yet convinced of) one can CANONICALLY identify any object. This is a really big deal; before, it was not obvious (or even deducible, in the general case) that isbn:foo and loc:bar referred to the same book. If info: provides such mappings, it's a pretty big deal for anyone who uses URI's.
You are confusing URL's and URI's. URL's are a subset of URI's; one attribute of that subset is that the protocol segment, combined with the rest of the URI, allows one to "locate" the "resource". In a general URI, this location feature is not necessarily provided. Note that isbn:029193185 (or whatever) is/already/ a valid URI; what the info: URI set seems to do is provide mappings between multiple existing, redundant URI's.
Just use a ramdisk, and a UPS (if you even need it). For reference, I use a flash-disk based Mini-ITX board with a UPS based on two standard 6V lantern batteries -- lasts about 8 hours.
You know, I've been thinking about this response for a couple of hours now... and I've come to the conclusion that, really, it doesn't depend on where the mole is. I don't want to see it.
Push technology cannot, ever, be made into a useful marketing vector. Client pull, and only pull, leads to reasonable, effective, and non-obtrusive marketing.
My iBook is about 16 months old (600MHz, purchased when the 700MHz came out). Yes, lithium ion batteries only last about 100-300 cycles, and apple's seem to be closer to 100. A new battery costs, what, $70? Buy one. I'm on my third. Even on a new battery, though, I never got more than 4:30 of battery life... maybe 5 hours, if I wasn't doing much and wireless was off. The problem is that the "reduced speed" option on the 600Mhz iBook lowers the clockspeed to 400Mhz, which is just silly; it doesn't make enough of a difference. 700/350 and 800/400 both make more sense, but I find (for my purposes) 600/200 is good enough. (BTW, overclocking is software-trivial also... but my iBook becomes unstable at 900MHz after about half an hour. It is stable at 800MHz for a make world, though; not bad for a 600MHz chip and a 40mm fan.)
Keep in mind that, with enough power and a correctly tuned angle of attack, an (approximation of a) 2-dimensional surface will generate lift. This is the principle behind delta wings; they generate lift from vortices forming over the leading edge, rather than from the airfoil shape of the wing. You're right, though, that most (all?) current delta wing craft use airfoil shaped wings, to allow them to get some lift at less outrageous speeds and angles of attack; that is, to let them take off and land.
Heck, I can get seven hours out of my ibook with the standard battery, at minimum screen brightness. (The joys of underclocking... I get to run a 2:1 bus ratio on my G3! What's such a big deal about doing it on a G5?)
Slashdot Mirror
"Spam is evil and bad", - unless of course its money they send you rather than spam...
Um... don't most people hold this view?
I'm not sure they've decided yet, but I suspect they'll decide, based on fab costs of the 1-chip PS2, pretty soon... before investing all too much in an emulator.
There's something even more important, though. Originally, the PS1 (PSX has become an overloaded term) was a typical system; a bunch of chips tied together on a circuit board. Over the lifetime of the system they reduced the component count significantly; the final revision of the PS1 had the entire system (well, except for standard external stuff) on a single chip.
This was nice; it let Sony cut down the console costs and increase the profit margin. But it allowed something even better. It allowed Sony to include an entire PS1 inside the PS2, for the cost of one (relatively small) chip. Now that the PS2 (which contains a PS1...) is on a single chip, it becomes feasible to put an entire PS2 inside the PS3, even though the architectures are (presumably) very different. It is literally two (or, I guess, three) systems in a single box; multiple CPU's, of which only one is active at a given time.
This leads, of course, to backwards compatibility which, in my opinion, is the most important think Sony has over the competion.
What? Yes it is. Don't use C.
How often, in the last eight years or so, have you had a disk die gradually (potentially due to dead sectors)? How often have you had a disk die suddenly? I think platter space has reached the point where sector errors are negligible next to physical breakdown, and no company would risk extra support when not necessary.
iBook 600MHz, with software over/underclocking to dynamically switch in the range 200-900MHz. (Would be 1GHz, but the processor just can't handle it stably except in winter.)
Eh. 10 hours with two batteries doesn't impress me too much... I get 7 hours with one battery under ideal conditions, 6 hours under actual conditions (writing code, so edit/compile/test cycle), and 4 hours under horrendous conditions (photon tracing), on a computer that cost me less than $1000.
I guess we'll see... when I saw how trivial the opt-out webpage is, I wrote a quick script to opt out everyone at a few of my local exchanges (212-799, 212-749, 212-724).
Last time I checked, ADC was somewhere around 3.2Gbps; I assume DVI is around the same.
The reason that it always lists the viewable size of a monitor next to its 'market' size these days is because of an earlier lawsuit; even 5 years ago, this practice was very rare.
Hmph! I don't see any of mine!
Come to think of it, none of mine were original...
Or funny...
Oh.
Offtopic, but hey, you're a BIOS person and I'm curious. Do any modern operating systems actually use the bios' hard work any more? I got the impression that they all more or less did their own hardware detection, talked to hardware directly instead of through the bios, etc. Does the bios really play an important role in today's x86 world?
(Yes, I realize that the MS BIOS discussed would not be "let windows do everything" but rather "use TCPA to validate that only people with the Magic Key can do anything"... just asking the theoretical question, above.)
I invoke the Nazi Law. Someone mentioned Godwin (or tried to... Goodwin!?) in the discussion.
PLEASE do not respond to this article! I can't afford it!
Look, troll. They're not saying that it's not a computer. They're saying that it's not a computer FOR TAX PURPOSES. The duty system apparently makes a distinction between entertainment systems and personal computer systems, and defines each by it's primary usage. So it is not a computer, for tax purposes. End of story.
Using URI's, one can identify any object (assuming a URI scheme is made to include that object; for example, ISBN numbers or LOC numbers for books; because creating a new scheme is trivial, this is not much of a limitation). With the new info: protocol, if it's done correctly (which I'm not yet convinced of) one can CANONICALLY identify any object. This is a really big deal; before, it was not obvious (or even deducible, in the general case) that isbn:foo and loc:bar referred to the same book. If info: provides such mappings, it's a pretty big deal for anyone who uses URI's.
You are confusing URL's and URI's. URL's are a subset of URI's; one attribute of that subset is that the protocol segment, combined with the rest of the URI, allows one to "locate" the "resource". In a general URI, this location feature is not necessarily provided. Note that isbn:029193185 (or whatever) is /already/ a valid URI; what the info: URI set seems to do is provide mappings between multiple existing, redundant URI's.
Just use a ramdisk, and a UPS (if you even need it). For reference, I use a flash-disk based Mini-ITX board with a UPS based on two standard 6V lantern batteries -- lasts about 8 hours.
You know, I've been thinking about this response for a couple of hours now... and I've come to the conclusion that, really, it doesn't depend on where the mole is. I don't want to see it.
I agree with you entirely on both points. :-)
But the x86-64 architecture is designed to allow both to scale up, as necessary, to 64 bits, without requiring program changes, yes?
Push technology cannot, ever, be made into a useful marketing vector. Client pull, and only pull, leads to reasonable, effective, and non-obtrusive marketing.
My iBook is about 16 months old (600MHz, purchased when the 700MHz came out). Yes, lithium ion batteries only last about 100-300 cycles, and apple's seem to be closer to 100. A new battery costs, what, $70? Buy one. I'm on my third. Even on a new battery, though, I never got more than 4:30 of battery life... maybe 5 hours, if I wasn't doing much and wireless was off. The problem is that the "reduced speed" option on the 600Mhz iBook lowers the clockspeed to 400Mhz, which is just silly; it doesn't make enough of a difference. 700/350 and 800/400 both make more sense, but I find (for my purposes) 600/200 is good enough. (BTW, overclocking is software-trivial also... but my iBook becomes unstable at 900MHz after about half an hour. It is stable at 800MHz for a make world, though; not bad for a 600MHz chip and a 40mm fan.)
Keep in mind that, with enough power and a correctly tuned angle of attack, an (approximation of a) 2-dimensional surface will generate lift. This is the principle behind delta wings; they generate lift from vortices forming over the leading edge, rather than from the airfoil shape of the wing. You're right, though, that most (all?) current delta wing craft use airfoil shaped wings, to allow them to get some lift at less outrageous speeds and angles of attack; that is, to let them take off and land.
Heck, I can get seven hours out of my ibook with the standard battery, at minimum screen brightness. (The joys of underclocking... I get to run a 2:1 bus ratio on my G3! What's such a big deal about doing it on a G5?)