For comparison, “amazing” occurs six times.
And most of those cases are of course using the word sarcastically
collapsed list of them
The next function to implement is called, amazingly, next(); its job is to move the iterator forward to the next position in the sequence. if (lc->sync == NOSYNC) for (i = lc->header.nr_regions; i < lc->region_count; i++) /* FIXME: amazingly inefficient */ log_set_bit(lc, lc->clean_bits, i); else for (i = lc->header.nr_regions; i < lc->region_count; i++) /* FIXME: amazingly inefficient */ log_clear_bit(lc, lc->clean_bits, i); /* * Amazingly, if ehv_bc_tty_open() returns an error code, the tty layer will * still call this function to close the tty device. So we can't assume that * the tty port has been initialized. */ * this header was blatantly ripped from netfilter_ipv4.h * it's amazing what adding a bunch of 6s can do =8^) /* * I studied different documents and many live PROMs both from 2.30 * family and 3.xx versions. I came to the amazing conclusion: there is * absolutely no way to route interrupts in IIep systems relying on * information which PROM presents. We must hardcode interrupt routing * schematics. And this actually sucks. -- zaitcev 1999/05/12 * corresponding ABS_X and ABS_Y events. This turns the Twiddler into a game * controller with amazing 18 buttons :-) * In an amazing feat of design, the Enhanced Features Register (EFR) * shares the address of the Interrupt Identification Register (IIR). * Access to EFR is switched on by writing a magic value (0xbf) to the * Line Control Register (LCR). Any interrupt firing during this time will * see the EFR where it expects the IIR to be, leading to * "Unexpected interrupt" messages. * Thanks BUGabundo and Malmostoso for your amazing help!
Only one of them barely reaching 200. For the size of the Linux kernel I find these numbers surprisingly low.
Coding is a very… emotional activity. We get a bit salty sometimes.
I remember commenting a particularly bad routine with “Lasciate ogne speranza, voi ch’intrate”.
There are also phrases such as “by the process of offending god, this somehow outputs…” and “This block was written by someone whose sanity was not so much questionable as it was entirely reprehensible - but it works”.
I also remember doing a search and replace of every instance of the word “fuck” with “[fornicate]” when bringing someone new onto a project.
That sharp drop of fucks is when Torvalds took some time off to work on his anger issues
I would have expected the comments to be pretty dry and to the point. Thos eare some interesting stats. 🤣
Most uses of ‘retard’ are in variable names like
B43legacy_OFDMTAB_ADVRETARDbut we also haveThe switch is so retarded that it makes our command/entry abstraction crumble apart.and
we shouldn't need asm for this, but gcc is being retardedMost uses of ‘retard’ are in variable names like
B43legacy_OFDMTAB_ADVRETARDbut we also haveThat explains the sudden drop, with legacy code being removed
Now do in GTA V source code
Would that be more or less, do you think?
