To be fair, IIRC, Alpha's x86 emulation could actually run about as fast as the fastest x86 machines back then...
But, Alpha ran at literally DOUBLE (or more) the clock speed, and had roughly equal integer IPC and better floating point IPC.
ARM has a clock speed deficit and somewhere in the same IPC ballpark as Atom, the weakest of the current x86s.
They are working on that, though. And, ARM did start out as a couple engineers at Acorn designing a custom CPU for a desktop machine, and they had one of the fastest desktop chips by a LOT when it came out. (They were gunning for the Amiga and the like, and an 8 MHz ARM2 just SLAUGHTERED the 7 MHz 68000. Yes, the 386 was about as fast at 25 MHz or so. But in 1987, a comparable 386-based machine was several times more expensive.)
I'd like to see ARM be a viable alternative to x86, but I don't think it's happening for a while. Windows is necessary, and that won't happen until ARM is fast enough to emulate x86 at near-Atom speeds. Good news is, an ARM in the Atom power envelope could probably do that.
If we want to get picky, it's only implemented properly and completely in RISC OS, everyone else only partially implements it. (And ROX Desktop apps on Linux have similar behavior, but that's a very small subset.)
(RISC OS save dialogs don't even have any filing system management in them. You navigate to the folder you want to save the file in in the Filer (very VERY roughly similar to the pre-OS X Finder, but completely different. Hard to explain.) Then, you drag the icon from the save dialog to the directory. You can also type out a full pathname if you want, though.)
IIRC, BlackBerries do run their JVM (which the OS runs under) right on the baseband, just like your average Nokia brick. So, that's an exception to smartphones having separated baseband and application processors.
(My own phone (an HTC Touch Pro,) OTOH, has separated baseband and application CPUs, yet they share a die. So, it's a dual core, one ARM9 for baseband, one ARM11 for application. Works just like you describe, just uses less PCB space.)
Although, IIRC, the baseband on the iPhone has been broken, too. You'd have to jailbreak to get there, but... there are other phones that likely have just as vulnerable basebands that aren't locked down.
Although, Verizon isn't using W-CDMA at all, that's used by UMTS and its descendants, part of the GSM 3G protocols. (Which the iPhone (3G and 3GS) DOES use.)
Verizon is using IS-2000-compliant CDMA, which is unrelated, only having code division multiplexing in common.
That said, I'm not sure whether IS-2000 is vulnerable to the same attack or not.
Just to make everything crystal clear and expand on your post some...
UMTS/HS*PA use a code division multiple access scheme, but not the exact (CDMA-based) protocol that is commonly referred to as "CDMA," formally known as IS-95 (pre-1xRTT) and IS-2000 (1xRTT and EVDO.)
Also, the first iPhone also supports EDGE, which is GPRS with different encoding methods available (GPRS being a data standard using spare GSM time-divided channels to perform its transmissions.)
webOS requires you to plug it into a computer, and transfer the app over USB. Also, you have to put it in developer mode, IIRC, which is the Konami code.
Of course, there are apps out there that let you download other apps OTA, once you've got that installed.
(I don't have a Pre, though - I've got an HTC Touch Pro, so I don't have to worry about that.)
But I'll take a weakly designed platform that lets me run whatever I want over an excellently designed platform that is restrictive.
And then, said "excellently designed platform" has some MAJOR drawbacks... like no multitasking. And the hardware that it comes on has no physical keyboard.
Whenever I buy music (which is very rarely,) I extensively research the artist, their label, and all to make sure not a single penny goes to the RIAA. For that matter, I don't even pirate RIAA stuff - a boycott is ineffective in a case like this unless the MARKET for the content is destroyed, not just the producers, and that requires reducing the amount of mindshare the content gets, which means not playing their content at all.
Get an indication of how many windows a program has open Have the ability to switch windows within a program from the taskbar, just like XP/Vista's program grouping, rather than dicking around with Command-`. (That said, I wouldn't mind the ABILITY to use an Alt-` shortcut to switch windows within a given program.)
And, it's more space efficient horizontally than the 95-Vista taskbar layout.
Actually, yes, there is such technology to degrade quality of some content when not using an HDCP-compliant display, to reduce quality of rips made by sniffing the monitor connection. (Of course, they're forgetting about LVDS. You can pop open an HDCP-compliant display, unplug the bare panel from the controller, and make a dummy panel that just gets the pixels decoded from the controller. Or, do it to a laptop with an HDCP-compliant GPU. Digital holes are a bitch like that, you can always get to whatever's driving the pixels, and IIRC, it's actually harder to decode TMDS than it is LVDS - hence why the panel is driven by LVDS.)
Don't treat illnesses. You do get the depreciation of happiness, but you get the drop in population, with less cost than curing aging or mandatory contraceptives (or even abortions.)
The IBM BASIC being referred to is Microsoft BASIC, which in 1981, damn near everyone used. And from what I've seen and heard, it was the Windows 95 of BASIC interpreters. Shiny features (ooh, floating point,) but not all that good, but good enough for most people.
OS/2... that was a decent product, although with some architectural design flaws. OS/2 1.3 fixed one design flaw that's Microsoft's fault (and it's not necessarily a flaw, especially by late 1980's/early 1990's standards - the GDI ran in the kernel, rather than in userland. Nowadays, that is a flaw, though,) Windows NT 3.1 fixed an arguably bigger flaw (single input queue, one program could effectively hang a preemptive multitasking system by hogging the input queue) but reintroduced the GDI and kernel merging. (As a side note, Windows NT 6.0 (Vista/Server 2008) split the GDI out of the kernel, IIRC.)
Apple just stole that bit of awesome usability from KDE (same place they got WebKit, for that matter,) where to get KDE apps to respect your choice of default browser, I recall having to set Opera (my browser of choice) as the default browser in Konqueror...
I'm beginning to think that the US should start moving towards more power moved to governments with smaller regional influence. Counties having the power that federal governments have now, and the federal government basically being like an EU of counties.
The submitter mentioned no HDD, and I could believe that it didn't have one at all.
Anyway, HDD interfaces back then were usually ST-506 style.
Now, if it did have one, and you had a more modern PC that still had an ISA slot, you could use it that way. Alternately, you could get an ATA controller for the machine.
The second sentence hid my point. I'll state it a little more clearly...
File locking is file locking. If you're getting burned by it regularly enough to use a drastically less robust filesystem, you probably shouldn't be messing with those files anyway.
(And, there are unlocker tools out there.)
Oh, and while NTFS does have one weak point that can result in corruption... FAT32 is a lot more susceptible to corruption than NTFS. That's like buying a Chrysler minivan over a Honda minivan because the Honda's transmission is known for failing in a certain way. The Chrysler's transmission is known for failing in worse ways, and the rest of the van sucks, too. (Accurate car analogies FTW.)
Mandate the <video> tag, don't mandate ANY codecs whatsoever, but mandate that browsers support user-loadable codecs in some manner, and mandate that the browser developer link to the appropriate codecs as needed.
Slashdot Mirror
To be fair, IIRC, Alpha's x86 emulation could actually run about as fast as the fastest x86 machines back then...
But, Alpha ran at literally DOUBLE (or more) the clock speed, and had roughly equal integer IPC and better floating point IPC.
ARM has a clock speed deficit and somewhere in the same IPC ballpark as Atom, the weakest of the current x86s.
They are working on that, though. And, ARM did start out as a couple engineers at Acorn designing a custom CPU for a desktop machine, and they had one of the fastest desktop chips by a LOT when it came out. (They were gunning for the Amiga and the like, and an 8 MHz ARM2 just SLAUGHTERED the 7 MHz 68000. Yes, the 386 was about as fast at 25 MHz or so. But in 1987, a comparable 386-based machine was several times more expensive.)
I'd like to see ARM be a viable alternative to x86, but I don't think it's happening for a while. Windows is necessary, and that won't happen until ARM is fast enough to emulate x86 at near-Atom speeds. Good news is, an ARM in the Atom power envelope could probably do that.
If we want to get picky, it's only implemented properly and completely in RISC OS, everyone else only partially implements it. (And ROX Desktop apps on Linux have similar behavior, but that's a very small subset.)
(RISC OS save dialogs don't even have any filing system management in them. You navigate to the folder you want to save the file in in the Filer (very VERY roughly similar to the pre-OS X Finder, but completely different. Hard to explain.) Then, you drag the icon from the save dialog to the directory. You can also type out a full pathname if you want, though.)
IIRC, BlackBerries do run their JVM (which the OS runs under) right on the baseband, just like your average Nokia brick. So, that's an exception to smartphones having separated baseband and application processors.
(My own phone (an HTC Touch Pro,) OTOH, has separated baseband and application CPUs, yet they share a die. So, it's a dual core, one ARM9 for baseband, one ARM11 for application. Works just like you describe, just uses less PCB space.)
Although, IIRC, the baseband on the iPhone has been broken, too. You'd have to jailbreak to get there, but... there are other phones that likely have just as vulnerable basebands that aren't locked down.
Although, Verizon isn't using W-CDMA at all, that's used by UMTS and its descendants, part of the GSM 3G protocols. (Which the iPhone (3G and 3GS) DOES use.)
Verizon is using IS-2000-compliant CDMA, which is unrelated, only having code division multiplexing in common.
That said, I'm not sure whether IS-2000 is vulnerable to the same attack or not.
Just to make everything crystal clear and expand on your post some...
UMTS/HS*PA use a code division multiple access scheme, but not the exact (CDMA-based) protocol that is commonly referred to as "CDMA," formally known as IS-95 (pre-1xRTT) and IS-2000 (1xRTT and EVDO.)
Also, the first iPhone also supports EDGE, which is GPRS with different encoding methods available (GPRS being a data standard using spare GSM time-divided channels to perform its transmissions.)
webOS requires you to plug it into a computer, and transfer the app over USB. Also, you have to put it in developer mode, IIRC, which is the Konami code.
Of course, there are apps out there that let you download other apps OTA, once you've got that installed.
(I don't have a Pre, though - I've got an HTC Touch Pro, so I don't have to worry about that.)
But I'll take a weakly designed platform that lets me run whatever I want over an excellently designed platform that is restrictive.
And then, said "excellently designed platform" has some MAJOR drawbacks... like no multitasking. And the hardware that it comes on has no physical keyboard.
Actually, there's another possible defense, bypassing soap, ballot, and jury.
Ammo.
If you're facing millions of dollars of damages and can't afford to effectively defend yourself, your life is effectively ruined.
So, go out with a bang.
Whenever I buy music (which is very rarely,) I extensively research the artist, their label, and all to make sure not a single penny goes to the RIAA. For that matter, I don't even pirate RIAA stuff - a boycott is ineffective in a case like this unless the MARKET for the content is destroyed, not just the producers, and that requires reducing the amount of mindshare the content gets, which means not playing their content at all.
And in this case, the user is TRYING to negate the point of the hotel firewall.
Unlike the OS X dock, though, you:
Get an indication of how many windows a program has open
Have the ability to switch windows within a program from the taskbar, just like XP/Vista's program grouping, rather than dicking around with Command-`. (That said, I wouldn't mind the ABILITY to use an Alt-` shortcut to switch windows within a given program.)
And, it's more space efficient horizontally than the 95-Vista taskbar layout.
32-bit or 64-bit?
Because 64-bit versions of Windows require, IIRC, parameters to be passed at boot and a group policy edit to allow unsigned drivers.
It's a shame Windows Server 2008 R2 isn't available in a 32-bit version... all the benefits of a 32-bit version, and you get to use over ~3 GiB RAM.
Actually, yes, there is such technology to degrade quality of some content when not using an HDCP-compliant display, to reduce quality of rips made by sniffing the monitor connection. (Of course, they're forgetting about LVDS. You can pop open an HDCP-compliant display, unplug the bare panel from the controller, and make a dummy panel that just gets the pixels decoded from the controller. Or, do it to a laptop with an HDCP-compliant GPU. Digital holes are a bitch like that, you can always get to whatever's driving the pixels, and IIRC, it's actually harder to decode TMDS than it is LVDS - hence why the panel is driven by LVDS.)
Take a look here: http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html#quality
I just use VLC for everything, on any OS that supports and runs it well, so it doesn't affect me, but the issue is still there.
Don't treat illnesses. You do get the depreciation of happiness, but you get the drop in population, with less cost than curing aging or mandatory contraceptives (or even abortions.)
The limit would be 867, and the version is Leopard.
And, there's a way to tell OpenFirmware to lie about the processor speed. But, it is still rather arbitrary.
IBM BIOS is terrible, even by 1981 standards.
The IBM BASIC being referred to is Microsoft BASIC, which in 1981, damn near everyone used. And from what I've seen and heard, it was the Windows 95 of BASIC interpreters. Shiny features (ooh, floating point,) but not all that good, but good enough for most people.
OS/2... that was a decent product, although with some architectural design flaws. OS/2 1.3 fixed one design flaw that's Microsoft's fault (and it's not necessarily a flaw, especially by late 1980's/early 1990's standards - the GDI ran in the kernel, rather than in userland. Nowadays, that is a flaw, though,) Windows NT 3.1 fixed an arguably bigger flaw (single input queue, one program could effectively hang a preemptive multitasking system by hogging the input queue) but reintroduced the GDI and kernel merging. (As a side note, Windows NT 6.0 (Vista/Server 2008) split the GDI out of the kernel, IIRC.)
Well, Lenovo's cooling is better than Dell or HP's cooling, so their nVidia GPU failures happen slightly later.
The nVidia GPU failures are nVidia's fault, not Lenovo's.
Apple just stole that bit of awesome usability from KDE (same place they got WebKit, for that matter,) where to get KDE apps to respect your choice of default browser, I recall having to set Opera (my browser of choice) as the default browser in Konqueror...
Windows has called the default web browser, even if it's IE, seperately, since IE 7.
I'm beginning to think that the US should start moving towards more power moved to governments with smaller regional influence. Counties having the power that federal governments have now, and the federal government basically being like an EU of counties.
Hard drive? How quaint.
The submitter mentioned no HDD, and I could believe that it didn't have one at all.
Anyway, HDD interfaces back then were usually ST-506 style.
Now, if it did have one, and you had a more modern PC that still had an ISA slot, you could use it that way. Alternately, you could get an ATA controller for the machine.
ELKS will, though... (And, uClinux will run on some 16-bit processors, just not 16-bit x86.)
The second sentence hid my point. I'll state it a little more clearly...
File locking is file locking. If you're getting burned by it regularly enough to use a drastically less robust filesystem, you probably shouldn't be messing with those files anyway.
(And, there are unlocker tools out there.)
Oh, and while NTFS does have one weak point that can result in corruption... FAT32 is a lot more susceptible to corruption than NTFS. That's like buying a Chrysler minivan over a Honda minivan because the Honda's transmission is known for failing in a certain way. The Chrysler's transmission is known for failing in worse ways, and the rest of the van sucks, too. (Accurate car analogies FTW.)
Of course, there's yet another solution.
Mandate the <video> tag, don't mandate ANY codecs whatsoever, but mandate that browsers support user-loadable codecs in some manner, and mandate that the browser developer link to the appropriate codecs as needed.