Najmniej popularne cytaty
#7594 Dodano: 09-11-2014 00:10. Głosów: 86
How do you pronounce char?
uint8_t
https://www.reddit.com/r/compsci/comments/2gflyh/how_do_you_pronounce_char/
uint8_t
https://www.reddit.com/r/compsci/comments/2gflyh/how_do_you_pronounce_char/
#7938 Dodano: 03-09-2016 12:27. Głosów: 87
In reality there's little practical need for this as hopefully people aren't going to be setting array.length to 0.5, -1, 1e21 or 'LEMONS'. But this is JavaScript authors we're talking about, so you never know...
http://stackoverflow.com/questions/1822350/what-is-the-javascript-operator-and-how-do-you-use-it
http://stackoverflow.com/questions/1822350/what-is-the-javascript-operator-and-how-do-you-use-it
#378 Dodano: 21-05-2009 09:03. Głosów: 87
-Dokąd matematycy jadą na wczasy?
-Do wód.
-Do wód.
#2782 Dodano: 08-01-2010 00:16. Głosów: 87
Why did the chicken cross the Möbius Strip?
To get to the same side.
To get to the same side.
#481 Dodano: 23-05-2009 14:35. Głosów: 87
<Esse> kebaba każdy lubi eot :>
<manequin> ja lubię, Ty lubisz, a na mocy indukcji reszta ;)
<manequin> ja lubię, Ty lubisz, a na mocy indukcji reszta ;)
#234 Dodano: 20-05-2009 07:19. Głosów: 87
Na egzaminie na uczelnie o profilu informatycznym pytaja sie nowego
kandydata jakie zna komendy jakiegos jezyka programowania.
- Góra, dól, lewo, prawo i fajer...
kandydata jakie zna komendy jakiegos jezyka programowania.
- Góra, dól, lewo, prawo i fajer...
#6893 Dodano: 14-06-2013 12:49. Głosów: 87
A programmer walks into a bar and asks the bartender for 1.00000000000003123939 root beers. Bartender says, I'll have to charge you extra, that's a root beer float. Programmer says, better make it a double.
#1010 Dodano: 21-06-2009 11:54. Głosów: 87
jeżeli e^x to funkcja eksponencjalna to ln(x) powinno się nazywać funkcją impotencjalną
#4404 Dodano: 11-01-2011 23:29. Głosów: 88
zalety modelu kaskadowego
#2141 Dodano: 28-09-2009 11:44. Głosów: 88
Gray's Law of Programming:
'n+1' trivial tasks are expected to be
accomplished in the same time as 'n' tasks.
Logg's Rebuttal to Gray's Law:
'n+1' trivial tasks take twice as long as 'n' trivial tasks.
'n+1' trivial tasks are expected to be
accomplished in the same time as 'n' tasks.
Logg's Rebuttal to Gray's Law:
'n+1' trivial tasks take twice as long as 'n' trivial tasks.
#6756 Dodano: 05-04-2013 00:58. Głosów: 88
"C++ provides a remarkable facility for concealing the trivial details of a program - such as where its bugs are." - David Keppel
#6069 Dodano: 16-06-2012 14:02. Głosów: 88
Z oficjalnej strony ASUSa:
How to update BIOS
Solution
Linux:
1. Please click the Add/Remove software icon under the Setting Tab and follow the instructions to update BIOS.
2. Download AFUDOS from the support site, and then follow the steps below:
2.1 Creating an USB boot device
2.2 Copy afudos.exe and the file of BIOS to USB device, and then plug it to Eee PC
2.3 Input: afudos /i(file name of BIOS)
3. Contact the local service center and ask for help.
How to update BIOS
Solution
Linux:
1. Please click the Add/Remove software icon under the Setting Tab and follow the instructions to update BIOS.
2. Download AFUDOS from the support site, and then follow the steps below:
2.1 Creating an USB boot device
2.2 Copy afudos.exe and the file of BIOS to USB device, and then plug it to Eee PC
2.3 Input: afudos /i(file name of BIOS)
3. Contact the local service center and ask for help.
#3305 Dodano: 05-04-2010 23:01. Głosów: 88
Internet to kolos na glinianych nogach. Prawą jest DNS, lewą SMTP.
#7957 Dodano: 03-09-2016 12:27. Głosów: 89
Q: Where does data written to /dev/null go?
A: It goes into a special data sink in the CPU where it is converted to heat which is vented through the heatsink / fan assembly. This is why CPU cooling is increasingly important; as people get used to faster processors, they become careless with their data and more and more of it ends up in /dev/null, overheating their CPUs. If you delete /dev/null (which effectively disables the CPU data sink) your CPU may run cooler but your system will quickly become constipated with all that excess data and start to behave erratically. If you have a fast network connection you can cool down your CPU by reading data out of /dev/random and sending it off somewhere; however you run the risk of overheating your network connection and / or angering your ISP, as most of the data will end up getting converted to heat by their equipment, but they generally have good cooling, so if you do not overdo it you should be OK.
Paul Robinson adds:
There are other methods. As every good sysadmin knows, it is part of standard practice to send data to the screen of interesting variety to keep all the pixies that make up your picture happy. Screen pixies (commonly mis-typed or re-named as “pixels”) are categorized by the type of hat they wear (red, green or blue) and will hide or appear (thereby showing the color of their hat) whenever they receive a little piece of food. Video cards turn data into pixie-food, and then send them to the pixies — the more expensive the card, the better the food, so the better behaved the pixies are. They also need constant stimulation — this is why screen savers exist.
To take your suggestions further, you could just throw the random data to console, thereby letting the pixies consume it. This causes no heat to be produced at all, keeps the pixies happy and gets rid of your data quite quickly, even if it does make things look a bit messy on your screen.
Incidentally, as an ex-admin of a large ISP who experienced many problems attempting to maintain a stable temperature in a server room, I would strongly discourage people sending the data they do not want out to the network. The fairies who do the packet switching and routing get annoyed by it as well.
// https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/funnies.html
A: It goes into a special data sink in the CPU where it is converted to heat which is vented through the heatsink / fan assembly. This is why CPU cooling is increasingly important; as people get used to faster processors, they become careless with their data and more and more of it ends up in /dev/null, overheating their CPUs. If you delete /dev/null (which effectively disables the CPU data sink) your CPU may run cooler but your system will quickly become constipated with all that excess data and start to behave erratically. If you have a fast network connection you can cool down your CPU by reading data out of /dev/random and sending it off somewhere; however you run the risk of overheating your network connection and / or angering your ISP, as most of the data will end up getting converted to heat by their equipment, but they generally have good cooling, so if you do not overdo it you should be OK.
Paul Robinson adds:
There are other methods. As every good sysadmin knows, it is part of standard practice to send data to the screen of interesting variety to keep all the pixies that make up your picture happy. Screen pixies (commonly mis-typed or re-named as “pixels”) are categorized by the type of hat they wear (red, green or blue) and will hide or appear (thereby showing the color of their hat) whenever they receive a little piece of food. Video cards turn data into pixie-food, and then send them to the pixies — the more expensive the card, the better the food, so the better behaved the pixies are. They also need constant stimulation — this is why screen savers exist.
To take your suggestions further, you could just throw the random data to console, thereby letting the pixies consume it. This causes no heat to be produced at all, keeps the pixies happy and gets rid of your data quite quickly, even if it does make things look a bit messy on your screen.
Incidentally, as an ex-admin of a large ISP who experienced many problems attempting to maintain a stable temperature in a server room, I would strongly discourage people sending the data they do not want out to the network. The fairies who do the packet switching and routing get annoyed by it as well.
// https://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/funnies.html
#7223 Dodano: 05-01-2014 13:14. Głosów: 89
<Master Chief> Using the command line is like driving picture nails with a sledgehammer. It works, but it's stupid.
<dhromed> To accuratize this interesting metaphor: it works in one go and that nail is never coming out again, but it takes more effort to set up, aim and swing-- and if you happen to miss, you're usually in deeper shit.
<dhromed> To accuratize this interesting metaphor: it works in one go and that nail is never coming out again, but it takes more effort to set up, aim and swing-- and if you happen to miss, you're usually in deeper shit.