Nice justification for that asshole Assange. Lying and exaggerating and raping, and avoiding justice - that's been his life story.
But keep rationalizing out what he's done. He's a murdering, meritless troll, nothing more. He's been responsible for more people being killed than anyone reading this, and lives being destroyed through his thoughtless, purposeful divulging of Manning's traffic. Blood all over his disgusting hands.
May he rot in the Ecuadorian embassy in London for the rest of his life.
I'm sure the potential knock on the door in the middle of the night had something to do with the MacGyver attitude. That said, the juice isn't worth the squeeze.
I have similar memories of F-15 Strike Eagle II which was 320x200 in 16 or 256 colors (if you had VGA). Looked great back then - today we'd laugh at it and call it an amorphous blob. Flying those missions against the Soviets or Iran was a load of fun.
I had a DX-66 with the same switch. I just left it on at all times. I honestly rarely used the switch, even on my XT compatible. Most of the uses by 1987 (which was when I got it) revolved around BASICA, of all things, and I didn't have that, since it was a clone and had GW-BASIC which had a subset of the timing issues of BASICA.
The original 486DX was released in 1989 and ran at 20mhz. It included a FPU, previously an add-on coprocessor on x86 chips.
Then, the 486SX was released, which disabled the FPU and was offered at speeds as slow as 16mhz.
The 486DX topped out at 50mhz, but then on-chip clock doubling was offered as the 486DX2, raising speeds up to 66mhz. Then clock tripling, finishing up at 100mhz with the 486DX4.
Earlier boxes had turbo buttons because they could shift back into a nominally PC/PC/XT compatible 4.77mhz (in the case of 8088/8086 boxes) or PC/AT compatible 6 or 8mhz (in the case of 286/386 boxes). It actually had a good reason - many early games were highly dependent on the system's clock speed.
He's not wrong. Sorry, i'm not a leftist ideological hack, probably just the opposite, and I agree with, in essence, everything said by the GP poster. We did militarize our police forces for bad reasons. We do overreact to crimes. We should strip out all of the military hardware from "first responders" aka law enforcement. There's no need for it and it makes our existence more coarse.
Getting rid of some stupid drug laws and over the top criminal enforcement would also help.
This is kind of funny because I remember people using funky 3270 and 5250 boards with DOS drivers in their OS/2 2.0 workstations. I mean, i'm sure you're right, but i'm also sure that most shops didn't implement this correctly.
By the time of Warp, the battle was over. OS/2 2.0 was IBM's only opportunity - a window between 3.1 and the release of Win 95. They got decent market penetration and even switched a few corporate shops over to OS/2. 2.0 had no TCP/IP stack at the time. I believe it came along with Warp 3.0 Connect, which was released in May 1995, too late to make a difference in the adoption of 3.1 and 95.
I'll grant you that the OEM deals helped, but before even 95 came out, people wanted Office. There were WordPerfect holdouts and people who liked Quattro Pro. But it was fast becoming a Microsoft world and none of the competitors stood a chance against Office. IBM created a suite but it was too little, too late.
The OEM deals wouldn't have worked if people purchasing in the commercial space didn't want Windows. It made things easier than dealing with the licensing for different applications from different vendors, and buying Microsoft appeared cheaper at the time than being on an upgrade treadmill with multiple companies. "You mean I can get rid of Foxpro, Wordperfect and even Novell? Sign me up." This would have happened regardless of the OEM bundling. Reducing the friction of licensing is primarily what won that world for Microsoft.
What the OEM deals primarily did was to make sure home users ended up with Windows, which gave them the gaming market for a while.
Every successful OS over the microcomputer age has had a killer app, something that it did that other competing machines did not. Something to sell it. Apple IIs had VisiCalc. The IBM PC had Lotus 1-2-3. Macintoshes had Pagemaker and later Quark. Windows had the Office suite, ultimately. OS/2 had nothing. Sure, it was great at running other OS' apps - it was a great DOS emulator and did Windows 3.1 pretty excellently, but it had no killer app of its own. This was mainly because IBM didn't consider it important to get people to write apps for its OS.
You can call that a lack of marketing and still be right. It's just not "marketing in general" but "marketing to developers".
A $9.99 upgrade plan from any prior OS would have been enough to avoid that. Instead, they charged $49.99, if my memory serves. But IBM's failure with OS/2 had to do with application development, not price.
He was born in Canada. But, his mother was a US citizen and only there due to her husband's work, and I think as a result he does qualify as native born. McCain was born in the Canal Zone and we've had a few other situations like that. I think that even if Obama had been born in Kenya, as some aver, he would probably have been adjudged as native born due to his mother similarly being a US citizen.
I feel like an airship would be a lot more effective and safe for this purpose. Why doesn't anyone talk about that? Why always fixed wing drone technology?
What if I don't want an unmanned fixed wing aircraft loitering over my head for months, just waiting to have a catastrophic mechanical failure and kill me randomly?
There are nuclear equivalents to most conventional weapons - Tomahawk missiles had a nuclear payload designed for them, for instance. Bolting on a nuclear warhead onto most weapons isn't impossible. Of course, the issue is - who is going to use them and risk escalation?
The answer, in general, is no one. There is a line there, and once crossed, it opens up the use of even half megaton strategic assets. Or a FOBS.
Nice justification for that asshole Assange. Lying and exaggerating and raping, and avoiding justice - that's been his life story.
But keep rationalizing out what he's done. He's a murdering, meritless troll, nothing more. He's been responsible for more people being killed than anyone reading this, and lives being destroyed through his thoughtless, purposeful divulging of Manning's traffic. Blood all over his disgusting hands.
May he rot in the Ecuadorian embassy in London for the rest of his life.
In a country where owning a typewriter was a punishable crime, imagine what concocting your own IT would be like?
People forget so quickly.
I'm reminded of Keynes' warning about "In the long run, we're all dead".
At the cost of doing nothing else.
I'm sure the potential knock on the door in the middle of the night had something to do with the MacGyver attitude. That said, the juice isn't worth the squeeze.
The Soviets are kicking themselves that they didn't think of this.
I have similar memories of F-15 Strike Eagle II which was 320x200 in 16 or 256 colors (if you had VGA). Looked great back then - today we'd laugh at it and call it an amorphous blob. Flying those missions against the Soviets or Iran was a load of fun.
I had a DX-66 with the same switch. I just left it on at all times. I honestly rarely used the switch, even on my XT compatible. Most of the uses by 1987 (which was when I got it) revolved around BASICA, of all things, and I didn't have that, since it was a clone and had GW-BASIC which had a subset of the timing issues of BASICA.
Usually, RomeUS comparisons are trite, uninformed and boring. In this case...you actually have a good point.
I'm drawn back to Jefferson's comment about the tree of Liberty needing refreshing with the blood of tyrants and patriots from time to time.
The original 486DX was released in 1989 and ran at 20mhz. It included a FPU, previously an add-on coprocessor on x86 chips.
Then, the 486SX was released, which disabled the FPU and was offered at speeds as slow as 16mhz.
The 486DX topped out at 50mhz, but then on-chip clock doubling was offered as the 486DX2, raising speeds up to 66mhz. Then clock tripling, finishing up at 100mhz with the 486DX4.
Earlier boxes had turbo buttons because they could shift back into a nominally PC/PC/XT compatible 4.77mhz (in the case of 8088/8086 boxes) or PC/AT compatible 6 or 8mhz (in the case of 286/386 boxes). It actually had a good reason - many early games were highly dependent on the system's clock speed.
By your logic, posting a video of prison anal rape of a person who did a swatting would reduce its frequency.
He's not wrong. Sorry, i'm not a leftist ideological hack, probably just the opposite, and I agree with, in essence, everything said by the GP poster. We did militarize our police forces for bad reasons. We do overreact to crimes. We should strip out all of the military hardware from "first responders" aka law enforcement. There's no need for it and it makes our existence more coarse.
Getting rid of some stupid drug laws and over the top criminal enforcement would also help.
Exactly what wasn't going to happen. IBM wasn't going to waste time reimplementing that moving target and there was zero chance MS would license it.
This is kind of funny because I remember people using funky 3270 and 5250 boards with DOS drivers in their OS/2 2.0 workstations. I mean, i'm sure you're right, but i'm also sure that most shops didn't implement this correctly.
By the time of Warp, the battle was over. OS/2 2.0 was IBM's only opportunity - a window between 3.1 and the release of Win 95. They got decent market penetration and even switched a few corporate shops over to OS/2. 2.0 had no TCP/IP stack at the time. I believe it came along with Warp 3.0 Connect, which was released in May 1995, too late to make a difference in the adoption of 3.1 and 95.
I'll grant you that the OEM deals helped, but before even 95 came out, people wanted Office. There were WordPerfect holdouts and people who liked Quattro Pro. But it was fast becoming a Microsoft world and none of the competitors stood a chance against Office. IBM created a suite but it was too little, too late.
The OEM deals wouldn't have worked if people purchasing in the commercial space didn't want Windows. It made things easier than dealing with the licensing for different applications from different vendors, and buying Microsoft appeared cheaper at the time than being on an upgrade treadmill with multiple companies. "You mean I can get rid of Foxpro, Wordperfect and even Novell? Sign me up." This would have happened regardless of the OEM bundling. Reducing the friction of licensing is primarily what won that world for Microsoft.
What the OEM deals primarily did was to make sure home users ended up with Windows, which gave them the gaming market for a while.
Every successful OS over the microcomputer age has had a killer app, something that it did that other competing machines did not. Something to sell it. Apple IIs had VisiCalc. The IBM PC had Lotus 1-2-3. Macintoshes had Pagemaker and later Quark. Windows had the Office suite, ultimately. OS/2 had nothing. Sure, it was great at running other OS' apps - it was a great DOS emulator and did Windows 3.1 pretty excellently, but it had no killer app of its own. This was mainly because IBM didn't consider it important to get people to write apps for its OS.
You can call that a lack of marketing and still be right. It's just not "marketing in general" but "marketing to developers".
A $9.99 upgrade plan from any prior OS would have been enough to avoid that. Instead, they charged $49.99, if my memory serves. But IBM's failure with OS/2 had to do with application development, not price.
He was born in Canada. But, his mother was a US citizen and only there due to her husband's work, and I think as a result he does qualify as native born. McCain was born in the Canal Zone and we've had a few other situations like that. I think that even if Obama had been born in Kenya, as some aver, he would probably have been adjudged as native born due to his mother similarly being a US citizen.
Or:
3) Current leadership is incompetent and lacks the will to do something about it.
I vote 3.
The turtle lady was wrong.
I feel like an airship would be a lot more effective and safe for this purpose. Why doesn't anyone talk about that? Why always fixed wing drone technology?
What if I don't want an unmanned fixed wing aircraft loitering over my head for months, just waiting to have a catastrophic mechanical failure and kill me randomly?
Umm...an overflow flag?
There are nuclear equivalents to most conventional weapons - Tomahawk missiles had a nuclear payload designed for them, for instance. Bolting on a nuclear warhead onto most weapons isn't impossible. Of course, the issue is - who is going to use them and risk escalation?
The answer, in general, is no one. There is a line there, and once crossed, it opens up the use of even half megaton strategic assets. Or a FOBS.