Dictionary De - En
De - Es
De - Pt| Proverbs, aphorisms, quotations (English) | by Linux fortune |
| BYTE editors are people who separate the wheat from the chaff, and then carefully print the chaff. | |
| Byte your tongue. | |
| Computer programmers do it byte by byte. | |
| I have not yet begun to byte! | |
| Long ago, in a finite state far away, there lived a JOVIAL character named Jack. Jack and his relations were poor. Often their hash table was bare. One day Jack's parent said to him, "Our matrices are sparse. You must go to the market to exchange our RAM for some BASICs." She compiled a linked list of items to retrieve and passed it to him. So Jack set out. But as he was walking along a Hamilton path, he met the traveling salesman. "Whither dost thy flow chart take thou?" prompted the salesman in high-level language. "I'm going to the market to exchange this RAM for some chips and Apples," commented Jack. "I have a much better algorithm. You needn't join a queue there; I will swap your RAM for these magic kernels now." Jack made the trade, then backtracked to his house. But when he told his busy-waiting parent of the deal, she became so angry she started thrashing. "Don't you even have any artificial intelligence? All these kernels together hardly make up one byte," and she popped them out the window... -- Mark Isaak, "Jack and the Beanstack" | |
| "Section 2.4.3.5 AWNS (Acceptor Wait for New Cycle State). In AWNS the AH function indicates that it has received a multiline message byte. In AWNS the RFD message must be sent false and the DAC message must be sent passive true. The AH function must exit the AWNS and enter: (1) The ANRS if DAV is false (2) The AIDS if the ATN message is false and neither: (a) The LADS is active (b) Nor LACS is active" -- from the IEEE Standard Digital Interface for Programmable Instrumentation | |
| "Virtual" means never knowing where your next byte is coming from. | |
| "We invented a new protocol and called it Kermit, after Kermit the Frog, star of "The Muppet Show." [3] [3] Why? Mostly because there was a Muppets calendar on the wall when we were trying to think of a name, and Kermit is a pleasant, unassuming sort of character. But since we weren't sure whether it was OK to name our protocol after this popular television and movie star, we pretended that KERMIT was an acronym; unfortunately, we could never find a good set of words to go with the letters, as readers of some of our early source code can attest. Later, while looking through a name book for his forthcoming baby, Bill Catchings noticed that "Kermit" was a Celtic word for "free", which is what all Kermit programs should be, and words to this effect replaced the strained acronyms in our source code (Bill's baby turned out to be a girl, so he had to name her Becky instead). When BYTE Magazine was preparing our 1984 Kermit article for publication, they suggested we contact Henson Associates Inc. for permission to say that we did indeed name the protocol after Kermit the Frog. Permission was kindly granted, and now the real story can be told. I resisted the temptation, however, to call the present work "Kermit the Book." -- Frank da Cruz, "Kermit - A File Transfer Protocol" | |
| "BYTE editors are men who seperate the wheat from the chaff, and then print the chaff." -- Lionel Hummel (uiucdcs!hummel), derived from a quote by Adlai Stevenson, Sr. | |
| I/O, I/O, It's off to disk I go, A bit or byte to read or write, I/O, I/O, I/O... | |
| SHIFT TO THE LEFT! SHIFT TO THE RIGHT! POP UP, PUSH DOWN, BYTE, BYTE, BYTE! | |
| Shift to the left, Shift to the right, Mask in, mask out, BYTE, BYTE, BYTE !!! | |
| Strange things are done to be number one In selling the computer The Druids were entrepreneurs, IBM has their strategem And they built a granite box Which steadily grows acuter, It tracked the moon, warned of monsoons, And Honeywell competes like Hell, And forecast the equinox But the story's missing link Their price was right, their future Is the system old at Stonemenge sold bright, By the firm of Druids, Inc. The prototype was sold; From Stonehenge site their bits and byte Would ship for Celtic gold. The movers came to crate the frame; It weighed a million ton! The traffic folk thought it a joke The man spoke true, and thus to you (the wagon wheels just spun); A warning from the ages; "They'll nay sell that," the foreman Your stock will slip if you can't ship spat, What's in your brochure's pages. "Just leave the wild weeds grow; See if it sells without the bells "It's Druid-kind, over-designed, And strings that ring and quiver; "And belly up they'll go." Druid repute went down the chute Because they couldn't deliver. -- Edward C. McManus, "The Computer at Stonehenge" | |
| I have replaced NT with Linux. Linux -- heir of the byte that dogged me. -- Allan Willis | |
| Brief History Of Linux (#18) There are lies, damned lies, and Microsoft brochures Even from the very first day, the Microsoft Marketing Department was at full throttle. Vaporware has always been their weapon of choice. Back when MS-DOS 1.25 was released to OEMs, Microsoft handed out brochures touting some of the features to be included in future versions, including: Xenix-compatible pipes, process forks, multitasking, graphics and cursor positioning, and multi-user support. The brochure also stated, "MS-DOS has no practical limit on disk size. MS-DOS uses 4-byte Xenix compatible pointers for file and disk capacity up to 4 gigabytes." We would like to emphasize in true Dave Barry fashion that we are not making this up. Big vaporous plans were also in store for Microsoft's "Apple Killer" graphical interface. In 1983 Microsoft innovated a new marketing ploy -- the rigged "smoke-and-mirrors" demo -- to showcase the "overlapping windows" and "multitasking" features of Interface Manager, the predecessor to Windows. These features never made it into Windows 1.0 -- which, incidentally, was released 1.5 years behind schedule. | |
| indent does _not_ solve the problem of: * buggers who use typedefs like WORD, DWORD, BYTE, IMANIDIOTSHOOTME and other crap from the same source (OK, they don't write the last one explicitly - not that it wasn't obvious from the rest of their, ahem, code). - Alexander Viro on coding style | |
