What is Digg?Sponsored by Sony Pictures
Watch a scene from 2012, in theaters November 13 view!
whowillsurvive2012.com - Get ready for the biggest event in history – the end of time. How will you survive? 2012- opening 11/13
30 Comments
- adidax, on 10/12/2007, -0/+14 (11) Every old idea will be proposed again with a different name and
a different presentation, regardless of whether it works.
Can anybody say Web 2.0? - CurtHowland, on 10/12/2007, -0/+9I like applying #12 to IPv6. If IPv6 had increased the address space, made the headers a static length, and then STOPPED, it would have been wonderful. Everything other than source, destination and time to live is an application issue, not a network issue.
- Unr3a1, on 10/12/2007, -0/+8"Good, Fast, Cheap: Pick any two (you can't have all three)."
Timelessly true. - charlietuna, on 10/12/2007, -2/+9http://web.mit.edu/adorai/www/seuss-technical-writing.html
I have no idea who wrote this, but it's awesome.
Here's an easy game to play.
Here's an easy thing to say:
If a packet hits a pocket on a socket on a port,
And the bus is interrupted as a very last resort,
And the address of the memory makes your floppy disk abort,
Then the socket packet pocket has an error to report!
If your cursor finds a menu item followed by a dash,
And the double-clicking icon puts your window in the trash,
And your data is corrupted 'cause the index doesn't hash,
Then your situation's hopeless, and your system's gonna crash!
You can't say this?
What a shame sir!
We'll find you
Another game sir.
If the label on the cable on the table at your house,
Says the network is connected to the button on your mouse,
But your packets want to tunnel on another protocol,
That's repeatedly rejected by the printer down the hall,
And your screen is all distorted by the side effects of gauss
So your icons in the window are as wavy as a souse,
Then you may as well reboot and go out with a bang,
'Cause as sure as I'm a poet, the sucker's gonna hang!
When the copy of your floppy's getting sloppy on the disk,
And the microcode instructions cause unnecessary risc,
Then you have to flash your memory and you'll want to RAM your ROM.
Quickly turn off the computer and be sure to tell your mom! - TimTheEnchanter, on 10/12/2007, -0/+5My favorite "April 1" RFCs are
rfc 1149
http://www.faqs.org/rfcs/rfc1149.html
rfc 2549
http://www.faqs.org/rfcs/rfc2549.html
There's a digg on someone that successfully implemented 1149. - kloof, on 10/12/2007, -1/+6All exciting at first but then you get sick of it.
(corollary) Pancakes. - inactive, on 10/12/2007, -0/+4There are lots of similar "joke" RFC's out there.
http://www.livinginternet.com/i/ia_rfc_fun.htm
.. Most of them dated april 1st.. - StarCrusher, on 10/12/2007, -0/+4"It's more complicated than you think."
It usually is. - coolwalking, on 10/12/2007, -0/+3My fave is the Infinite Monkey Protocol Suite (IMPS) (http://www.ietf.org/rfc/rfc2795.txt). I did a networking project on it. Solid C :)
- strictnein, on 10/12/2007, -0/+2@floorman: Hopefully someone will print a copy of "The Elements of Style" for you.
- adml_shake, on 10/12/2007, -0/+2You put me to sleep at "Status of this Memo"
- trejrco, on 10/12/2007, -1/+3Interesting take, however the counter-point might be to say that also fixing known problems (and/or preemptively addressing new ones) is a noble goal ...
- Johnpaine, on 10/12/2007, -0/+2all RFCs are completely retarded anyways.
- floorman56, on 10/12/2007, -1/+3That will be printed on my sales person computer Tue morning!!!!!!
- CurtHowland, on 10/12/2007, -1/+3"Fixing known problems"... Hmmm.....
Let's see. You have a packet, with a source, destination and time to live. What problem might there be delivering that packet that is not dependent upon something other than the network protocol?
No route? Circular route? Congestion? None of which have anything to do with that packet. Everything that a network device _needs_ is in those three elements.
But I did indeed leave something out. Payload size. My apologies, make that 4 elements, which the IPv6 headers do an excellent job of encapsulating.
I'm not going to say that someone may not _want_ to filter for QoS for specific applications, or complicate matters with UDP, TCP, ports and things like that. But those are easily contained within the payload to be codified and dealt with by the end points or by other specialized hardware that decodes the packets to decide what they are.
Too bad that IPv6 had to go the other way, and load the "protocol" with so much cruft. Second System Syndrome in action. I wonder what would happen if someone officially pointed out that IPv6 violates RFC 1925(12)?
But I'm very "old school". I like very stupid network devices combined with very smart hosts. I think it comes from spending years debugging wacky network problems in the middle of the night. - zcreem, on 10/12/2007, -2/+3No matter how long you think it will take, it always takes longer.
[collary] Iraq. - nofxjunkee, on 10/12/2007, -1/+2rfc 1149 never gets old
http://www.blug.linux.no/rfc1149/ - inactive, on 10/12/2007, -0/+1http://tools.ietf.org/html/rfc1149
- panfist, on 10/12/2007, -0/+1I didn't find anything hilarious or insightful about this joke document.
"No matter how hard you push and no matter what the priority, you can't increase the speed of light."
Forgive me for not being awed or laughing. These "truths" are so lame and tired they remind me of why I rarely talk to my CS and IT classmates. - darthgarlic, on 10/12/2007, -2/+2There should be an addition to this stating you will always have a manager that has no clue about what you do.
- inactive, on 10/12/2007, -1/+1I love all those April 1st RFC`s :)
There are also a lot of poems in a couple of RFC`s. Just do a fulltext search for 'poem' :) - dbremer, on 10/12/2007, -0/+0my favorite is #3 - "with enough thrust pigs fly just fine"
But for them to add the caveats is truely insightful and hilarious - codemonkey2841, on 10/12/2007, -1/+1Mitch Hedberg FTW!
- phjr, on 10/12/2007, -1/+1That's true. Multiple interdependencies are a nightmare in such systems.
- adml_shake, on 10/12/2007, -1/+1Why is he being modded down?! This is 100% true!
- egrumling, on 10/12/2007, -1/+1@charlietuna
Gilbert and Sullivan maybe?
http://en.wikipedia.org/wiki/Gilbert_and_sullivan - diggsIt, on 10/12/2007, -3/+2Windows OS - No. 5 on the list.
- inactive, on 10/12/2007, -3/+1For some reason I'm getting a domain parking page
- nofxjunkee, on 10/12/2007, -6/+2wtf... bury this, stupid digg comments...
- airborne99, on 10/12/2007, -7/+3 (1) It Has To Work.
(2) No matter how hard you push and no matter what the priority,
you can't increase the speed of light.
(2a) (corollary). No matter how hard you try, you can't make a
baby in much less than 9 months. Trying to speed this up
*might* make it slower, but it won't make it happen any
quicker.
(3) With sufficient thrust, pigs fly just fine. However, this is
not necessarily a good idea. It is hard to be sure where they
are going to land, and it could be dangerous sitting under them
as they fly overhead.
(4) Some things in life can never be fully appreciated nor
understood unless experienced firsthand. Some things in
networking can never be fully understood by someone who neither
builds commercial networking equipment nor runs an operational
network.
(5) It is always possible to aglutenate multiple separate problems
into a single complex interdependent solution. In most cases
this is a bad idea.
(6) It is easier to move a problem around (for example, by moving
the problem to a different part of the overall network
architecture) than it is to solve it.
(6a) (corollary). It is always possible to add another level of
indirection.
(7) It is always something
(7a) (corollary). Good, Fast, Cheap: Pick any two (you can't
have all three).
(8) It is more complicated than you think.
(9) For all resources, whatever it is, you need more.
(9a) (corollary) Every networking problem always takes longer to
solve than it seems like it should.
(10) One size never fits all.
(11) Every old idea will be proposed again with a different name and
a different presentation, regardless of whether it works.
(11a) (corollary). See rule 6a.
(12) In protocol design, perfection has been reached not when there
is nothing left to add, but when there is nothing left to take
away.
© Digg Inc. 2009
— Content created and posted by Digg users is