It's funny you say that - b/c the whole time I was talking about the IEEE (remember, thats what got the conversation started).
Hmm, let's review, with the important information being <b><font color=red>blatantly obvious</b></font color=red> for even people with the most selective of memories:
In reply to:
--------------------------------------------------------------------------------
IEEE does standards for more than just firewire - they do basically everything. I have a personal relationship with IEEE 802.3 standard (10gig specifically) - its a scary place - I don't reccommend hanging out there. ;-)
--------------------------------------------------------------------------------
I know. I was just being silly. When most people hear IEEE, the first thing that comes to mind is Firewire, even if they can't recall the 1394 part.
And the Institute of Electrical and Electronics Engineers is a bit scary. I'm all for standards, but I'm also leery of <b><font color=red>anyone</b></font color=red> who makes them. <b><font color=red>ANSI is a perfect example.</b></font color=red> Everyone claims <b><font color=red>ANSI C++ compliance</b></font color=red>, yet no one actually adheres to it 100% and no one takes away that compliancy label for not adhering 100%.
<pre><font color=blue>If you don't give me accurate and complete system specs
then I can't give you an accurate and complete answer.</pre><p></font color=blue>
In reply to:
--------------------------------------------------------------------------------
<b><font color=red>you should be all for standards</b></font color=red> b/c without them <b><font color=red>nothing</b></font color=red> would work together. There are parts of <b><font color=red>the standards</b></font color=red> that don't get followed as much but for the most part the important stuff is followed and you can use your ethernet gear anywhere, anytime, and with basically any other peice of ethernet gear. It's better for the industry and it's better for the end-user.
--------------------------------------------------------------------------------
Tell that to the early adoptors of wireless ethernet devices who couldn't even get a simple wireless network to run because the devices didn't conform perfectly to standards and often only worked with devices built by the same manufacturer.
Tell that to the early adoptors of Firewire devices who often couldn't even use the same device on both a Mac and a PC even with drivers for both.
Tell that to the early adoptors of USB devices who often couldn't tell which PCs with USB ports their USB devices would run on until they tried to use them.
<b><font color=red>Tell that to anyone trying to write cross-platform ANSI C++ source code only to find a million and one compilers that claim to conform to the standard but in reality don't and so you end up having to make minor modifications to your ANSI C++ source code just so that it will compile on certain ANSI C++ compilers.</b></font color=red>
Don't get me wrong. I'm all for standards. I just have a very strong innate distrust in manufacturers actually following those standards 100.00%, even when they claim to. (Perhaps especially if they claim to.) Standards are great if they're followed exactly to the letter. It is just too bad that they hardly ever are, and yet they still get to claim compatability.
<pre><font color=blue>I'm proud to be an American,
who served my country in the US Air Force,
to protect the rights of my fellow Americans,
to hold protests against others like me.</pre><p></font color=blue>
Gee, I see an awful lot of talk about <b>all</b> standards going on here. And not even just from me, but from this 'tommunist' bloke too.
Wait a second! <b>You're</b> tommunist! Gee, you really showed me how "<b><font color=red>the whole time</b></font color=red>" <i>you</i> were "<b><font color=red>talking about the IEEE</b></font color=red>". Why, I'll never doubt your infinite wisdom and perfect memory again. You are God!
If you are going to use IEEE standards as an example to argue that it is standards organizations fault when devices aren't compliant I will simply say that you are wrong in that the IEEE doesn't do this and never has.
<b>Repeatedly</b> I listed more than just IEEE. Also repeatedly I made it clear that I was talking about <b>all</b> standards, <b>as did <i>you</i></b>.
So yeah - I did read your posts
Not only did you quite clearly <b>not</b> read my posts, but you also obviously never read your own posts either!
so before you throw an insult out there and run away crying like a baby you should maybe read over the argument you were trying to make and the examples you were trying to use to make it
Funny, I don't recall seeing any crying involved. Hell, I don't even see any running away involved. I simply see one arse who can't even follow his own posts, not to mention other people's. Gee, I can't imagine why <i>anyone</i> would be inclined to stop bothering to hold a conversation with someone like that. It couldn't possibly be because even holding a conversation with a brick wall would be more entertaining.
Now if you'll excuse me, I believe that my point is already crystal clear while yours is mucking around in a cesspool of your own making. I've had quite enough of your ineptitude at conversation. Good day.
<font color=blue><pre>I'm proud to be an American,
who served my country in the US Air Force,
to protect the rights of my fellow Americans,
to hold protests against others like me.</pre><p></font color=blue>
* Editied because of a bug in the forum software making quote blocks non-recursive.<P ID="edit"><FONT SIZE=-1><EM>Edited by slvr_phoenix on 04/16/03 09:12 AM.</EM></FONT></P>