I was under the impression most modern machines executed a halt instruction during idle time, which generally reduced their power consumption. They were then woken up when an interrupt went off to signify the beginning on the next time slice/something important happening.
If you actually paid attention, you'd realise that if the architecture was any good, there's absolutely no point in having the entire software stack 64 bit clean, and that it's inefficient in both terms of memory and CPU time.
This is why the majority of old school 64 bit workstations (The SGIs, etc. of this world) have all their apps compiled with 32-bit addressing. They have no problems interfacing with 32-bit librariesyet can still take useful advantage of the 64-bit architecture of the machines.
Only if you're doing protein folding, linking MAME with an optimising linker, or something requiring an equally huge amount of memory, would you actually compile full 64 bit.
Web browsers, etc. come no where near close to the memory requirements at which being 64-bit is an advantage on a well designed platform.
I've said this else where, but I'll say it again here: the only reason you'd want a 64 bit web browser is due to the flaws in the designs of 64 bit x86 instruction sets.
On most 64 bit capable processors, all code can use 64 bit registers and data transfers. Therefore a 32 bit web browser can use a 32 bit flash plug in, and both can perform 64 bit operations. This is faster than pure 64 bit, because it only needs to load 32 bit addresses from RAM.
On these platforms, the only reason you'd use a 64 bit browser and plugins is that they need to use over 2-4GB (dependent on platform). This is, to be frank, an exceptionally silly thing to do with a web browser, and would just slow it down.
It should be noted that outside of the 64 bit flavours of x86, there's little point in 64 bit flash.
On most processors, 32 bit programs and libraries can use 64 bit data transfers/registers. The only reason you'd go for a full 64 bit app is if you need to use over 2 to 4 GB of memory, depending on the platform. A web browser doesn't really need this, so gets a speed advantage from using 32 bit addressing and 64 bit wide data bus.
It's an iPod. You can listen to it at work by putting your headphones on, switching it on, and pressing play.
So again, in what way is this tool useful outside of pirating music?
Yes, you can use the command line to do copy files off, but you can use a brick to break into a car. It isn't the primary purpose of those tools. Nobody in their right mind would bother, because they don't need to - they already have their music on their computer.
This plugin sounds like the equivalent of an autopick, except there isn't any legal reason to use it.
Sorry, but how is this not just a blatant piracy tool?
For what possible reason would I need to use this? My computer can always access the same music the iPod can, seeing as it came from the computer in the first place. My other machines can access the same music either through Bonjour music shares, or by connecting to the file server the files are actually stored on. If I ever lose the machine, I restore from my DVD-R backups. If I'm away from home, it's still not a problem, since that's the whole point of the iPod.
The only use I can see for such a feature is to warez music off a friends iPod - the functionality is utterly redundant otherwise.
And all I want is global domination over men, to live in a palace surrounded by a sea of sapphires, and eat chocolate all day long without getting fat.
Another advantage of using an FPGA is that the hardware is adaptive.
Not using that texture unit? Why not replace it with a second rasterizer? Not using alpha? Hardly worth wasting transistors on it then. Need 16-bits per channel for photoshop? Don't need any of the 3D hardware.
I would have thought with a good modular design, the drivers ought to be able to build the GPU most suited to the users current needs, like building lego.
I find it even more amusing that such comments generally come from Americans, because, of course, there isn't a single US citizen in poverty, oh no. >_<
I thought it was "generally accepted" that the Hindenburg disaster was as big as it was more the genius combination of hydrogen, gun cotton and thermite in the construction, rather than just hydrogen.
Do they not teach you Americans basic quantum physics at school?
Measuring something changes it. Therefore you can't just splice in a repeater into the middle of the fibre, because the act of receiving the photon changes the exact quantum state of what is eventually received the other end. Normal repeaters only work due to them a) not caring so much about the exact quantum state and b) having $FSCKLOADS of particles to work with.
The problem of course is that if the non-free version gets good, others will simply fork.
This assumes that a company that dedicates full time resources to a product is unable to produce anything that would beat the part time input of volunteers.
Slashdot Mirror
It reminds me of last Saturday evening, down my favourite night club ;)
Unfortunately, EMT64 has some really brain dead designs issues with address width that'll kill performance.
No, but I'm sure it'd boogy on down to the repetitive DOOF DOOF DOOF of it's system clock!
Which is great, except Snood was merely a rip off of an old Taito arcade game, Puzzle Bobble.
I was under the impression most modern machines executed a halt instruction during idle time, which generally reduced their power consumption. They were then woken up when an interrupt went off to signify the beginning on the next time slice/something important happening.
If you actually paid attention, you'd realise that if the architecture was any good, there's absolutely no point in having the entire software stack 64 bit clean, and that it's inefficient in both terms of memory and CPU time.
This is why the majority of old school 64 bit workstations (The SGIs, etc. of this world) have all their apps compiled with 32-bit addressing. They have no problems interfacing with 32-bit librariesyet can still take useful advantage of the 64-bit architecture of the machines.
Only if you're doing protein folding, linking MAME with an optimising linker, or something requiring an equally huge amount of memory, would you actually compile full 64 bit.
Web browsers, etc. come no where near close to the memory requirements at which being 64-bit is an advantage on a well designed platform.
I've said this else where, but I'll say it again here: the only reason you'd want a 64 bit web browser is due to the flaws in the designs of 64 bit x86 instruction sets.
On most 64 bit capable processors, all code can use 64 bit registers and data transfers. Therefore a 32 bit web browser can use a 32 bit flash plug in, and both can perform 64 bit operations. This is faster than pure 64 bit, because it only needs to load 32 bit addresses from RAM.
On these platforms, the only reason you'd use a 64 bit browser and plugins is that they need to use over 2-4GB (dependent on platform). This is, to be frank, an exceptionally silly thing to do with a web browser, and would just slow it down.
It should be noted that outside of the 64 bit flavours of x86, there's little point in 64 bit flash.
On most processors, 32 bit programs and libraries can use 64 bit data transfers/registers. The only reason you'd go for a full 64 bit app is if you need to use over 2 to 4 GB of memory, depending on the platform. A web browser doesn't really need this, so gets a speed advantage from using 32 bit addressing and 64 bit wide data bus.
Or they could have used an airship.
Surely there's oodles of prior art back on the old 8-bits?
I fondly remember invaderload on Alpha Centauri!
There is - it's called USB and Firewire.
Well, one assumes that if you have music at work, you have some means of playing it back.
It's an iPod. You can listen to it at work by putting your headphones on, switching it on, and pressing play.
So again, in what way is this tool useful outside of pirating music?
Yes, you can use the command line to do copy files off, but you can use a brick to break into a car. It isn't the primary purpose of those tools. Nobody in their right mind would bother, because they don't need to - they already have their music on their computer.
This plugin sounds like the equivalent of an autopick, except there isn't any legal reason to use it.
Sorry, but how is this not just a blatant piracy tool?
For what possible reason would I need to use this? My computer can always access the same music the iPod can, seeing as it came from the computer in the first place. My other machines can access the same music either through Bonjour music shares, or by connecting to the file server the files are actually stored on. If I ever lose the machine, I restore from my DVD-R backups. If I'm away from home, it's still not a problem, since that's the whole point of the iPod.
The only use I can see for such a feature is to warez music off a friends iPod - the functionality is utterly redundant otherwise.
Actually, I knew a guy from Bradford, UK, who really was like that. Every single word dripped the utmost sarcasm.
"I know exactly where I am! I'm directly above the centre of the Earth!"
Sure - which one do you want to borrow?
And all I want is global domination over men, to live in a palace surrounded by a sea of sapphires, and eat chocolate all day long without getting fat.
:(
About as likely to happen, too, unfortunately
Another advantage of using an FPGA is that the hardware is adaptive.
Not using that texture unit? Why not replace it with a second rasterizer? Not using alpha? Hardly worth wasting transistors on it then. Need 16-bits per channel for photoshop? Don't need any of the 3D hardware.
I would have thought with a good modular design, the drivers ought to be able to build the GPU most suited to the users current needs, like building lego.
I find it even more amusing that such comments generally come from Americans, because, of course, there isn't a single US citizen in poverty, oh no. >_<
I thought it was "generally accepted" that the Hindenburg disaster was as big as it was more the genius combination of hydrogen, gun cotton and thermite in the construction, rather than just hydrogen.
The entire point of the medium is to send only one photon. Therefore it's *all* about quantum physics.
Do they not teach you Americans basic quantum physics at school?
Measuring something changes it. Therefore you can't just splice in a repeater into the middle of the fibre, because the act of receiving the photon changes the exact quantum state of what is eventually received the other end. Normal repeaters only work due to them a) not caring so much about the exact quantum state and b) having $FSCKLOADS of particles to work with.
Actually, I was thinking OS X 8;P
The problem of course is that if the non-free version gets good, others will simply fork.
This assumes that a company that dedicates full time resources to a product is unable to produce anything that would beat the part time input of volunteers.