As I understand it, the problem isn't the pump, it's the glucose sensor. If there was a reliable sensor, the technology has been around for decades to implant a mechanism, rechargeable with a a magnetic charger and programmer, and refillable with a syringe. But the reliable sensors all take chemicals, and all destroy blood to make their test.
He didn't do so. He just pointed out that blind obedience to city ordinances can lead to truly awful behavior, and in some cases should be ignored or even defied.
It wouldn't work. As near as I can tell from the literature pointed out by my Type 1 co-worker, the immune problemm that destroyed your insulin producing cells is probably still active, and would also destroy the self-grown transplant tissue. My co-worker also pointed out some fascinating immuno-suppressive therapies that seem to control this problem, and allow diabetic animals to regenerate their own insulin producing cells, which seems like having this printer without bothering to buy the printer.
The "new security model" bought very little actual security. Most users still run as "Administrator". Most still automatically click "yes", and most still are happy to answer questionnaires that give away far too much information and still are willing to send passwords by email, and still use the same password for everything. Kerberos still isn't generally used, and single-sign-on still is mishandled. Not much has changed for genuine security, but DRM has gotten a lot of support, and the API's remain concealed and obsccured. In other words, for practical security, Vista changed little that users really benefited from: there were modest kernel improvements, but the loss of stability was profound. And the new interfaces wasn't enough to be worth the bother.
Now, the jump from Win95 to XP was noticeability. Applications were _far_ more stable, because they switched from a DOS kernel to a far NT kernel, courtesty of David Cutler and his transfer of DEC's intellectual property from VMS. (Check the lawsuit history, especially involving memory management.) XP had far longer uptimes, far better security, and massively better network performance. Vista had far better..... annoying you with stupid questions, all of which users answered "yes". This is not an improvement.
Is it integrated now? Good: that was an amazing waste of a slot on a motherboard for something unlikely to even be set up correctly. Is it still such a pain to configure? Having to reboot your server, just to set up the fallback control system, was amazingly stupid and a compelling reason to recommend the use of a remote KVM.
That's not how it was sold, and not how it was designed. I understand a great deal about software, thank you: and Windows 7 came along 2.5 years later, under massive pressure because companies still refused to use Vista. That's a little hurried for a major OS release, but hardly "soon". And a stack of features that were praised to the heavens for Vista never came about, and remain discarded in Windows 7. (WinFS, for example.)
No, the break in compatibility to get stability was the switch from Win95 (which was DOS based) to Windows XP (which was NT based, and a lot of which was actually VMS pirated by David Cutler and his crew hired away from DEC). XP actually turned out to be a step up. Vista turned out to be a "new vision", most of which people didn't actually want. Windows 7 has a potential market now because it's 6 years from the release of Windows XP: with the need for DirectX 10 for gamers, contemporary drivers for exciting new hardware such as drives with 4K blocks, and that many years of merging the latest MS Office into the operating system, it's not surprising that customers will consider finally upgrading.
It's not the existence that's so appalling: it's the labeling of it as a "license", reather than a tax, which is what it most clearly _is_. Most "licenses" grant you permission to do something, in a public area or a use that would actually _prevent_ others from using the resource. In this case, it's for merely possessing equipment, in your own home. That makes it pretty clearly a property tax, not a "license" by most legal definitions.
"ILO cards" remain expensive, and in many cases quite painful to implement. Even Dell's version of this approach, that awful excuse for a remote network-based console that they called "DRAC" remains an expensive waste of a PCI slot that shouldn't have been allowed out of their engineering group. Do _not_ get me started on those those things.
I recently had to demonstrate just how much more reliable it was for a partner company by walking them through the connection of a serial port, to another of their computers in a hosted configuration, becuase it worked when their very expernsive and highly engineered DRAC setup had never actually been configured properly. (Whoever had recorded the MAC addresses apparently hadn't even recorded the correct number of digits: it was a mess.)
And this is why, when I get a call about all sorts of problems throughout my career, I want to see the code, _and_ the wiring. An otherwise intelligent engineer, stepping outside their experience, will make assumptions that turn out not to apply in fascinating cases that break down under use. The 3-wire setup is common and not unreasonable in a small test setup. But even for a household DB-9 setup, you should use an adapter that connects the flow-control wires on each end together, to prevent a hardware flow control from being sent on one end and no response provided, even if it will be ignored downstream.
This is why it's sometimes useful to leave the caps off the adapters fo RS-232: you can look inside them and remind yourself what is actually going on. you can get a probe in there to measure it, and even if you touch a bare wire, it's less than 15 Volts and shouldn't have enough power to cause problems.
Then refer to the principles, not the mishmosh of badly used constitutional arguments that that commodore64_love cited. The idea that you can open any public service you want, wherever you want, without any local licensing or registration of that service, and worse that you can simply shoot the police who come to shut it down, is simply nonsense.
The nonsense is even worse when the constitutional arguments cited are about a case in England. They have a rather different government: founding your argments in history or law and parallel cases would be far more reasonable. And the _law_ for soup kitchens is that they need to follow local food preparation regulations, for simple safety reasons. There may also be "zoning" laws, preventing you from running a busines out of your home: that can be a lot trickier for small charities.
The UK already has one: they patrol neighborhoods scanning for unlicensed televisions, those on which they haven't paid their "license fee", which anyone else in the world would call a television tax.
First: this law is in the UK, not the US, so your whole string of constitutional references is pretty irrelevant.
Second: I've worked in soup kitchens. If you're handing out good to friends, it's not a big deal. People can reasonably understand the risks. But when you're setting up a soup kitchen, the very scale of it makes it a business, you're running a restaurant and come under various safety regulations. If you don't keep your kitchen clean and the food reasonably fresh, you can kill the people who receive your generosity, you will draw rats (which will endanger those near your soup kitchen), you will overflow local sanitation and garbage services if you don't arrange for enough pickups, and you can spread plague that will kill people city wide. (Look up "Typhoid Mary" for the classic historic case.)
Typhoid Mary, in particular, is relevant. If you run such a soup kitchen and spread plague, _as many open wi-fi access points do by hosting cracking and malware and phishing sites_, you should be shut down. And there are numerous legal grounds under which to do so.
Oh, dear. This is why statistics so often lie. The question of _legalizing_ marijuana is often conflated with that of _decriminalizing_ it. Decriminalizing it would provide the first, third, and fourth benefits at least somewhat, and consistently gathers far more than 50% support in polls.
That's a very good question, the sort of thing that makes electrical engineering instructors excited and wipe off a chalkboard to give explanations. Complex electrical components have various "grounds", and many are certainly not necessarily "common". Even for circuitry that talks to each other, the "signal ground" may be electrically isolated from the power supply grounds and the case grounds and should be handled separately. If you don't do this, you wind up with mistakes of the sort I've seen, where someone wires case ground for the serial port to the signal grounds, someone accidentally miswires a power supply, and you have "neutral" of one device wired directly to the serial port grounds of the other, and trying to carry a few amps of current down a really _surprised_ serial cable.
For serial ports in particular, the "signal ground" of one port may be quite different from that of the network port, other serial ports, USB, or the memory circuitry or CPU. And that difference can cause mistakes: RS-232 is particularly robust against such mistakes, but it's not immune, especially over long distances.
Unfortunately, every untrained technician and their ill-trained supervisor gets these wrong. The flow control lines are not there for laughs: mis-handled, they lead to many unfortunate adventures, at the worst moments. I've had to deal with the errors when someone thought the way you did, failed to connect the flow control to anything, and wound up with jammed serial lines.
The standard is published many places, such as http://www.zytrax.com/tech/layer_1/cables/tech_rs232.htm#db25. Even your "three wire description" has left something important out, that I've seen mis-wired: the third wire is _signal ground_, not "common ground". "Common ground" is when we share something interesting to talk about: it's an unfortunate choice of words for wiring.
> So, what happens when someone complained about Vista and insisted on XP?
No, what happened when Microsoft came out with Vista and _no one wanted it_? The OEM could continue with their familiar XP operating system and driver installation, and not waste money and resources on engineering solutions that few customers wanted. Unfortunately, Microsoft proceeded to manipulate the OEM's in ways that require Microsoft power, ways for which Microsoft has been convicted before. The _threatened_ OEM's, by raising the prices of Vista licenses for those few customers that wanted them, unless OEM's agreed to switch entirely to Vista. Numerous customers did not _want_ Vista, but were coerced by new hardware being available only with Vista pre-installed. And that effectively raises the price of XP equipped machines quite a lot, because for an individual customer doing all that driver and patch upgrading is hideously expensive.
Vendors were willing to continue with XP, to support customers who wanted it. Microsoft acted against those vendors: and if you don't believe a big vendor can do a hardsell, try attending a meeting with a big vendor, and a few of the little after-hours meetings they try to arrange with your management. It's enlightening.
I can think of such opensource tools, though not necessarily GPL. SSH, which forked from open source to closed source and still has an open source fork available, is available in a more featureful closed source version, especially including Kerberos support ofr Windows clients.
No, no, that's not porn. It's the Charlie's Angels theme: where there were plenty of young men who committed self-abuse to that television introduction, the show never really crossed the line into real pornography.
Porn music gends to have more of a beat, and less flutes than that particular rendition.
I wouldn't care to bet on that. The Secret Service has a history of being far, far behind the times with both equipment and policy: take a look at their old "Operation Sundevil" raid on Steve Jackson Games, where they believed that a role-play game called "Cyberwar" was a guide to cybercrime. Given their lack of progress in dealing with modern wire fraud, which is one of their main jobs, there is no reason to assume they are competent enough to have patched vulnerabilities known for decades.
Given that the prisoners in Guantanamo Bay are not allowed to speak to anyone, and their lawyers are gagged, that charges or trials have only been attempted for a few of them, and that at least 3 of them were tortured to death, it seems that _no one will admit_ what those prisoners are being held for. So it might well be for calling Dick Cheney a Republican: the only ones who can really tell are not able or willing to talk.
The translations of the controls from console to keyboard for various Resident Evil games was awful, especially in recent releases. Many were unplayable unless you used cheats, because you couldn't control character motion well enough in combat scenes.
Excuse me? The chance of stealing it _and not getting caught_ just went up considerably, even if the students weren't previously aware of the anti-hijacking measures.
Unfortunately, as someone who's tried to challenge a tax audit for old expenses, I can tell you that a lot of those records do not keep well. Many poor quality printouts are not likely to last even a few years due to the poor quality of the paper and the ink. This is especially true of receipts, which are on the cheapest printers possible.
True. There have actually been a few _good_ books about video game worlds. The "X-Com: UFO Defense" book by Diane Duane was actually fun to read, both consistent with the gameplay and lending color to the characters. Of course, Diane is also the woman who wrote "Spock's World" and "The Romulan Way", which also preserved the structure of someone else's fictional world but actually explored the people in it. I highly recommend her books to fans of worlds she's written books for.
Slashdot Mirror
As I understand it, the problem isn't the pump, it's the glucose sensor. If there was a reliable sensor, the technology has been around for decades to implant a mechanism, rechargeable with a a magnetic charger and programmer, and refillable with a syringe. But the reliable sensors all take chemicals, and all destroy blood to make their test.
He didn't do so. He just pointed out that blind obedience to city ordinances can lead to truly awful behavior, and in some cases should be ignored or even defied.
It wouldn't work. As near as I can tell from the literature pointed out by my Type 1 co-worker, the immune problemm that destroyed your insulin producing cells is probably still active, and would also destroy the self-grown transplant tissue. My co-worker also pointed out some fascinating immuno-suppressive therapies that seem to control this problem, and allow diabetic animals to regenerate their own insulin producing cells, which seems like having this printer without bothering to buy the printer.
It's described at http://www.faustmanlab.org/, and it's quite fascinating work.
The "new security model" bought very little actual security. Most users still run as "Administrator". Most still automatically click "yes", and most still are happy to answer questionnaires that give away far too much information and still are willing to send passwords by email, and still use the same password for everything. Kerberos still isn't generally used, and single-sign-on still is mishandled. Not much has changed for genuine security, but DRM has gotten a lot of support, and the API's remain concealed and obsccured. In other words, for practical security, Vista changed little that users really benefited from: there were modest kernel improvements, but the loss of stability was profound. And the new interfaces wasn't enough to be worth the bother.
Now, the jump from Win95 to XP was noticeability. Applications were _far_ more stable, because they switched from a DOS kernel to a far NT kernel, courtesty of David Cutler and his transfer of DEC's intellectual property from VMS. (Check the lawsuit history, especially involving memory management.) XP had far longer uptimes, far better security, and massively better network performance. Vista had far better..... annoying you with stupid questions, all of which users answered "yes". This is not an improvement.
Is it integrated now? Good: that was an amazing waste of a slot on a motherboard for something unlikely to even be set up correctly. Is it still such a pain to configure? Having to reboot your server, just to set up the fallback control system, was amazingly stupid and a compelling reason to recommend the use of a remote KVM.
That's not how it was sold, and not how it was designed. I understand a great deal about software, thank you: and Windows 7 came along 2.5 years later, under massive pressure because companies still refused to use Vista. That's a little hurried for a major OS release, but hardly "soon". And a stack of features that were praised to the heavens for Vista never came about, and remain discarded in Windows 7. (WinFS, for example.)
No, the break in compatibility to get stability was the switch from Win95 (which was DOS based) to Windows XP (which was NT based, and a lot of which was actually VMS pirated by David Cutler and his crew hired away from DEC). XP actually turned out to be a step up. Vista turned out to be a "new vision", most of which people didn't actually want. Windows 7 has a potential market now because it's 6 years from the release of Windows XP: with the need for DirectX 10 for gamers, contemporary drivers for exciting new hardware such as drives with 4K blocks, and that many years of merging the latest MS Office into the operating system, it's not surprising that customers will consider finally upgrading.
It's not the existence that's so appalling: it's the labeling of it as a "license", reather than a tax, which is what it most clearly _is_. Most "licenses" grant you permission to do something, in a public area or a use that would actually _prevent_ others from using the resource. In this case, it's for merely possessing equipment, in your own home. That makes it pretty clearly a property tax, not a "license" by most legal definitions.
"ILO cards" remain expensive, and in many cases quite painful to implement. Even Dell's version of this approach, that awful excuse for a remote network-based console that they called "DRAC" remains an expensive waste of a PCI slot that shouldn't have been allowed out of their engineering group. Do _not_ get me started on those those things.
I recently had to demonstrate just how much more reliable it was for a partner company by walking them through the connection of a serial port, to another of their computers in a hosted configuration, becuase it worked when their very expernsive and highly engineered DRAC setup had never actually been configured properly. (Whoever had recorded the MAC addresses apparently hadn't even recorded the correct number of digits: it was a mess.)
And this is why, when I get a call about all sorts of problems throughout my career, I want to see the code, _and_ the wiring. An otherwise intelligent engineer, stepping outside their experience, will make assumptions that turn out not to apply in fascinating cases that break down under use. The 3-wire setup is common and not unreasonable in a small test setup. But even for a household DB-9 setup, you should use an adapter that connects the flow-control wires on each end together, to prevent a hardware flow control from being sent on one end and no response provided, even if it will be ignored downstream.
This is why it's sometimes useful to leave the caps off the adapters fo RS-232: you can look inside them and remind yourself what is actually going on. you can get a probe in there to measure it, and even if you touch a bare wire, it's less than 15 Volts and shouldn't have enough power to cause problems.
Then refer to the principles, not the mishmosh of badly used constitutional arguments that that commodore64_love cited. The idea that you can open any public service you want, wherever you want, without any local licensing or registration of that service, and worse that you can simply shoot the police who come to shut it down, is simply nonsense.
The nonsense is even worse when the constitutional arguments cited are about a case in England. They have a rather different government: founding your argments in history or law and parallel cases would be far more reasonable. And the _law_ for soup kitchens is that they need to follow local food preparation regulations, for simple safety reasons. There may also be "zoning" laws, preventing you from running a busines out of your home: that can be a lot trickier for small charities.
The UK already has one: they patrol neighborhoods scanning for unlicensed televisions, those on which they haven't paid their "license fee", which anyone else in the world would call a television tax.
First: this law is in the UK, not the US, so your whole string of constitutional references is pretty irrelevant.
Second: I've worked in soup kitchens. If you're handing out good to friends, it's not a big deal. People can reasonably understand the risks. But when you're setting up a soup kitchen, the very scale of it makes it a business, you're running a restaurant and come under various safety regulations. If you don't keep your kitchen clean and the food reasonably fresh, you can kill the people who receive your generosity, you will draw rats (which will endanger those near your soup kitchen), you will overflow local sanitation and garbage services if you don't arrange for enough pickups, and you can spread plague that will kill people city wide. (Look up "Typhoid Mary" for the classic historic case.)
Typhoid Mary, in particular, is relevant. If you run such a soup kitchen and spread plague, _as many open wi-fi access points do by hosting cracking and malware and phishing sites_, you should be shut down. And there are numerous legal grounds under which to do so.
Oh, dear. This is why statistics so often lie. The question of _legalizing_ marijuana is often conflated with that of _decriminalizing_ it. Decriminalizing it would provide the first, third, and fourth benefits at least somewhat, and consistently gathers far more than 50% support in polls.
That's a very good question, the sort of thing that makes electrical engineering instructors excited and wipe off a chalkboard to give explanations. Complex electrical components have various "grounds", and many are certainly not necessarily "common". Even for circuitry that talks to each other, the "signal ground" may be electrically isolated from the power supply grounds and the case grounds and should be handled separately. If you don't do this, you wind up with mistakes of the sort I've seen, where someone wires case ground for the serial port to the signal grounds, someone accidentally miswires a power supply, and you have "neutral" of one device wired directly to the serial port grounds of the other, and trying to carry a few amps of current down a really _surprised_ serial cable.
For serial ports in particular, the "signal ground" of one port may be quite different from that of the network port, other serial ports, USB, or the memory circuitry or CPU. And that difference can cause mistakes: RS-232 is particularly robust against such mistakes, but it's not immune, especially over long distances.
Unfortunately, every untrained technician and their ill-trained supervisor gets these wrong. The flow control lines are not there for laughs: mis-handled, they lead to many unfortunate adventures, at the worst moments. I've had to deal with the errors when someone thought the way you did, failed to connect the flow control to anything, and wound up with jammed serial lines.
The standard is published many places, such as http://www.zytrax.com/tech/layer_1/cables/tech_rs232.htm#db25. Even your "three wire description" has left something important out, that I've seen mis-wired: the third wire is _signal ground_, not "common ground". "Common ground" is when we share something interesting to talk about: it's an unfortunate choice of words for wiring.
You wrote:
> So, what happens when someone complained about Vista and insisted on XP?
No, what happened when Microsoft came out with Vista and _no one wanted it_? The OEM could continue with their familiar XP operating system and driver installation, and not waste money and resources on engineering solutions that few customers wanted. Unfortunately, Microsoft proceeded to manipulate the OEM's in ways that require Microsoft power, ways for which Microsoft has been convicted before. The _threatened_ OEM's, by raising the prices of Vista licenses for those few customers that wanted them, unless OEM's agreed to switch entirely to Vista. Numerous customers did not _want_ Vista, but were coerced by new hardware being available only with Vista pre-installed. And that effectively raises the price of XP equipped machines quite a lot, because for an individual customer doing all that driver and patch upgrading is hideously expensive.
Vendors were willing to continue with XP, to support customers who wanted it. Microsoft acted against those vendors: and if you don't believe a big vendor can do a hardsell, try attending a meeting with a big vendor, and a few of the little after-hours meetings they try to arrange with your management. It's enlightening.
I can think of such opensource tools, though not necessarily GPL. SSH, which forked from open source to closed source and still has an open source fork available, is available in a more featureful closed source version, especially including Kerberos support ofr Windows clients.
No, no, that's not porn. It's the Charlie's Angels theme: where there were plenty of young men who committed self-abuse to that television introduction, the show never really crossed the line into real pornography.
Porn music gends to have more of a beat, and less flutes than that particular rendition.
I wouldn't care to bet on that. The Secret Service has a history of being far, far behind the times with both equipment and policy: take a look at their old "Operation Sundevil" raid on Steve Jackson Games, where they believed that a role-play game called "Cyberwar" was a guide to cybercrime. Given their lack of progress in dealing with modern wire fraud, which is one of their main jobs, there is no reason to assume they are competent enough to have patched vulnerabilities known for decades.
Given that the prisoners in Guantanamo Bay are not allowed to speak to anyone, and their lawyers are gagged, that charges or trials have only been attempted for a few of them, and that at least 3 of them were tortured to death, it seems that _no one will admit_ what those prisoners are being held for. So it might well be for calling Dick Cheney a Republican: the only ones who can really tell are not able or willing to talk.
The translations of the controls from console to keyboard for various Resident Evil games was awful, especially in recent releases. Many were unplayable unless you used cheats, because you couldn't control character motion well enough in combat scenes.
Excuse me? The chance of stealing it _and not getting caught_ just went up considerably, even if the students weren't previously aware of the anti-hijacking measures.
Wow. The Linux emulaors are available over at the Penguin Liberation Front, if you can ever extract the data from those cartridges.
Unfortunately, as someone who's tried to challenge a tax audit for old expenses, I can tell you that a lot of those records do not keep well. Many poor quality printouts are not likely to last even a few years due to the poor quality of the paper and the ink. This is especially true of receipts, which are on the cheapest printers possible.
True. There have actually been a few _good_ books about video game worlds. The "X-Com: UFO Defense" book by Diane Duane was actually fun to read, both consistent with the gameplay and lending color to the characters. Of course, Diane is also the woman who wrote "Spock's World" and "The Romulan Way", which also preserved the structure of someone else's fictional world but actually explored the people in it. I highly recommend her books to fans of worlds she's written books for.