Very predictable. Nothing will change there either. Non-IEEE floating point vector instructions, or "multimedia" instruction sets will probably continue to be unstandardized and platform-dependent. This shouldn't worry you on x86 since 3DNow!, SSE and SSE2 all conform to the IEEE spec.
I've worked for a large, safety-critical, government beaurocracy in my time, and I can assure you it didn't know what it was doing, especially when buying technical goods and services. I doubt the US military is much different.
Unfortunatley, what with Linux (and GNU) being Free and collective efforts, and popular in Europe, South America and Asia, it has the "pinko commie hippy" stigma attached to it in conservative circles. Don't expect any progress from the US govenrment any time soon.
He goes on to explain that the ashtray costs $400 to research and to make; however, whenever you are in a sub, the ashtray won't break into millions of bits during combat action.
Very interesting. How does this relate to Microsoft software? *ducks*
...because a 64-bit machine could "see" all the data at once (in a single 64-bit segment - fast) whereas a 32-bit one would have to share it between several address spaces (32-bti segments) and switch back and forth between them (slower) to get at the data.
2GB kernel, 2GB user. OK maybe 1GB kernel, 3GB user, but it's that order of magnitude. As for slow and hacky, I remember the 286. You young 'uns don't know you're born...
Say I've got a 32-bit Penitum 4 which has 32-bit address registers. The machine has a 36-bit address bus, so it can access 16*4GB of physical memory. That's 64GB of RAM. My operating system takes up 1 gigabyte of the processes adress space, leaving 3 gigabytes to the process. My process wants to allocate 8 gigabytes of RAM. How do you address 8 gigabytes of RAM with a 32-bit pointer? How do you map 8 gigabytes into a 4 gigabyte address range? Now, I have a 64-bit CPU that has 40 of its address pins wired up. It has 64 gigabytes of memory. The kernel takes up 1 gigabyte of process address space. My application wants 8 gigabytes of RAM. It has 64-bit pointers.
So, wiseguy, how does your 32-bit machine do it? Does it by any chance allocate four 2 gigabyte "chunks" (segments?) of memory, and select each as needed? Isn't this how the 80286 with it's 16-bit address registers got around the 64k limit? Have we come full circle?
(1) Quite a few, mainly CAD and scientific users.
(2) Yes. I write kernel code
(3) Yes. Do you know about segmented memory? Do you know how the 8086, 80186 and 80286 (all 16-bit CPUs) accessed more that 64k of RAM? Have you ever programmed for MS-DOS or Windows 3.1? I have.
(4) Every one else has had 64-bit CPUs since the 1990s. UltraSPARC, MIPS, Alpha, PA-RISC, intel i960 (actually, 1980s!), POWER....
Let me ask you this: are you a dumb troll, or is that a stupid question?
However, Apple have the marketing power, user base, application software, user-friendliness and pretty GUI to make a commercial success of their 64-bit desktop machines (which, incidentally, run at a competitive speed).
And what's more, when you start running programs that use more than 2GB of data, the 64-bit machine is going to beat the pants off the 32-bit one, since the 32-bit machine (i.e. intel) is going to have to resort to slow and hacky solutions such as segments and paging. The intel may me "faster" but only as long as 32-bit are enough for you. The days of 32-bit machines are numbered, just as they were for 16-bit machines when 32-bit machines started to appear.
Don't you know that these guys cross-bred with the aliens! That's where they got 7 fingers from and hence 7-bit binary. The binary codes were calculations of landing and take-off trajectories for the flying-saucers. There's even one where they factor in the mass of Jesus as one of the passengers.
You'll be pleased to hear that not long after that company got into serious financial difficulties, cut everyones wages in half (and got sued for constructive dismissal by loads of people) and closed a load of stores. They're now the subject of hostile takeover bids.
My experience was that the women got away with having things like purple hair (which was specifically against the dress code) whereas one poor man got sacked because his trousers were the wrong shaded of grey. They weren't "dark" enough.
If people adopted PNGs wholesale Microsoft would be forced to fix their buggy software. However the wold doesn't work like that. People have become too used to having to alter their way of working to fit around the limitations of Microsoft's software now. It's become an accepted way of life and deeply ingrained in our culture. It will take many generations to change.
If you're a woman you can probably get away with it. Mnay traditional, large companies are very strict about how men dress and have their hair etc. but apply much less rigorous rules to their female staff. It's a horrendous and blatant display of double-standards and anti-male discrimination. Maybe it is a relic from the days when people only considrered males to be serious employees and women to be less important? Who knows. I used to work for one of them. When I left I grew my hair. It's half way down my back now and I'll only lose it naturally to alopecia! Finding a good professional job has not been a problem. I think you'll find that the people (companies) who are most successful are the ones that are nicest to work for, and treat their staff with dignity and respect and as individuals.
It depends how fast you are going. 300ft at 70mph is approximately the minumum safe distance to leave between cars to enable them to take the appropriate action in the event of an emergency. If everyone knew this and stuck to it there would ba a heck of a lot less accidents on the motorways.
A lot of people are already lousy drivers. What they also need is a system that detects the proximity of cars behind, to prevent tailgating (the number of times some w***er has been driving 3 feet behind me on the motorway and nearly killed me...). It would use a radar to detect approaching cars and put on the brake lights (not the brakes) to make the maniac approaching slow down and back off when he got too close for safety.
Yeah, I know. I only went on a course once and ran the kernel debugger for a few hours during the course of the week and it was over a year ago. I wrote a small device driver module and watched it execute, passing things up and down a stream. That doesn't really count. I suppose if I'd want to know about a real OS I'd have studied NT like everyone else? For you irony-impared Americans, that was tongue in cheek.
I'm not basing my hatred of Windows on kernel debugging. There's so much wrong with Windows, I just cannot think where to start. Everything about Windows is "dumbing down" the experience from the user and in doing so removing power from them. A UNIX system is an incredibly rich and flexible (and extensible) tool. It's very empowering. WIndows is all smoke and mirrors, trade secrets, treating the user as a moron etc. As someone who uses computers every day to do work, I just can't imagine how I'd get 1/10th the work done on a Windows box, without substantial expensive 3rd-party add-ons (mainly software). The last time I used Windows at work was NT4 in 2000. I found it so primitive, buggy, unstable and restrictive compared to Linux and Solaris. I know Windows has improved some what, however it's still an expensive toy compared to Linux and Solaris. On a UNIX machine, everything's there, it's documented and it just works. Most of the software is Open Source or Free. Everything conforms to standards. If you don't like one system, you can move over to another e.g. fed up with Linux? Try Free BSD. Want an enterprise server with a support contract? Move up to Solaris. Need a real-time embedded POSIX kernel? Get QNX. Want to run on a small ARM machine? Get Net BSD.... and KEEP YOUR EXISTING SOFTWARE.... and we haven't mentioned 64-bits yet, have we? There have been 64-bit UNIXes for over 10 years now. They're mature. Where is Windows? What about porting your applications? Which processor? Do you have a choice other than itanic? Good luck.
Slashdot Mirror
Very predictable. Nothing will change there either. Non-IEEE floating point vector instructions, or "multimedia" instruction sets will probably continue to be unstandardized and platform-dependent.
This shouldn't worry you on x86 since 3DNow!, SSE and SSE2 all conform to the IEEE spec.
Exactly what would a manned mission to Mars get us?
In a word : inspiration
I've worked for a large, safety-critical, government beaurocracy in my time, and I can assure you it didn't know what it was doing, especially when buying technical goods and services. I doubt the US military is much different.
Unfortunatley, what with Linux (and GNU) being Free and collective efforts, and popular in Europe, South America and Asia, it has the "pinko commie hippy" stigma attached to it in conservative circles. Don't expect any progress from the US govenrment any time soon.
He goes on to explain that the ashtray costs $400 to research and to make; however, whenever you are in a sub, the ashtray won't break into millions of bits during combat action.
Very interesting. How does this relate to Microsoft software? *ducks*
Imagine if they'd spent that amount of money on a space shuttle replacement, or a manned^H^H^H^H^H^Hpersonned mission to Mars.
...because a 64-bit machine could "see" all the data at once (in a single 64-bit segment - fast) whereas a 32-bit one would have to share it between several address spaces (32-bti segments) and switch back and forth between them (slower) to get at the data.
2GB kernel, 2GB user. OK maybe 1GB kernel, 3GB user, but it's that order of magnitude. As for slow and hacky, I remember the 286. You young 'uns don't know you're born...
Say I've got a 32-bit Penitum 4 which has 32-bit address registers. The machine has a 36-bit address bus, so it can access 16*4GB of physical memory. That's 64GB of RAM. My operating system takes up 1 gigabyte of the processes adress space, leaving 3 gigabytes to the process. My process wants to allocate 8 gigabytes of RAM. How do you address 8 gigabytes of RAM with a 32-bit pointer? How do you map 8 gigabytes into a 4 gigabyte address range?
Now, I have a 64-bit CPU that has 40 of its address pins wired up. It has 64 gigabytes of memory. The kernel takes up 1 gigabyte of process address space. My application wants 8 gigabytes of RAM. It has 64-bit pointers.
So, wiseguy, how does your 32-bit machine do it? Does it by any chance allocate four 2 gigabyte "chunks" (segments?) of memory, and select each as needed? Isn't this how the 80286 with it's 16-bit address registers got around the 64k limit? Have we come full circle?
(1) Quite a few, mainly CAD and scientific users.
(2) Yes. I write kernel code
(3) Yes. Do you know about segmented memory? Do you know how the 8086, 80186 and 80286 (all 16-bit CPUs) accessed more that 64k of RAM? Have you ever programmed for MS-DOS or Windows 3.1? I have.
(4) Every one else has had 64-bit CPUs since the 1990s. UltraSPARC, MIPS, Alpha, PA-RISC, intel i960 (actually, 1980s!), POWER....
Let me ask you this: are you a dumb troll, or is that a stupid question?
However, Apple have the marketing power, user base, application software, user-friendliness and pretty GUI to make a commercial success of their 64-bit desktop machines (which, incidentally, run at a competitive speed).
And what's more, when you start running programs that use more than 2GB of data, the 64-bit machine is going to beat the pants off the 32-bit one, since the 32-bit machine (i.e. intel) is going to have to resort to slow and hacky solutions such as segments and paging. The intel may me "faster" but only as long as 32-bit are enough for you. The days of 32-bit machines are numbered, just as they were for 16-bit machines when 32-bit machines started to appear.
Every time I see a slashdot headline with the word "homebrew" in it I think that at last there's an article about beer, but no :-(
Don't you know that these guys cross-bred with the aliens! That's where they got 7 fingers from and hence 7-bit binary. The binary codes were calculations of landing and take-off trajectories for the flying-saucers. There's even one where they factor in the mass of Jesus as one of the passengers.
Wasn't that a Nazi cartoon? Didn't he come from "New Texas" and defend earth against the Bendars?
You'll be pleased to hear that not long after that company got into serious financial difficulties, cut everyones wages in half (and got sued for constructive dismissal by loads of people) and closed a load of stores. They're now the subject of hostile takeover bids.
My experience was that the women got away with having things like purple hair (which was specifically against the dress code) whereas one poor man got sacked because his trousers were the wrong shaded of grey. They weren't "dark" enough.
If people adopted PNGs wholesale Microsoft would be forced to fix their buggy software. However the wold doesn't work like that. People have become too used to having to alter their way of working to fit around the limitations of Microsoft's software now. It's become an accepted way of life and deeply ingrained in our culture. It will take many generations to change.
If you're a woman you can probably get away with it. Mnay traditional, large companies are very strict about how men dress and have their hair etc. but apply much less rigorous rules to their female staff. It's a horrendous and blatant display of double-standards and anti-male discrimination. Maybe it is a relic from the days when people only considrered males to be serious employees and women to be less important? Who knows. I used to work for one of them. When I left I grew my hair. It's half way down my back now and I'll only lose it naturally to alopecia! Finding a good professional job has not been a problem. I think you'll find that the people (companies) who are most successful are the ones that are nicest to work for, and treat their staff with dignity and respect and as individuals.
It depends how fast you are going. 300ft at 70mph is approximately the minumum safe distance to leave between cars to enable them to take the appropriate action in the event of an emergency. If everyone knew this and stuck to it there would ba a heck of a lot less accidents on the motorways.
A lot of people are already lousy drivers. What they also need is a system that detects the proximity of cars behind, to prevent tailgating (the number of times some w***er has been driving 3 feet behind me on the motorway and nearly killed me...). It would use a radar to detect approaching cars and put on the brake lights (not the brakes) to make the maniac approaching slow down and back off when he got too close for safety.
You forgot EISA, the 16MHz, 32-bit backwards-compatable successor to 16-bit ISA.
...after they released 3 albums of Country and Western of their own and have just started doing Heavy Metal again.
Yeah, I know. I only went on a course once and ran the kernel debugger for a few hours during the course of the week and it was over a year ago. I wrote a small device driver module and watched it execute, passing things up and down a stream. That doesn't really count. I suppose if I'd want to know about a real OS I'd have studied NT like everyone else? For you irony-impared Americans, that was tongue in cheek.
I'm not basing my hatred of Windows on kernel debugging. There's so much wrong with Windows, I just cannot think where to start. Everything about Windows is "dumbing down" the experience from the user and in doing so removing power from them. A UNIX system is an incredibly rich and flexible (and extensible) tool. It's very empowering. WIndows is all smoke and mirrors, trade secrets, treating the user as a moron etc. As someone who uses computers every day to do work, I just can't imagine how I'd get 1/10th the work done on a Windows box, without substantial expensive 3rd-party add-ons (mainly software). The last time I used Windows at work was NT4 in 2000. I found it so primitive, buggy, unstable and restrictive compared to Linux and Solaris. I know Windows has improved some what, however it's still an expensive toy compared to Linux and Solaris. On a UNIX machine, everything's there, it's documented and it just works. Most of the software is Open Source or Free. Everything conforms to standards. If you don't like one system, you can move over to another e.g. fed up with Linux? Try Free BSD. Want an enterprise server with a support contract? Move up to Solaris. Need a real-time embedded POSIX kernel? Get QNX. Want to run on a small ARM machine? Get Net BSD. ... and KEEP YOUR EXISTING SOFTWARE.... and we haven't mentioned 64-bits yet, have we? There have been 64-bit UNIXes for over 10 years now. They're mature. Where is Windows? What about porting your applications? Which processor? Do you have a choice other than itanic? Good luck.