There are no such words as "amazing" or "shocking". Pretending that there are is double-plus ungood.
In other news, we would like to stress that we never were at war with Oceana, that black is white, night is day and, most importantly, that it is unpatriotic to think.
Invoking the War Powers Act is not the same as delcaring war. The Viet Nam Conflict was fought under the hWar Powers Act, but we never did declare war on North Viet Nam. Neither have we declared war now, in any but a metephorical sense.
For mine, I hope it was not, given that I'm replying to you.
Intel made a CPU that churns at a significantly higher clock speed in order to perform almost as well as AMDs "slower" chip. That is a case of "the company with the most resources, experience, and capital [securing] their lead"?
Wow. The sky must be a bizar color in your world. The sky in mine appears blue; and AMD still has the performace lead.
The Tech-Report article points out a couple interesting meta-ideas - this is Intel's chance to retake the performance crown from AMD, as well as being one of those round numbers that makes people feel warm and fuzzy.
How in Bob's name are those "meta-ideas"?!
They are not ideas about ideas, they are simply ideas. Why do people feel the need to adorn their words with unnecessary cruft? I guess the old gearhead saying applys to prose as well: "If it don't go, chrome it".
<sigh>
This should be listed as a special case of Rule 17.
While I applaud the idea, and champion it myself, users and marketeers will resist this to the end.
You see, security isn't user friendly.
<sight>
When I've tried to push a "secure by default" position in the past, the response I usually get is: "But that would be a pain for the user! Let's make the secure configuration an option. The user that really needs security can just turn it on".
The rub is, the ones who really need it don't now enough to turn it on.
How is this a bad thing, except for their competitors? The networks are their property, why shouldn't they be able to do what they want with it.
bah!
/. really has become "News for whiners, stuff that only makes sense in some bullshit utopian Star Trek world."
--
If your map and the terrain differ,
trust the terrain.
Unless you're a/.er, of course, in which case you should whine that the terrain should conform to your map, but not actually what is shown on your map, but what you interpret the map to really mean. And if the Earth is so evil as to not conform to your imagined reality, it should be forced to. Because as we all know, freedom is good, unless it's someone else's freedom.
While is a concern, I believe that it will be a problem in the long run. If insurance companies do pull a stunt like this, they will simply be replaced by companies that will take care of their clients, or by private groups that will band together to negotiate with drug companies and providers for reasonable rates.
Of course, this is assuming that we (here in the US) can keep at least a nominally market driven health care system.
--
If your map and the terrain differ,
trust the terrain.
Actually, I think it would have had much the same effect on the OS front, once that pesky little AT&T lawsuit was resolved.
BSD arguably did have a similar effect if you consider the bigger picture of UNIX and TCP/IP. Not to mention the fact that two of the largest Free Software projects use a copyright agreement similar to BSD: Apache and X.
--
If your map and the terrain differ,
trust the terrain.
Or perhaps they knew about infringment some time ago. Magnequench asked the infringing manufacturers to pay up, and the infringers refused or ignored them. Bringing suit would be the final recourse. Users of the magnets (who are not actually the infringers) are brought into the case to a) bring publicity and b) bring pressure on the magnet suppliers to settle.
Or perhaps not.
Unless you have evidence one way or the other, I don't see what justification you have to accuse them.
--
If your map and the terrain differ,
trust the terrain.
I see several errors in your post. First of all, you seem to imply that Free Software/Open Source Software cannot be commercial (i.e. "for pay" as you put it). That is patently false. What it cannot be is proprietary.
Secondly, in your analysis of your options if you want an added feature in a piece of software, you overlook another option. You could pay someone to add the feature you want. They may require (as rms does) that you allow the change to be rolled into the main distribution as Free Software. In this case you're paying for the work needed to add the feature, not the feature itself. On the other hand, you might be buying your own custom version of the software, if it is the orignal author, or if the license allows for it (BSD for instance). In addition, with Free Software you can always get the feature you want if you are willing to pay for it. You can pay someone to do it, even if they are not the original author. How much pull do have with Microsoft or Oracle?
Either way, you get your feature, and the main program stays free.
As for your "point" about some "Socialist" ideal, you really need to think about this in more than a superficial manner. There's nothing wrong with charging you for the software. In fact, I don't see a big deal with limiting your ability to distribute changed code (a la the old QT versions)... I write the code, I get to pick the terms. I simply recognise the increased total value of the code when it is released as Free Software, at least in many cases.
--
If your map and the terrain differ,
trust the terrain.
Some of these might be of interest. Remember: Google and boolean logic searches are your friend.
--
If your map and the terrain differ,
trust the terrain.
They do make devices as well. Heard of the Palm Vx, Palm IIIxe, Palm M100, or Palm VIIx? In fact they also OEM devices for IBM.
No really. They do. Honest. I have one right here.
They also made the OS, and license it to Sony, Handspring, Symbol, TRG, etc.
--
If your map and the terrain differ,
trust the terrain.
I also enjoyed Heiserman's books. I built some simple robots "back in the day" when those books were still in print. I have a copy of the machine intelligence one at the very least, I think I have one of the others as well. (not for sale, tho!)
I spent quite a bit of time as a teen playing with MI. Was alot of fun, even tho the computing power I had at my disposal was a wopping 16K CoCo (later a 64K CoCo, the 256K bank switched, but that's for another discussion). It might be fun to break out my notes and play w/it some more now that the Palm Vx I have is more powerful!
I have no idea where Heiserman went, but if he did anything interesting it should be out there, either on the web or in Gopher space. I think I'll have a look later tonight. I'll report back if I find anythin!
--
If your map and the terrain differ,
trust the terrain.
Html is fine as an online manual format, as long as the pages are lynx friendly. Lynx starts up quick, runs fast, and most importantly, lynx can use a vi keymap. It has the advantage (over info) of being a standard format that most everyone knows some of, and that has many tools for manipulating/generating it.
Still and all, manpages are "the right thing" for basic docs. For html to replace it, we'd need to do the equiv of the manpath for lynx. Setting a default page with an index of available "man" pages would be close, but not as easy as typing "man foo" to get help on foo.
Short version: Use html for more indepth online manuals. Long live man! 'nuff said.
--
If your map and the terrain differ,
trust the terrain.
Actually, my Yamaha CDRW is SCSI/FW hybrid. At 8x there's no bottle neck.
My points still hold: (1) FC does 1 Gig and 2 Gig today and (2) FC can (and often is) configured in a switched configuration. AFAIK IEEE1394 isn't a switched archetecture.
Bottom line: IEEE-1394 is great for consumer external storage, consumer and some pro digital imaging and video, and perhaps digital audio. It doesn't play in the same league as FC, though. --
If your map and the terrain differ,
trust the terrain.
Lot of overhead? 36 bytes in a basic FC header. Yeah, lots of overhead. Granted, a loop config has overhead for ARB, but a switched config seems pretty low overhead to me. And 70MB/s?! Piss poor config then, or a non-switched setup w/too many devices on a loop. In another window right now I'm seeing 88MB/s on a FFL connection (QLA2200 HBA to an inexpensive Euorlogic JBOD.) I've seen solid 90s.
As for Linux support, QLogic cards are supported under Linux... heck, even FreeBSD has basic QLogic support.
*** disclaimer: I work for QLogic. These are my opinions, not those of QLogic *** --
If your map and the terrain differ,
trust the terrain.
*** disclaimer : I work for QLogic, a major FC player. these are my opinions only, and do not represent those of QLogic Corp. ***
Well, to be a bit more honest, you can get QLA2200/33 cards (copper) for around $830 retail, 66MHz PCI version for around $950 retail. For the $1200 you quote, you can get a 2202 in copper (dual FC on one card) or a 2200 optical and still have $100 - $200 left over. Hell, you can get a 2300 for around $1300 (2 Gb/s).
I'll grant you that the switches tend to cost a bit more than GigE, but then they scale better in a storage application, too.
Bottom line is that neither GigE, nor FC are "dead tech". Both have a long life ahead of 'em in their respective niches: GigE for high speed packet switched networks, FC for storage and video.
Again, all IMNSHO. --
If your map and the terrain differ,
trust the terrain.
Slashdot Mirror
rm -rf /bin/Laden
shouldn't it? And while we're at it:
rm -rf /al\ Qaeda
In other news, we would like to stress that we never were at war with Oceana, that black is white, night is day and, most importantly, that it is unpatriotic to think.
Thank you.
Invoking the War Powers Act is not the same as delcaring war. The Viet Nam Conflict was fought under the hWar Powers Act, but we never did declare war on North Viet Nam. Neither have we declared war now, in any but a metephorical sense.
They have the TECHNIC Pneumatic Pack for US$ 27.99.
Between Lego, Pitsco and EBay you can get pretty much whatever you might want to build sweet Midstorms 'bots.
Happy shopping.
For mine, I hope it was not, given that I'm replying to you.
Intel made a CPU that churns at a significantly higher clock speed in order to perform almost as well as AMDs "slower" chip. That is a case of "the company with the most resources, experience, and capital [securing] their lead"?
Wow. The sky must be a bizar color in your world. The sky in mine appears blue; and AMD still has the performace lead.
How in Bob's name are those "meta-ideas"?!
They are not ideas about ideas, they are simply ideas. Why do people feel the need to adorn their words with unnecessary cruft? I guess the old gearhead saying applys to prose as well: "If it don't go, chrome it".
<sigh>
This should be listed as a special case of Rule 17.
While I applaud the idea, and champion it myself, users and marketeers will resist this to the end.
You see, security isn't user friendly.
<sight>
When I've tried to push a "secure by default" position in the past, the response I usually get is: "But that would be a pain for the user! Let's make the secure configuration an option. The user that really needs security can just turn it on".
The rub is, the ones who really need it don't now enough to turn it on.
bah!
-- /.er, of course, in which case you should whine that the terrain should conform to your map, but not actually what is shown on your map, but what you interpret the map to really mean. And if the Earth is so evil as to not conform to your imagined reality, it should be forced to. Because as we all know, freedom is good, unless it's someone else's freedom.
If your map and the terrain differ,
trust the terrain.
Unless you're a
Of course, this is assuming that we (here in the US) can keep at least a nominally market driven health care system.
--
If your map and the terrain differ,
trust the terrain.
BSD arguably did have a similar effect if you consider the bigger picture of UNIX and TCP/IP. Not to mention the fact that two of the largest Free Software projects use a copyright agreement similar to BSD: Apache and X.
--
If your map and the terrain differ,
trust the terrain.
Or perhaps not.
Unless you have evidence one way or the other, I don't see what justification you have to accuse them.
--
If your map and the terrain differ,
trust the terrain.
I see several errors in your post. First of all, you seem to imply that Free Software/Open Source Software cannot be commercial (i.e. "for pay" as you put it). That is patently false. What it cannot be is proprietary.
Secondly, in your analysis of your options if you want an added feature in a piece of software, you overlook another option. You could pay someone to add the feature you want. They may require (as rms does) that you allow the change to be rolled into the main distribution as Free Software. In this case you're paying for the work needed to add the feature, not the feature itself. On the other hand, you might be buying your own custom version of the software, if it is the orignal author, or if the license allows for it (BSD for instance). In addition, with Free Software you can always get the feature you want if you are willing to pay for it. You can pay someone to do it, even if they are not the original author. How much pull do have with Microsoft or Oracle?
Either way, you get your feature, and the main program stays free.
As for your "point" about some "Socialist" ideal, you really need to think about this in more than a superficial manner. There's nothing wrong with charging you for the software. In fact, I don't see a big deal with limiting your ability to distribute changed code (a la the old QT versions) ... I write the code, I get to pick the terms. I simply recognise the increased total value of the code when it is released as Free Software, at least in many cases.
--
If your map and the terrain differ,
trust the terrain.
Actually there are several driving techniques sites. Here are a few:
Drivers Club
Bootlegger turn
The Chronicle's list of driving related sites
Some of these might be of interest. Remember: Google and boolean logic searches are your friend.--
If your map and the terrain differ,
trust the terrain.
OK, so how do you propose coming to the point where no one else has guns? Seriously. I'd like to know.
Also, consider that, if the person next to you at the bar might be armed, would you be as likely to take a swing at her? Or even be overly rude?
--
If your map and the terrain differ,
trust the terrain.
for some definitions of "low", anyway.
don't people ever get tired of "my dick is bigger than your's so I must be better than you"?
--
If your map and the terrain differ,
trust the terrain.
uh, no.
The founders of Palm did leave to start Handspring, though. That might be what you're thinking of.
--
If your map and the terrain differ,
trust the terrain.
Yeah, it is. I suck. What can I say.
--
If your map and the terrain differ,
trust the terrain.
As amusing as this is, I have to ask: If you're "not making this up", you must have a reference you can site for this "definition", right?
Feel free to break /. tradition and back up your statement by siting your source. I won't tell on you.
--
If your map and the terrain differ,
trust the terrain.
They do make devices as well. Heard of the Palm Vx, Palm IIIxe, Palm M100, or Palm VIIx? In fact they also OEM devices for IBM. No really. They do. Honest. I have one right here.
They also made the OS, and license it to Sony, Handspring, Symbol, TRG, etc.
--
If your map and the terrain differ,
trust the terrain.
I also enjoyed Heiserman's books. I built some simple robots "back in the day" when those books were still in print. I have a copy of the machine intelligence one at the very least, I think I have one of the others as well. (not for sale, tho!)
I spent quite a bit of time as a teen playing with MI. Was alot of fun, even tho the computing power I had at my disposal was a wopping 16K CoCo (later a 64K CoCo, the 256K bank switched, but that's for another discussion). It might be fun to break out my notes and play w/it some more now that the Palm Vx I have is more powerful!
I have no idea where Heiserman went, but if he did anything interesting it should be out there, either on the web or in Gopher space. I think I'll have a look later tonight. I'll report back if I find anythin!
--
If your map and the terrain differ,
trust the terrain.
Not to be pedantic, but those were MAC-10s, not Uzis.
--
If your map and the terrain differ,
trust the terrain.
Still and all, manpages are "the right thing" for basic docs. For html to replace it, we'd need to do the equiv of the manpath for lynx. Setting a default page with an index of available "man" pages would be close, but not as easy as typing "man foo" to get help on foo.
Short version: Use html for more indepth online manuals. Long live man! 'nuff said.
--
If your map and the terrain differ,
trust the terrain.
My points still hold: (1) FC does 1 Gig and 2 Gig today and (2) FC can (and often is) configured in a switched configuration. AFAIK IEEE1394 isn't a switched archetecture.
Bottom line: IEEE-1394 is great for consumer external storage, consumer and some pro digital imaging and video, and perhaps digital audio. It doesn't play in the same league as FC, though.
--
If your map and the terrain differ,
trust the terrain.
As for Linux support, QLogic cards are supported under Linux ... heck, even FreeBSD has basic QLogic support.
*** disclaimer: I work for QLogic. These are my opinions, not those of QLogic ***
--
If your map and the terrain differ,
trust the terrain.
Well, to be a bit more honest, you can get QLA2200/33 cards (copper) for around $830 retail, 66MHz PCI version for around $950 retail. For the $1200 you quote, you can get a 2202 in copper (dual FC on one card) or a 2200 optical and still have $100 - $200 left over. Hell, you can get a 2300 for around $1300 (2 Gb/s).
I'll grant you that the switches tend to cost a bit more than GigE, but then they scale better in a storage application, too.
Bottom line is that neither GigE, nor FC are "dead tech". Both have a long life ahead of 'em in their respective niches: GigE for high speed packet switched networks, FC for storage and video.
Again, all IMNSHO.
--
If your map and the terrain differ,
trust the terrain.