XP's underlying NT kernel and merging of the Windows 9x interfaces made it useful. Vista's killer apps are better security (which admittedly needed a new OS release), DRM (which is not the same thing as security, but tends to be linked), and their XML based file system "WinFS" which seems to have been appropriapriately discarded.
There is no "killer app" that demands Vista. Expect XP to last as long as or longer than Windows 98 and Windows 2000.
The basic physics was common knowledge since the first germanium crystal radios, and since Tesla's work. The engineering side of a cheap and efficient receiver has always been difficult.
There's a major mistake in the little blurb in The Fine Article, though. The reflections off the wall do not change the frequencies of the transmitted waves: they do smear the shape of the waves, and mess up the phases of the components, and make it more difficult to tune the receiver to recover the power efficiently. 70% efficiency in such a device would be quite amazing: I'd love to see if they measured it correctly, and didn't cook the numbers the same way Microsoft cooks their sales results for Vista.
Such technologies have been in use for years, for pacemakers, cochlear implants, and other embedded medical devices. They're not hard to make. Of course, if you have such a device implanted, you *cannot* be safely put in an MRI. The shifting magnetic fields will couple to the embedded loops in the device and drive masses of current through it, destroying it and potentially overheating it. If the coupling is strong enough, such as if a magnet is in the device, then the MRI will couple *mechanically* to the device, and can rip it completely out of your twitching, charred flesh.
It's a real concern: the signs are up all over the MRI chamber warning people with such devices never to go near them.
You don't meet many bible-thumping Baptists, do you? They do some serious hellfire and damnation in their sermons, especially when talking about the Catholics.
There are far more secretive ways to track things: control over the international routers allows black-holing domains and sites, and rerouting or echoing their traffic to permit complete analysis of all traffic from them. Take a look at tools listed at www.sandstorm.com to see what is available, commercially, for such traffic analysis both recorded for later probing and real-time analysis with control of the routers and the kind of warrant-free tapping of internet backbones as has already been discovered.
No, control over the core DNS tables is to allow fast cutting off of any sites you want to block. It's a censorship tool, not a monitoring tool.
Ahh yes. Then there's the Marathon 2 rocket-launch trick: firing a rocket propels the player backwards. Badly handled, this could push you right off into the poison or lava. But there was at least one point in the game where you had to walk over a high wall into a valley where dozens, even hundreds of aliens would appear and waste all your ammo with you, leaving you beaten and bleeding to enter the next level, and the last save point was at least 5 minutes of play before that point.
It was extremely painful to deal with until I worked out how to walk off the edge, trigger the aliens to show up, blow myself backward onto the edge with the rocket, then wait while the aliens started shooting at each other. Then I could hop down and mop up the mess with a much, much smaller bucket, sometimes even just a dishrag instead of the Zamboni previously required.
There's also an amazingly funny video trailer for Team Fortress 2, that involves soldiers bouncing and spinning across the sky by rocket launching themselves, with a water ballet soundtrack. Watching them land gracefully in a neat row and the last one breaking his leg with an audible "snap" is amazingly funny to watch.
Unfortunately, the owners of the intellectual property have used their market dominance to hinder any potential competition. The "dumping" in competitor's markets has been especially destructive. I'm afraid we'll have to wait for the owners' business plan to destroy them utterly before any other effective competition can occur.
Oh, yes. Even with licensed software, managing the licenses is amazingly painful with all the different approaches to licenses.
Other such bugs are amazingly painful internal trouble ticket or purchasing systems: they're so painful they force employees to waste their own money on small purchases and leave purchasing departments either unbothered by requests, or able to steer requests to their "preferred" vendors.
And systems where security is so poor that people simply leave all files accessible to each other do make it easy to sniff other people's email for relevant documents when they're not in the office.
Run your Windows in a virtual environment, behind a firewall in the virtual server. Then use the updated OS image as your canonical installation image.
This would work better if it were easier to register the license keys remotely, but it's workable.
No, BSD is still quite active, including the one inside Apple these days. But the testers were probably unable to install OpenBSD on any hardware less than 8 years old: that OS does *not* have a sane installer or compatibility with a lot of more modern components.
Go ahead, get an off-the-shelf USB wheel-mouse working on OpenBSD without spending at least 2 days hand-building kernels and other components.
For the cost of wasting 5 hours on the phonen of one of my technical peers, I can often contact the *author* of the open source tool and pay them for one hour of support time, at a substantial savings to my personal or my employer's bottom line.
Next time, start the clock and measuer how long it takes. From harsh, harsh experience, the forum is faster. The last 3 MS support calls I made took at least 3 levels of escalation to get to the engineers I needed to talk to. It's even worse when I'm calling to report a bug and a workaround: I don't get credit for the fix, the fix if ever eventually provided is not properly described in the "update" list, and the bug report often vanishes into the void.
Google and public Wikies are often far, far, far faster and more detailed than the Microsoft tech support, especially for the more obscure subtleties of hardware and software interactions among products from different vendors.
The policy is known as "embrace and extend": in practice, it's "embrace and extend and break compatibility". The extensions seem to quite deliberately violate the existing standards: this has occurred repeatedly, with Kerberos (which required a serious patch in MIT's oritingal version to inter-operate with Microsoft's bastardized version), with DNS and DHCP (don't get me started on this one, I had to deal with it last week to show how easy it is to steal a Window's machine's hostname if you use Active Directory's built-in DHCP).
It's been tough. It has to scale well, deal with small payments, be reasonably secure, and have enough profitability to get the equipment set up and the salaries paid.
Hmm. If anyone could trust them with money, PirateBay would be in an amusingly MPEG patent-free environment to do this.
You do know that the more serious lawsuits involved the fact that much of NT was written by David Cutler, one of the core authors of VMS, who took his merry gang of software pirates Microsoft hired away from DEC when DEC canned some of David's software projects? There are lots of old articles about it: look up "david cutler", "VMS", and "Windows NT".
It's not the Bugzilla search: it's the bug authors who cannot be convinced to use a consistent format on submitting bugs. "What's wrong with my system" is not a useful title for a bug.
Parallel processing is fine and useful. It is also vastly, vastly, vastly tougher to fully test and support, especially in such a wild and woolly environment as system boot: people have been hand-inserting all sorts of oddnesses in there, and the robustness is a testament to the wisdom of keeping it simple and single-threaded.
It's useful for laptops, where every erg of boot-time energy is essentially wasted. Keep an eye on the One Laptop Per Child project for related work. They're actually using a Linux based BIOS.
It's also useful for micro-Linux implementations, for cell phones, routers, firewalls, etc.
It's also useful for testing environments and co-location uses where the manpower wasted connecting up and doing boot time operations also costs a lot of work and money.
And it's fun to show off while tools like Vista are booting in layer after layer of memory gobbling and unwanted "optimizers" and "pre-indexers" that mean the pretty login screen shows up, but you can't do any real work for another few minutes until everything is completely pre-loaded.
This is confusing. Russia right now is a big *source* of spammer operations that infest Windows machines and lease time on them to spamming companies. They have sharp programmers and no enforcement of computer security abuses to speak of, and an active criminal underground to launder the money through.
Killing them doesn't seem to be all that helpful so far.
Righteousness is good. But there's something about righteousness automatically winning out in the long run that doesn't work out well. The 9/11 bombers thought they were being "righteous" and destroying the enemies of Allah and of Islam. And the political effects of that have already shaped nations.
Slashdot Mirror
XP's underlying NT kernel and merging of the Windows 9x interfaces made it useful. Vista's killer apps are better security (which admittedly needed a new OS release), DRM (which is not the same thing as security, but tends to be linked), and their XML based file system "WinFS" which seems to have been appropriapriately discarded.
There is no "killer app" that demands Vista. Expect XP to last as long as or longer than Windows 98 and Windows 2000.
No, your llama is full of RAM. And she's going to be really surprised when the crias are born. (Or would they be lambs? Maybe lias? Maybe crambs?)
The basic physics was common knowledge since the first germanium crystal radios, and since Tesla's work. The engineering side of a cheap and efficient receiver has always been difficult. There's a major mistake in the little blurb in The Fine Article, though. The reflections off the wall do not change the frequencies of the transmitted waves: they do smear the shape of the waves, and mess up the phases of the components, and make it more difficult to tune the receiver to recover the power efficiently. 70% efficiency in such a device would be quite amazing: I'd love to see if they measured it correctly, and didn't cook the numbers the same way Microsoft cooks their sales results for Vista.
Such technologies have been in use for years, for pacemakers, cochlear implants, and other embedded medical devices. They're not hard to make. Of course, if you have such a device implanted, you *cannot* be safely put in an MRI. The shifting magnetic fields will couple to the embedded loops in the device and drive masses of current through it, destroying it and potentially overheating it. If the coupling is strong enough, such as if a magnet is in the device, then the MRI will couple *mechanically* to the device, and can rip it completely out of your twitching, charred flesh.
It's a real concern: the signs are up all over the MRI chamber warning people with such devices never to go near them.
You don't meet many bible-thumping Baptists, do you? They do some serious hellfire and damnation in their sermons, especially when talking about the Catholics.
You haven't read many mid-term papers by students studying Perl, have you?
There are far more secretive ways to track things: control over the international routers allows black-holing domains and sites, and rerouting or echoing their traffic to permit complete analysis of all traffic from them. Take a look at tools listed at www.sandstorm.com to see what is available, commercially, for such traffic analysis both recorded for later probing and real-time analysis with control of the routers and the kind of warrant-free tapping of internet backbones as has already been discovered.
No, control over the core DNS tables is to allow fast cutting off of any sites you want to block. It's a censorship tool, not a monitoring tool.
Ahh yes. Then there's the Marathon 2 rocket-launch trick: firing a rocket propels the player backwards. Badly handled, this could push you right off into the poison or lava. But there was at least one point in the game where you had to walk over a high wall into a valley where dozens, even hundreds of aliens would appear and waste all your ammo with you, leaving you beaten and bleeding to enter the next level, and the last save point was at least 5 minutes of play before that point.
It was extremely painful to deal with until I worked out how to walk off the edge, trigger the aliens to show up, blow myself backward onto the edge with the rocket, then wait while the aliens started shooting at each other. Then I could hop down and mop up the mess with a much, much smaller bucket, sometimes even just a dishrag instead of the Zamboni previously required.
There's also an amazingly funny video trailer for Team Fortress 2, that involves soldiers bouncing and spinning across the sky by rocket launching themselves, with a water ballet soundtrack. Watching them land gracefully in a neat row and the last one breaking his leg with an audible "snap" is amazingly funny to watch.
Unfortunately, the owners of the intellectual property have used their market dominance to hinder any potential competition. The "dumping" in competitor's markets has been especially destructive. I'm afraid we'll have to wait for the owners' business plan to destroy them utterly before any other effective competition can occur.
This is the default in most RedHat systems. Many users learn to automatically type "rm -rf", and the protection evaporates pretty quickly.
Oh, yes. Even with licensed software, managing the licenses is amazingly painful with all the different approaches to licenses.
Other such bugs are amazingly painful internal trouble ticket or purchasing systems: they're so painful they force employees to waste their own money on small purchases and leave purchasing departments either unbothered by requests, or able to steer requests to their "preferred" vendors.
And systems where security is so poor that people simply leave all files accessible to each other do make it easy to sniff other people's email for relevant documents when they're not in the office.
Nahh. There won't be the gravity to hold it down at her feet: it'll be free to return to her heart, minus friction losses.
It's still a long way to run on the treadmill, though.
Run your Windows in a virtual environment, behind a firewall in the virtual server. Then use the updated OS image as your canonical installation image.
This would work better if it were easier to register the license keys remotely, but it's workable.
No, BSD is still quite active, including the one inside Apple these days. But the testers were probably unable to install OpenBSD on any hardware less than 8 years old: that OS does *not* have a sane installer or compatibility with a lot of more modern components.
Go ahead, get an off-the-shelf USB wheel-mouse working on OpenBSD without spending at least 2 days hand-building kernels and other components.
For the cost of wasting 5 hours on the phonen of one of my technical peers, I can often contact the *author* of the open source tool and pay them for one hour of support time, at a substantial savings to my personal or my employer's bottom line.
Next time, start the clock and measuer how long it takes. From harsh, harsh experience, the forum is faster. The last 3 MS support calls I made took at least 3 levels of escalation to get to the engineers I needed to talk to. It's even worse when I'm calling to report a bug and a workaround: I don't get credit for the fix, the fix if ever eventually provided is not properly described in the "update" list, and the bug report often vanishes into the void.
Google and public Wikies are often far, far, far faster and more detailed than the Microsoft tech support, especially for the more obscure subtleties of hardware and software interactions among products from different vendors.
The policy is known as "embrace and extend": in practice, it's "embrace and extend and break compatibility". The extensions seem to quite deliberately violate the existing standards: this has occurred repeatedly, with Kerberos (which required a serious patch in MIT's oritingal version to inter-operate with Microsoft's bastardized version), with DNS and DHCP (don't get me started on this one, I had to deal with it last week to show how easy it is to steal a Window's machine's hostname if you use Active Directory's built-in DHCP).
It's been tough. It has to scale well, deal with small payments, be reasonably secure, and have enough profitability to get the equipment set up and the salaries paid.
Hmm. If anyone could trust them with money, PirateBay would be in an amusingly MPEG patent-free environment to do this.
You do know that the more serious lawsuits involved the fact that much of NT was written by David Cutler, one of the core authors of VMS, who took his merry gang of software pirates Microsoft hired away from DEC when DEC canned some of David's software projects? There are lots of old articles about it: look up "david cutler", "VMS", and "Windows NT".
It's not the Bugzilla search: it's the bug authors who cannot be convinced to use a consistent format on submitting bugs. "What's wrong with my system" is not a useful title for a bug.
Parallel processing is fine and useful. It is also vastly, vastly, vastly tougher to fully test and support, especially in such a wild and woolly environment as system boot: people have been hand-inserting all sorts of oddnesses in there, and the robustness is a testament to the wisdom of keeping it simple and single-threaded.
It's useful for laptops, where every erg of boot-time energy is essentially wasted. Keep an eye on the One Laptop Per Child project for related work. They're actually using a Linux based BIOS.
It's also useful for micro-Linux implementations, for cell phones, routers, firewalls, etc.
It's also useful for testing environments and co-location uses where the manpower wasted connecting up and doing boot time operations also costs a lot of work and money.
And it's fun to show off while tools like Vista are booting in layer after layer of memory gobbling and unwanted "optimizers" and "pre-indexers" that mean the pretty login screen shows up, but you can't do any real work for another few minutes until everything is completely pre-loaded.
That would explain why Hillary Clinton wears so much makeup.
This is confusing. Russia right now is a big *source* of spammer operations that infest Windows machines and lease time on them to spamming companies. They have sharp programmers and no enforcement of computer security abuses to speak of, and an active criminal underground to launder the money through.
Killing them doesn't seem to be all that helpful so far.
Righteousness is good. But there's something about righteousness automatically winning out in the long run that doesn't work out well. The 9/11 bombers thought they were being "righteous" and destroying the enemies of Allah and of Islam. And the political effects of that have already shaped nations.