Well, in terms of cache, the CPU (just like x86) uses separate instruction and data caches, at least at some level, making it a Harvard machine in that sense, but they have to support cache flushing operations to support self-modifying code. So there's really no security advantage gained through this bit of Harvardness. And it's certainly not unique to the PPC.
NeXT's.app came long before Java came close to being released. The first web browser was a.app, and Java didn't get released until everybody knew what the web was.
You're absolutely right on, but I've got a minor picky point about the first part. While the instruction set must remain stable pretty much downrange forever in a given architecture, this is only really true for the front-end instruction set, which isn't what the CPU actually executes on any current IA-32[e] design. Only the decode stage of things is bound by the instruction set, and the actual bulk of the work is done in the internal architecture which can, and does, change between different designs.
Actually, you're somewhat mistaken here. That Space.com page that was linked to refers to two different articles, one Zenit launch and one Falcon 1 launch. The Zenit is the Sea Launch flight, and is a MUCH bigger booster, and MUCH more expensive. The Falcon is a more or less (apart from subsystems and avionics) an independent, ground-up launcher by SpaceX, with nothing to do with Boeing and the rest of the Sea Launch groups.
I'm a student who hates Windows as much as the next guy. I like using the Mac, and the Mac will always be my primary workstation, and I use it whenever possible. I don't want to carry two computers around, but I still need to be able to run Xilinx ISE and AutoCAD and ANSYS and Fluent and all the other things that won't run on the Mac. Fortunately, I can run MATLAB on the mac side of things with the rest of my life, but when I need to design or simulate something, I have to use Win32. It'd be nice not to have to use a separate machine for that.
Dual-booting isn't a fad for some of us, it's what we have to do if we want to be able to use the Mac and still get work done.
AMD has only been outselling Intel on the retail market, which means that more people who are building their own computers are using AMD than Intel, and it's still pretty close. The OEM market, which is where the vast majority of CPUs go is still absolutely dominated by Intel. Yes, AMD likely would be able to supply Apple in terms of percentage of production, but I'm not sure they could supply the same kind of flow that Intel could for mobile processors.
No, no, the moving parts aren't the problem. It's a Bimmer, remember? The mechanical components will be amazing, reliable and powerful, but they will somehow find a way to write software for it. And the software will suck. It will likely try to kill you.
How much 64-bit native software is really out there, and what does it use the 64-bit space for? The actual register size change really doesn't do jack in terms of virtually any app out there (2^32 is still more than big enough number to do just about anything with) while the advantage actually comes in the fact that you can address a whole lot more RAM. Since this is a laptop chip, it'd be really hard to make a low-power notebook with more than 4gb of RAM anyways. EM64T is slated for the next generation Pentium M.
The minute you say "instantaneous communication", we can throw out the idea as being impossible under our current knowledge of physics. It's a problem of "causality".
Basically, here's how it works. You've got two events, separated in time and space. Say, I sneeze, and somebody at Alpha Centauri falls out of his chair three years later (three years in both people's rest frames. let's assume they're not moving relative to each other). Relativity says the relative time between those events can be shifted by up to (speed of light)*(rest distance between objects). (I can work out the math and post something if people are interested, and it's not just theory, it's been observed many-a-time) For our sneeze/chair situation, that's four years. This means that you, on the far away star can have fallen out of your chair and be well on your way to paying that hospital bill long before I ever sneeze. This is called a "spacelike separation", because you can't say which order two events happened in.
Ok, now let's say we have an instant communications system. We have a transmitter and a receiver (one here, one on alpha centauri), both with a bomb on them. When you press the button on the transmitter, it blows up the receiver. But not before the receiver sends a signal back saying "ok, I'm about to blow up, you can go ahead and blow up yourself". This is all fine and dandy in the rest frame, but if we're moving quickly, the receiver gets its signal before the transmitter sends it, just as how you fell out of your chair before I sneezed! The receiver sends its message to blow up the transmitter, it blows up, but the problem is, the transmitter never sent its message.
I'm sure there are holes in my thought experiment, but it's the best I could come up with on short notice;-) There are better ones, I'm sure, but you get the picture. As far as we know, if you can send a message faster than light can, you more or less break the universe.
Right now, between the ESA and us, there are 4 different EELV class boosters. All of them are throttle-able, minimally staged (I believe all two stage), and are all pretty cheap. The Ariane 5, the Delta 4, the Atlas V and the SpaceX Falcon 9. Then there's the russian's stuff.
My question is this: why do we need to build a new "space program"? Why can't we build new rockets, and capsules for those rockets, allowing us to switch capsules when better capsule tech comes about, and better rockets when better rocket tech comes about? Keep competition going, it'll be good for the industry.
Mercury flew on different rockets. So did Apollo. Soyuz flew on various forms of the Soyuz booster, and a handful of times on Protons in the (never got past the testing phase) Zond program. CEV should be the same way.
The escape rocket should be able to abort the mission through the point in the ascent when the main propulsion of the capsule itself can continue the abort. In other words, the system should be (and was, in the Apollo days) able to get the capsule off the stack until the last stage separates from the capsule.
I'd hope that the CEV is going for the same level of safety.
Getting money back from anybody is hell. What you CAN do is refuse to pay a certain charge when the bill gets to you. Things actually get cleared up pretty quickly that way.
You just made all that up, didn't you. "1.9 amps/hz"? A dime sized-reader? I don't know of a dime-sized much anything. A dime is really, really small. And 64.2W is a shitload of power. If my credit card is broadcasting with more power than my car's amateur radio transmitter, there's something horribly wrong, and you'd be able to pick it up in the next county, not "3000 yards".
As others have mentioned, Cocoa is just the NeXT API, very minimally changed. In fact, this becomes VERY apparent looking at the names of the API calls. Everything's in the form of NSWindow and NSRegion, NS standing for NeXTSTEP.
The XLR's mother car, the Corvette (back to at least the '99 C5) has this too. You slide the little switch to "passive" mode on the key, and it'll unlock the door when you get near the car.
On the Lexus (at least on my IS), while there are only a few mechanical keys that are in circulation, each key needs a radio transponder in it that's interrogated to start the car. The ID is specific to the key, but you can tell the car (through a bizarre song and dance involving turning the key a couple of times and pumping the accelerator) to allow a new key to pair with the car.
So, you can add a key to the car, but you need at least one key to get the thing in the programming mode. They don't store that code anywhere, so if you lose all four keys it came with, you have to buy a new ECU. Really, really expensive. Also hard to steal.
At this point, there's very little information available about which products will and will not survive the merger. Why would any shareholder approve a merger when all he/she knew was that the two companies were to merge?
You are correct in that the TV sats are in GEO, but TDRSS and the weathersats are too. Hell, GOES stands for Geostationary Operational Environmental Satellite.
Note that you can write a Java app on OS X that uses AppKit and looks, feels and runs like a full-fledged OS X app. There are probably apps you use every day and don't notice that they're written in Java.
However you are correct about Swing apps. They're ugly as sin.
The HP iPods are simply rebranded iPods. They come off the same assembly line as the standard Apple branded iPod. The advantage to this situation is that Apple gets access to the HP distribution channel for the iPod, getting their device in every store with HP contracts, and shipping an iPod as a build-to-order option on HP computers.
I've found that the tolerance for this sort of thing varies wildly from place to place. I've got blue hair. (well, half of it) I'm originally from Dallas where you certainly will get funny looks and nobody seems to take you seriously, but in California, it's pretty much a non-issue. Yes, I am a college student, so that helps, but I'm an engineering student where you have to put on a suit (I tend to wear a shirt with it that matches my hair. It adds to the effect. Sort of the whole anime villain thing.) and give a presentation to a bunch of surgeons on the instrument you just designed that they're going to use.
I had to let it wash out before going home to salvage my chances of getting a job.
Shit. As a native Texan living in California, I feel I must object to one of these insults. Unfortunately, I can't quite decide which one isn't true...
Slashdot Mirror
Well, in terms of cache, the CPU (just like x86) uses separate instruction and data caches, at least at some level, making it a Harvard machine in that sense, but they have to support cache flushing operations to support self-modifying code. So there's really no security advantage gained through this bit of Harvardness. And it's certainly not unique to the PPC.
NeXT's .app came long before Java came close to being released. The first web browser was a .app, and Java didn't get released until everybody knew what the web was.
You're absolutely right on, but I've got a minor picky point about the first part. While the instruction set must remain stable pretty much downrange forever in a given architecture, this is only really true for the front-end instruction set, which isn't what the CPU actually executes on any current IA-32[e] design. Only the decode stage of things is bound by the instruction set, and the actual bulk of the work is done in the internal architecture which can, and does, change between different designs.
Actually, you're somewhat mistaken here. That Space.com page that was linked to refers to two different articles, one Zenit launch and one Falcon 1 launch. The Zenit is the Sea Launch flight, and is a MUCH bigger booster, and MUCH more expensive. The Falcon is a more or less (apart from subsystems and avionics) an independent, ground-up launcher by SpaceX, with nothing to do with Boeing and the rest of the Sea Launch groups.
I'm a student who hates Windows as much as the next guy. I like using the Mac, and the Mac will always be my primary workstation, and I use it whenever possible. I don't want to carry two computers around, but I still need to be able to run Xilinx ISE and AutoCAD and ANSYS and Fluent and all the other things that won't run on the Mac. Fortunately, I can run MATLAB on the mac side of things with the rest of my life, but when I need to design or simulate something, I have to use Win32. It'd be nice not to have to use a separate machine for that.
Dual-booting isn't a fad for some of us, it's what we have to do if we want to be able to use the Mac and still get work done.
AMD has only been outselling Intel on the retail market, which means that more people who are building their own computers are using AMD than Intel, and it's still pretty close. The OEM market, which is where the vast majority of CPUs go is still absolutely dominated by Intel. Yes, AMD likely would be able to supply Apple in terms of percentage of production, but I'm not sure they could supply the same kind of flow that Intel could for mobile processors.
No, no, the moving parts aren't the problem. It's a Bimmer, remember? The mechanical components will be amazing, reliable and powerful, but they will somehow find a way to write software for it. And the software will suck. It will likely try to kill you.
How much 64-bit native software is really out there, and what does it use the 64-bit space for? The actual register size change really doesn't do jack in terms of virtually any app out there (2^32 is still more than big enough number to do just about anything with) while the advantage actually comes in the fact that you can address a whole lot more RAM. Since this is a laptop chip, it'd be really hard to make a low-power notebook with more than 4gb of RAM anyways. EM64T is slated for the next generation Pentium M.
The minute you say "instantaneous communication", we can throw out the idea as being impossible under our current knowledge of physics. It's a problem of "causality".
Basically, here's how it works. You've got two events, separated in time and space. Say, I sneeze, and somebody at Alpha Centauri falls out of his chair three years later (three years in both people's rest frames. let's assume they're not moving relative to each other). Relativity says the relative time between those events can be shifted by up to (speed of light)*(rest distance between objects). (I can work out the math and post something if people are interested, and it's not just theory, it's been observed many-a-time) For our sneeze/chair situation, that's four years. This means that you, on the far away star can have fallen out of your chair and be well on your way to paying that hospital bill long before I ever sneeze. This is called a "spacelike separation", because you can't say which order two events happened in.
Ok, now let's say we have an instant communications system. We have a transmitter and a receiver (one here, one on alpha centauri), both with a bomb on them. When you press the button on the transmitter, it blows up the receiver. But not before the receiver sends a signal back saying "ok, I'm about to blow up, you can go ahead and blow up yourself". This is all fine and dandy in the rest frame, but if we're moving quickly, the receiver gets its signal before the transmitter sends it, just as how you fell out of your chair before I sneezed! The receiver sends its message to blow up the transmitter, it blows up, but the problem is, the transmitter never sent its message.
I'm sure there are holes in my thought experiment, but it's the best I could come up with on short notice;-) There are better ones, I'm sure, but you get the picture. As far as we know, if you can send a message faster than light can, you more or less break the universe.
please don't mod this as funny
Looks like somebody noticed that funny mods don't get ya karma anymore;-)
Right now, between the ESA and us, there are 4 different EELV class boosters. All of them are throttle-able, minimally staged (I believe all two stage), and are all pretty cheap. The Ariane 5, the Delta 4, the Atlas V and the SpaceX Falcon 9. Then there's the russian's stuff.
My question is this: why do we need to build a new "space program"? Why can't we build new rockets, and capsules for those rockets, allowing us to switch capsules when better capsule tech comes about, and better rockets when better rocket tech comes about? Keep competition going, it'll be good for the industry.
Mercury flew on different rockets. So did Apollo. Soyuz flew on various forms of the Soyuz booster, and a handful of times on Protons in the (never got past the testing phase) Zond program. CEV should be the same way.
The escape rocket should be able to abort the mission through the point in the ascent when the main propulsion of the capsule itself can continue the abort. In other words, the system should be (and was, in the Apollo days) able to get the capsule off the stack until the last stage separates from the capsule.
I'd hope that the CEV is going for the same level of safety.
Getting money back from anybody is hell. What you CAN do is refuse to pay a certain charge when the bill gets to you. Things actually get cleared up pretty quickly that way.
You just made all that up, didn't you. "1.9 amps/hz"? A dime sized-reader? I don't know of a dime-sized much anything. A dime is really, really small. And 64.2W is a shitload of power. If my credit card is broadcasting with more power than my car's amateur radio transmitter, there's something horribly wrong, and you'd be able to pick it up in the next county, not "3000 yards".
Man, the mod system here is broken...
As others have mentioned, Cocoa is just the NeXT API, very minimally changed. In fact, this becomes VERY apparent looking at the names of the API calls. Everything's in the form of NSWindow and NSRegion, NS standing for NeXTSTEP.
The Wikipedia! The best karma whoring invention since Google.
The XLR's mother car, the Corvette (back to at least the '99 C5) has this too. You slide the little switch to "passive" mode on the key, and it'll unlock the door when you get near the car.
Still have to start the car with the key, though.
On the Lexus (at least on my IS), while there are only a few mechanical keys that are in circulation, each key needs a radio transponder in it that's interrogated to start the car. The ID is specific to the key, but you can tell the car (through a bizarre song and dance involving turning the key a couple of times and pumping the accelerator) to allow a new key to pair with the car.
So, you can add a key to the car, but you need at least one key to get the thing in the programming mode. They don't store that code anywhere, so if you lose all four keys it came with, you have to buy a new ECU. Really, really expensive. Also hard to steal.
At this point, there's very little information available about which products will and will not survive the merger. Why would any shareholder approve a merger when all he/she knew was that the two companies were to merge?
I usually just dump the oil out of it. The smell lets me know when it's off.
You are correct in that the TV sats are in GEO, but TDRSS and the weathersats are too. Hell, GOES stands for Geostationary Operational Environmental Satellite.
Note that you can write a Java app on OS X that uses AppKit and looks, feels and runs like a full-fledged OS X app. There are probably apps you use every day and don't notice that they're written in Java.
However you are correct about Swing apps. They're ugly as sin.
The HP iPods are simply rebranded iPods. They come off the same assembly line as the standard Apple branded iPod. The advantage to this situation is that Apple gets access to the HP distribution channel for the iPod, getting their device in every store with HP contracts, and shipping an iPod as a build-to-order option on HP computers.
I've found that the tolerance for this sort of thing varies wildly from place to place. I've got blue hair. (well, half of it) I'm originally from Dallas where you certainly will get funny looks and nobody seems to take you seriously, but in California, it's pretty much a non-issue. Yes, I am a college student, so that helps, but I'm an engineering student where you have to put on a suit (I tend to wear a shirt with it that matches my hair. It adds to the effect. Sort of the whole anime villain thing.) and give a presentation to a bunch of surgeons on the instrument you just designed that they're going to use.
I had to let it wash out before going home to salvage my chances of getting a job.
Shit. As a native Texan living in California, I feel I must object to one of these insults. Unfortunately, I can't quite decide which one isn't true...