Microsoft was sued today for "price fixing". By bundling products such as "Notepad" and "Solitare", Wallace claims the move is designed to drive software vendors out of business; and O'Gara parrots the proprietary vendors "OS-Bundled Applications kill buisness" mantra.
Experts expect the result will be the complete removal of all "application layer" software from the Windows where 3rd party competition exists or used to exist, as well as any "late additions" to the OS that are or used to be provided by 3rd parties (such as network support, etc).
This was settled long ago; Wallace and O'Gara will lose.
Yep, but there's just one problem with an all-in-one device - namely, it's an all-in-one device.
I want a specific telephony feature set. I do not want others.
I want a specific camera. The one bundled on my specific phone will be a joke.
I want a specific media player, and I want it to do exactly specific things.
I want a specific feature set on my PDA. In fact, I don't want a PDA - I want a small PC.
I want specific interfaces on that PDA.
I want specific software on my PDA.
I want a useful display on my PDA.
Assuming that some day, someone will actually produce an all-in-one cellphone that'll let me pick my choice of Wifi chipset, cell provider, software, and have a camera that's viable, and have a provider who doesn't pull a Verizon and lock-out/gimp half of the functionality... there's still the very big problem of it being an all-in-one device.
Things break, and other things become outmoded.
In the old days, they made combo-PCMCIA cards that were both modems and NICs. They were wonderful - instead of buying a $50 modem card, and a $50 NIC, you'd now spend $90 on a combo. What people forget is that the connectors break (X-Jack, anyone?); and now, instead of having a dead $50 card, you've now got a dead $90 card. Likewise, after the shift from 14.4k to 28.8, all of the old 14.4 portions of the cards became useless. The NICs were still fine, however - but they still go into the trash. Then, they came out with 33.6 - so, another batch of perfectly good NICs get tossed, since they're physically on the same cards as the old modems. It didn't take a rocket scientist to figure out that combo-cards were a very stupid idea.
With all the features being homed on a single device, they are all (in effect) dependant on each other. Lose one (or have one become non-useful), and the entire device must be replaced. Because of this, no long-term buy-in can happen; the device will be relegated to short term trivial usage, and treated as expendable.
I somehow don't see the market suddenly deciding to follow this path, especially when it concerns something as scummy as a cell-phone provider. At least, not following it in a serious way, at least. There will always be "Tony the IROC guy" in the McDonald's parking lot on Friday night - but that's a trivial "Look at me" use, not a wide market buy-in.
The the taking of a paper image and creating a machine displayable format doesn't constitute translation, I'm not sure what does...
However, this was a scan, which is in effect a photo. Q.v. law on photos of "public works" to find how this should play out. As far as I can tell, copyright may very well apply in this context, even without the translation issue.
In the beginning, Network software cost money, and Windows didn't do it. No big deal, products like Novell, Banyon, and 3Comm had a market.
Then, some versions of Windows did some type of networking. But it didn't do TCP/IP. Other companies had a market, and it was a good one.
Then, Microsoft added networking with TCP/IP, and gave it away for free. A natural progression, with great benefits - but a bunch of things suddenly weren't viable anymore. Benefit to the market? Easy networking... Netware et al finally died the horrible death that it deserved, and users were now actually able to perform such *complex tasks* as killing a print job without paying $16k for a Novell course. Downside? No competition, and that industry was effectively dead - no more innovation unless it comes from Redmond.
In the case of Media player, such a development would have big impact - we're on the edge of the DRM threshold, and a player with full marketshare (as the MS Network stack achieved) will dictate the solution to distributers, producers, and the public... instead of letting a solution evolve by market forces, if I'm making any sense.
... that when confronted with a highly skilled enemy who's ghouls and spooks rivaled our own during the peak of the cold war... we didn't really have this issue.
So, this means you......upgrade the firmware in your microwave every year, or buy a new microwave each year...upgrade the firmware in your wristwatch every year, or buy a new wristwatch each year...upgrade the firmware in your alarmclock every year, or buy a new alarmclock each year...upgrade the firmware in your network switches every year, or buy completely new network switches each year...upgrade the mainboard controller in the HVAC for your house, or buy a completely new HVAC system for your house each year...upgrade the firmware in your car radio each year, or buy a new car radio...upgrade the firmware in your car each year, or buy a new car...upgrade the firmware in your coffee maker each year, or buy a new coffee maker...upgrade the firmware in your "digital thermometer" each year, or buy a new "digital thermometer"...upgrade the firmware on your NICs each year, or buy new NICs each year...replace all of your hard drives every 3 weeks...replace your RAM every 4 months...replace your cell phone every week
All of these things become obsolete, with newer things able to do the exact same job "better" and "cheaper"... so by your argument, you MUST toss the old immediately and replace it even it if works just fine.
As for your other assertion, > The computer, though its basic internal processor memory is all binary numbers, does NOT work in binary. You must be privvy to some new type of "latch" and "flip flop" that the rest of the planet is unaware of. Or, you don't know WTF you're talking about.
Heh, I know the ones of which you speak:) Had one to play with for a weekend from a Cable Supervisor with AT&T, a very nice unit used for finding current leakage in the old transcon cables (and even today, bad patches in the jack bays). Although, I have to say - even the $20k units do a fair job of keeping up with it. You can still see your footprints, tiretracks, etc, but because you can't manually specify the notch-width, small temp variations can get lost... meaning you must manage the hottest and coldest region in view if you wish to see subtle gradients.
But, they do work well - you can get anywhere from a quarter to half a degree resolution out of 'em, easily (unless the floor is at 200 degrees and the ceiling is above 2000... but then half a degree doesn't matter, and getting your ass out of there does.) Still, you get about 256 shades to play with from coldest to hottest, so if you manage what's in view, you can get fairly decent results.
"Abuse" of the patriot act would mean to deviate from what it allows, or use it in a way that is not appropriate. Even if an evaluator has full access to all actions taken under it - finding "no abuse" simply means that all actions taken were consistent with the Act. In no way, shape, or form does this mean that "abuse" didn't take place relative to preexisting law. If the Act allows for murder, for example, anyone who murders under the premise of the Act is *not* abusing it. They may well be abusing other law - but that's far outside the scope of the evaluation, isn't it.
So, secrets have little to do with this. The Act permits egregious behavior; thus far, all egregious actions taken appear to be allowed by that act, and no "abuse" has occurred.
Nah, you don't need to spend that much. You can bottom-feed off the low end for about $13 grand for a fixed-notch greyscale bolometer type. Better ones will run up to 20 grand, and offer a full floating, variable width notch with false color representation.
Granted, these are all intended for structural firefighting, so they aren't cheap. But they *are* intended to be dropped, kicked, and roasted. Obviously, you'll trade weight for battery life and heat shielding - the Draegers have full Ni cladding and can survive long exposure, but they weigh a lot. The Scotts are much lighter, but don't get them above 600 degrees...
I'm proposing that we start a brand new paradigm -.ini-file based databases. If we can make a database revolving around XML, we can use those exact same arguments to make one that revolves around.ini files. And, the.ini file approach will be more extensible and robust, since it has strong legacy support.
Well, you really need to have a TCP/IP based File I/O for any performance with an XML database. Although technically, you would probably get better gains by switching to an HTML database. The HTML database would be better, anyway, because it'll run in any web browser, and it doesn't exactly care what filesystem is in use. That, and all these "data integrity" whiners can then use any CSS validator to check the validity of the data. That way, your HTML Programmers can write on whatever platform they wish, enabling a new paradigm for a pan-dimensional database structure to coexist and re-leverage new legacies before they are implemented, in a cost-efficient and transcendentally transparent manner.
I found that Dilbert, btw! It was an E-Mail based database! Now if you'll please excuse me, I'll be over here, ducking under a table.
For an XML database to really shine, it needs to be integrated with with a TCP/IP filesystem. Once the physical data is stored using TCP/IP (as opposed to FAT or NTFS), the XML database really begins to take off because the data is already in a network format.
From the management side, it further enables the 10,000 monkey technique of writing code. Quite literally, it lowers the requires skillset for production... ergo reduces the "Fast, Cheap, Correct... pick Two" paradox.
From the coder's side, there's a small group-think issue... but actual reasons will depend on the individual. VB weenies will like it because they can pretend to be competent. More talented coders will tolerate it because the crap developed by the VB crowd can be better managed / mitigated. Those in the middle will like it because it has better screen-sav^H^H^H colors.
From the Microsoft side,.NET is a further push for lock-in via the Application Barrier. By enabling the 10k Monkey technique, it causes software vendors to be dependant on the MS platform because the better "fast/cheap/correct" ratio allows for better pricing or margins. Likewise, this will steer the enterprise toward these vendors. And Since the enterprise is dependant on the vendor... well, the enterprise now requires MS for a cost-effective development model, and the lock-in (application barrier) is complete.
They were BOUGHT by those companies in the EXACT SAME WAY that a terrestrial radio or TV station BOUGHT their frequencies. I ought to know - I've bought a few.
Airwaves are airwaves - the law does not concede "ownership" of them... only exclusivity in transmit rights. Big difference.
Slashdot Mirror
Oh, c'mon. This is the U.S. for chrissakes, and G.W. is president. If your computer gets invaded from some other country...
... at which point convection currents will kick in. So hopefully, it's a null issue. Hopefully.
Microsoft was sued today for "price fixing". By bundling products such as "Notepad" and "Solitare", Wallace claims the move is designed to drive software vendors out of business; and O'Gara parrots the proprietary vendors "OS-Bundled Applications kill buisness" mantra.
Experts expect the result will be the complete removal of all "application layer" software from the Windows where 3rd party competition exists or used to exist, as well as any "late additions" to the OS that are or used to be provided by 3rd parties (such as network support, etc).
This was settled long ago; Wallace and O'Gara will lose.
Silly, you forgot Rule #3 when dealing with Microsoft - *avoid even numbered service packs*.
Yeah, but the licensing fees will kill you.
"Damn, I was just getting ready to invade it!"
Yep, but there's just one problem with an all-in-one device - namely, it's an all-in-one device.
I want a specific telephony feature set. I do not want others.
I want a specific camera. The one bundled on my specific phone will be a joke.
I want a specific media player, and I want it to do exactly specific things.
I want a specific feature set on my PDA. In fact, I don't want a PDA - I want a small PC.
I want specific interfaces on that PDA.
I want specific software on my PDA.
I want a useful display on my PDA.
Assuming that some day, someone will actually produce an all-in-one cellphone that'll let me pick my choice of Wifi chipset, cell provider, software, and have a camera that's viable, and have a provider who doesn't pull a Verizon and lock-out/gimp half of the functionality... there's still the very big problem of it being an all-in-one device.
Things break, and other things become outmoded.
In the old days, they made combo-PCMCIA cards that were both modems and NICs. They were wonderful - instead of buying a $50 modem card, and a $50 NIC, you'd now spend $90 on a combo. What people forget is that the connectors break (X-Jack, anyone?); and now, instead of having a dead $50 card, you've now got a dead $90 card. Likewise, after the shift from 14.4k to 28.8, all of the old 14.4 portions of the cards became useless. The NICs were still fine, however - but they still go into the trash. Then, they came out with 33.6 - so, another batch of perfectly good NICs get tossed, since they're physically on the same cards as the old modems. It didn't take a rocket scientist to figure out that combo-cards were a very stupid idea.
With all the features being homed on a single device, they are all (in effect) dependant on each other. Lose one (or have one become non-useful), and the entire device must be replaced. Because of this, no long-term buy-in can happen; the device will be relegated to short term trivial usage, and treated as expendable.
I somehow don't see the market suddenly deciding to follow this path, especially when it concerns something as scummy as a cell-phone provider. At least, not following it in a serious way, at least. There will always be "Tony the IROC guy" in the McDonald's parking lot on Friday night - but that's a trivial "Look at me" use, not a wide market buy-in.
... except that Mac OS 2015 will still be waiting for IE8, which was released back in 2009. :)
The the taking of a paper image and creating a machine displayable format doesn't constitute translation, I'm not sure what does...
However, this was a scan, which is in effect a photo. Q.v. law on photos of "public works" to find how this should play out. As far as I can tell, copyright may very well apply in this context, even without the translation issue.
It's a mixed bag.
In the beginning, Network software cost money, and Windows didn't do it. No big deal, products like Novell, Banyon, and 3Comm had a market.
Then, some versions of Windows did some type of networking. But it didn't do TCP/IP. Other companies had a market, and it was a good one.
Then, Microsoft added networking with TCP/IP, and gave it away for free. A natural progression, with great benefits - but a bunch of things suddenly weren't viable anymore. Benefit to the market? Easy networking... Netware et al finally died the horrible death that it deserved, and users were now actually able to perform such *complex tasks* as killing a print job without paying $16k for a Novell course. Downside? No competition, and that industry was effectively dead - no more innovation unless it comes from Redmond.
In the case of Media player, such a development would have big impact - we're on the edge of the DRM threshold, and a player with full marketshare (as the MS Network stack achieved) will dictate the solution to distributers, producers, and the public... instead of letting a solution evolve by market forces, if I'm making any sense.
... that when confronted with a highly skilled enemy who's ghouls and spooks rivaled our own during the peak of the cold war... we didn't really have this issue.
So, this means you... ...upgrade the firmware in your microwave every year, or buy a new microwave each year ...upgrade the firmware in your wristwatch every year, or buy a new wristwatch each year ...upgrade the firmware in your alarmclock every year, or buy a new alarmclock each year ...upgrade the firmware in your network switches every year, or buy completely new network switches each year ...upgrade the mainboard controller in the HVAC for your house, or buy a completely new HVAC system for your house each year ...upgrade the firmware in your car radio each year, or buy a new car radio ...upgrade the firmware in your car each year, or buy a new car ...upgrade the firmware in your coffee maker each year, or buy a new coffee maker ...upgrade the firmware in your "digital thermometer" each year, or buy a new "digital thermometer" ...upgrade the firmware on your NICs each year, or buy new NICs each year ...replace all of your hard drives every 3 weeks ...replace your RAM every 4 months ...replace your cell phone every week
All of these things become obsolete, with newer things able to do the exact same job "better" and "cheaper"... so by your argument, you MUST toss the old immediately and replace it even it if works just fine.
As for your other assertion,
> The computer, though its basic internal processor memory is all binary numbers, does NOT work in binary.
You must be privvy to some new type of "latch" and "flip flop" that the rest of the planet is unaware of. Or, you don't know WTF you're talking about.
You need to OWN the site that was searched. This is no different than keyword bombing tricks of old; it is merely a bait-and-switch.
Not news.
Heh, I know the ones of which you speak :) Had one to play with for a weekend from a Cable Supervisor with AT&T, a very nice unit used for finding current leakage in the old transcon cables (and even today, bad patches in the jack bays). Although, I have to say - even the $20k units do a fair job of keeping up with it. You can still see your footprints, tiretracks, etc, but because you can't manually specify the notch-width, small temp variations can get lost... meaning you must manage the hottest and coldest region in view if you wish to see subtle gradients.
But, they do work well - you can get anywhere from a quarter to half a degree resolution out of 'em, easily (unless the floor is at 200 degrees and the ceiling is above 2000... but then half a degree doesn't matter, and getting your ass out of there does.) Still, you get about 256 shades to play with from coldest to hottest, so if you manage what's in view, you can get fairly decent results.
ZZzzzzt... well said, but you missed it.
"Abuse" of the patriot act would mean to deviate from what it allows, or use it in a way that is not appropriate. Even if an evaluator has full access to all actions taken under it - finding "no abuse" simply means that all actions taken were consistent with the Act. In no way, shape, or form does this mean that "abuse" didn't take place relative to preexisting law. If the Act allows for murder, for example, anyone who murders under the premise of the Act is *not* abusing it. They may well be abusing other law - but that's far outside the scope of the evaluation, isn't it.
So, secrets have little to do with this. The Act permits egregious behavior; thus far, all egregious actions taken appear to be allowed by that act, and no "abuse" has occurred.
Nope, what if you have PARALLEL PROCESSORS? Who's the idiot now?
Nah, you don't need to spend that much. You can bottom-feed off the low end for about $13 grand for a fixed-notch greyscale bolometer type. Better ones will run up to 20 grand, and offer a full floating, variable width notch with false color representation.
Granted, these are all intended for structural firefighting, so they aren't cheap. But they *are* intended to be dropped, kicked, and roasted. Obviously, you'll trade weight for battery life and heat shielding - the Draegers have full Ni cladding and can survive long exposure, but they weigh a lot. The Scotts are much lighter, but don't get them above 600 degrees...
Oh, it gets worse.
.ini-file based databases. If we can make a database revolving around XML, we can use those exact same arguments to make one that revolves around .ini files. And, the .ini file approach will be more extensible and robust, since it has strong legacy support.
I'm proposing that we start a brand new paradigm -
Well, you really need to have a TCP/IP based File I/O for any performance with an XML database. Although technically, you would probably get better gains by switching to an HTML database. The HTML database would be better, anyway, because it'll run in any web browser, and it doesn't exactly care what filesystem is in use. That, and all these "data integrity" whiners can then use any CSS validator to check the validity of the data. That way, your HTML Programmers can write on whatever platform they wish, enabling a new paradigm for a pan-dimensional database structure to coexist and re-leverage new legacies before they are implemented, in a cost-efficient and transcendentally transparent manner.
I found that Dilbert, btw! It was an E-Mail based database! Now if you'll please excuse me, I'll be over here, ducking under a table.
... is that XML is only half of the solution.
For an XML database to really shine, it needs to be integrated with with a TCP/IP filesystem. Once the physical data is stored using TCP/IP (as opposed to FAT or NTFS), the XML database really begins to take off because the data is already in a network format.
I swear to god there was a Dilbert on this...
You can get... uh, sort-of tabs with PEI+ (pay), or real tabs with FTXBrowser (free). Both just wrap PIE, but they work.
Actually, it's a money issue.
.NET is a further push for lock-in via the Application Barrier. By enabling the 10k Monkey technique, it causes software vendors to be dependant on the MS platform because the better "fast/cheap/correct" ratio allows for better pricing or margins. Likewise, this will steer the enterprise toward these vendors. And Since the enterprise is dependant on the vendor... well, the enterprise now requires MS for a cost-effective development model, and the lock-in (application barrier) is complete.
From the management side, it further enables the 10,000 monkey technique of writing code. Quite literally, it lowers the requires skillset for production... ergo reduces the "Fast, Cheap, Correct... pick Two" paradox.
From the coder's side, there's a small group-think issue... but actual reasons will depend on the individual. VB weenies will like it because they can pretend to be competent. More talented coders will tolerate it because the crap developed by the VB crowd can be better managed / mitigated. Those in the middle will like it because it has better screen-sav^H^H^H colors.
From the Microsoft side,
So goes the theory, at least.
It's not coincidence. QDos was a CP/M ripoff - as any MASM hacker can tell you, one need only take a look at an exe's PSP to see it, byte for byte.
Case closed, IMO.
BZZZT... negative.
They were BOUGHT by those companies in the EXACT SAME WAY that a terrestrial radio or TV station BOUGHT their frequencies. I ought to know - I've bought a few.
Airwaves are airwaves - the law does not concede "ownership" of them... only exclusivity in transmit rights. Big difference.
I've very glad you feel better. You're still just as dead when the plane blows up, but at least now you can feel good about it.