Lol, or get a jacket with lots of pockets?
Heh. I have a summer type jacket (thing is as thin as a T-shirt, so I'm not exactly baking in it) that I wear in spring and fall that has 5 big internal pockets, and 4 external pockets. For winter I have a nice leather jacket with two internal, two external pockets. Everything fits! I.e. my phone and Palm, and when I want to play more music than can fit on my MMC card - a CD mp3 player.
Interesting post, but I want to point out that writing optimized code does not mean going beyond the boundaries of C89/C99. I treat warnings as errors - in fact, 99% of all warnings are quite reasonable - sloppy code or runtime errors. It pisses me off that so many programmers think that just because it (barely) compiles, its worthwhile to put their abortions out into the world. For one thing, there is a high chance of the code chocking on newer versions of or different compilers.
Why are there so many OSS projects out there with incredibly sloppy code that no one bothers to fix?
I personally always compile everything with -Wall --pedantic.
Ahahaha oh man... first I thought.. damn... is this Donnie Ganiere posting? No, just Rockway:-)./me remembers Donnie using the entire IMSA forlang lab to pingflood some CS server...
The problem that I see with that statement is that you immediately equate clock frequency with computational speed. Okay - just because say... I give you a D Flip-Flop that can run at 10Ghz (how uber!), does not mean it has more computational power (rofl) than a D Flip-Flop that maxes out at 10 Mhz. CPU design is important.
If you're going to measure CPU performance by the Hz, might as well measure it by the core voltage, chip size, weight, attractiveness of packaging or computrons.
Well, I don't think they are that simple minded. I would suppose that they only store the changes between the versions... and that they compress everything too. Of course, please realize that I am talkin completely out of my ass... I am just throwing ideas into the air. It is possible that they have some form of a version control system set up, just to minimize redundancy.
Oh man... I *loved* the CD Caddies, ever since my dad got a Toshiba CD-ROM back 10 years go.
In fact, still use it. This SCSI CD-ROM kicks the shit out of most ATAPI ones in terms of reliability and speed. It can read CD-Rs, but not CD-RWs - but thats okay, thats what my CD recorder is for.
After fellow Slashdotters are done, *someone* is going to have to do a lot of explaining to UMICH's IT department... and convincing as well to keep his account around.
Some of us don't have a Cray around to help with the compile-times... or even a distcc cluster devoted just to upgrade that Gentoo box in a reasonable time.
I *like* Gentoo. I *understand* why the Gentoo-people want to go with a BSD-ports-like system. Fine. But for the love of God... if your answer explaining Gentoo's greateness is "recompiling everything from scratch to update", then you didn't understand the question.
That said, it tooks me 13 minutes to bring up my Debian system up to date... which I haven't updated in 3 months now. 10 of those took downloading the 300MB of packages.
"I'll probably get modded down for saying this, but I have Karma to burn..."
The second rule of/. moderation is that you ask to be modded down if you want to be modded up. So if I ask you to mod me up, I'm sarcastically asking to be modded down. Which means I really want to be modded up! Meta-sarcasm!
In fact it is not. Heck it changed a lot from 386->486->586->686.
New instructions. New modes of operations. New registers (not the ones you care about, but the ones I do as a kernel hacker). Have fun doing page-granular TLB flushes on your 80386.
Whats wrong with GAIM? I am serious. It supports AIM, ICQ, MSN, Yahoo, Jabber, Gadu-Gadu, Groupwise, IRC and Napster - has tons of plugins, has txt as well as HTML logging....
Yes, but as I have stated - x86 has become more RISCy since all those extra complex instructions, long unused by any compilers (and that are vestigial remants of the CISC 8086), are
a) deprecated, for backwards compatibility only
b) actually take longer to execute (i.e. that performance increase that made sense using them back in 8086 days isn't there anymore since the chip developers have LONG changed the internal design and maintain these instructions for compatibility only...
The CISC versus RISC battles are largely a non-issue... Today, CISC processors are based on hybrid CISC-RISC architecture. These designs use a decoder to convert CISC instructions into RISC instructions before execution. They are then processed by a RISC core, which performs a few basic instructions very quickly. An example of this would be the AMD Athlon chips, and I suppose Intel does the same as well. RISC processors too are becoming CISCy. Heck, AltiVec added 162 instructions to the G4.
RISC processors generally have more registers, and they are truly GENERAL PURPOSE as opposed to the crap one encounters with IA-32... I still say though that Sparc is the best with its register windows...
But as you might have noted, technical and design superiority is a non-issue when it comes to marketing *sigh*. If it wasn't, then my beloved Alpha AXP wouldn't be dead, ARM wouldn't be confined to the embedded/handheld market and we would all be playing Counter-Strike on our ubiquitous Power boxen.
Lots of Windows vulnerabilites are due to employee incompetence and shoddy design (... see most priviledge escalation exploits on NT). Blaming it on x86 is something new... ^_^
Sure IA-32 is a dirty hack. But BIOS has nothing to do with IA-32 being a dirty hack - if anything, it is a vestigial DOS remnant currently used to a) bring up the hardware (chipset, memory, PCI) b) boot the first 512 bytes of your choice of media. I see nothing wrong with CISC, seriously - the RISC and CISC wars are over and at this point there are no difference to the end user. What do you mean the x86 is designed for handcoded assembly? I hope you realize that handcoded assembly will perform better than compiler-generated on ANY architecture... And if you mean the tons of complex task-specific redundant instructions under IA-32 which are remnants of 8086, then please realize that on both AMD and Intel chips, they are simply there for backwards compatibility - they do not give performance increases anymore. (they actually cause a performance decrease simply because the CPU manufacturers don't care about them since they are obsolete...)
Like it or hate it (I hate it... as a kernel-level developer), IA-32 (well x86-64 now) is to stay. Why? Because there aren't a lot of other cheap architectures around which I can build sub $200 machines. Sure, Apple has damn cheap PPC quality laptops (compared to other laptops) - but I can't build a sub $500 desktop around a non-obsolete chip.
My predictions are that in 10 years there will be 3 non-marginal architectures - some incarnation of IA-32 or x86-64, some incarnation of ARM and some incarnation of Power. Unless something radical happens, I don't expect Power to profilerate further than mainframes and (sorry) niche computers.
Okay... XMMS? If you want iTunes-like automatic song ranking and thus "weighted" randomized selection, there is a pluggin floating around for that somewhere. Check apt-cache:-).
Of course, why make ONLY a jukebox? Make a PVR box with MythTV, or your other favorite OSS PVR UI (like Freevo, or something...), and set it up with a CIR receiver - Bam! You have the envy of all your friends:-P.
Re:Does it work properly/completely with Opera yet
on
Gmail Adds Features
·
· Score: 1
Thing is, its not a FireFox fault. Its the classic case of DLL (whoops! DSO) hell present in some Linux distributions *cough* SuSE *cough* where some ancient moz libraries installed conflict with new ones. Meh, use Debian or Slackware - never had an issue.
... I remember playing WAVs on me 16mhz PS/2 m55 using that Windows driver, which took me 3 hours at my public library's computers to find.... Quality was crap, but it was novel - impressed the hell out of me before I went back to listening to 192kbps MP3s on my Pentium Pro.
Simple (your idea is put to use by GIMP to export to html) - but it doesn't work as expected on way to many browsers... For example Firefox didn't display's GIMP's HTML export correctly.
Another problem is that you wind up with a giant file, which takes forever to download and tends to expose a lot of bugs in browsers, since they don't expect large files.
I made a variation on this idea where instead of using tables+gif I used CSS. Essentially I created bazilions of 1px-by-1px regions... Here is a proof-of-concept program that will convert any image supported by ImageMagick into CSS+XHTML - http://alumni.imsa.edu/~andyw/projects/image2xhtml.html Here is a result of a conversion of a tiny image - http://alumni.imsa.edu/~andyw/projects/me.html. This is as bad (worse actually) than tables, since the output file becomes astronomical in size even for medium-sized pix.
Slashdot Mirror
Lol, or get a jacket with lots of pockets? Heh. I have a summer type jacket (thing is as thin as a T-shirt, so I'm not exactly baking in it) that I wear in spring and fall that has 5 big internal pockets, and 4 external pockets. For winter I have a nice leather jacket with two internal, two external pockets. Everything fits! I.e. my phone and Palm, and when I want to play more music than can fit on my MMC card - a CD mp3 player.
Interesting post, but I want to point out that writing optimized code does not mean going beyond the boundaries of C89/C99. I treat warnings as errors - in fact, 99% of all warnings are quite reasonable - sloppy code or runtime errors. It pisses me off that so many programmers think that just because it (barely) compiles, its worthwhile to put their abortions out into the world. For one thing, there is a high chance of the code chocking on newer versions of or different compilers.
Why are there so many OSS projects out there with incredibly sloppy code that no one bothers to fix?
I personally always compile everything with -Wall --pedantic.
Ahahaha oh man... first I thought.. damn... is this Donnie Ganiere posting? No, just Rockway :-). /me remembers Donnie using the entire IMSA forlang lab to pingflood some CS server...
The problem that I see with that statement is that you immediately equate clock frequency with computational speed. Okay - just because say... I give you a D Flip-Flop that can run at 10Ghz (how uber!), does not mean it has more computational power (rofl) than a D Flip-Flop that maxes out at 10 Mhz. CPU design is important. If you're going to measure CPU performance by the Hz, might as well measure it by the core voltage, chip size, weight, attractiveness of packaging or computrons.
Well, I don't think they are that simple minded. I would suppose that they only store the changes between the versions... and that they compress everything too. Of course, please realize that I am talkin completely out of my ass... I am just throwing ideas into the air. It is possible that they have some form of a version control system set up, just to minimize redundancy.
IE /already/ does that. FYI. I just find it plain annoying. I just think of it as a bandwith-unfriendly 404 page, nothing more. Go Google.
It may improve on the UI and usability (like Crazybrowser did), but you are still using the IE engine to render your webpages.
How secure is that?
Your ideas are intriguing to me and I wish to subscribe to your newsletter.
-Sincerely, andreyw
This is Kristopher Kubicki's article... who is in UIC's ACM club, the meetings of which I should get around to attending.
No, he had an i486-DX2 clocked at 66Mhz.
/ re cord/127.htm
http://www.cpu-collector.com/menu/searchresults
Anyways I posted this just in case you thought he was jokeing. I
Oh man... I *loved* the CD Caddies, ever since my dad got a Toshiba CD-ROM back 10 years go.
In fact, still use it. This SCSI CD-ROM kicks the shit out of most ATAPI ones in terms of reliability and speed. It can read CD-Rs, but not CD-RWs - but thats okay, thats what my CD recorder is for.
Heck, I wished I had caddies for all my cds.
You have a point there - Of course it will be a fake voice, since Joyce would never, ever call you :).
After fellow Slashdotters are done, *someone* is going to have to do a lot of explaining to UMICH's IT department... and convincing as well to keep his account around.
Cats land on their feet. Toast lands jellyside down. A cat glued to some jelly toast will hover in quantum indecision.
Some of us don't have a Cray around to help with the compile-times... or even a distcc cluster devoted just to upgrade that Gentoo box in a reasonable time.
I *like* Gentoo. I *understand* why the Gentoo-people want to go with a BSD-ports-like system. Fine. But for the love of God... if your answer explaining Gentoo's greateness is "recompiling everything from scratch to update", then you didn't understand the question.
That said, it tooks me 13 minutes to bring up my Debian system up to date... which I haven't updated in 3 months now. 10 of those took downloading the 300MB of packages.
"I'll probably get modded down for saying this, but I have Karma to burn..."
/. moderation is that you ask to be modded down if you want to be modded up. So if I ask you to mod me up, I'm sarcastically asking to be modded down. Which means I really want to be modded up! Meta-sarcasm!
The second rule of
In fact it is not. Heck it changed a lot from 386->486->586->686.
New instructions. New modes of operations. New registers (not the ones you care about, but the ones I do as a kernel hacker). Have fun doing page-granular TLB flushes on your 80386.
Whats wrong with GAIM? I am serious. It supports AIM, ICQ, MSN, Yahoo, Jabber, Gadu-Gadu, Groupwise, IRC and Napster - has tons of plugins, has txt as well as HTML logging....
No adverts....
And its GPL.
Its pretty impressive considering it was designed back in the days when the SOVIETS existed.
Makes you think what kind of advanced computers they have now that no one will find about for another 10+ years...
Yes, but as I have stated - x86 has become more RISCy since all those extra complex instructions, long unused by any compilers (and that are vestigial remants of the CISC 8086), are a) deprecated, for backwards compatibility only b) actually take longer to execute (i.e. that performance increase that made sense using them back in 8086 days isn't there anymore since the chip developers have LONG changed the internal design and maintain these instructions for compatibility only...
The CISC versus RISC battles are largely a non-issue... Today, CISC processors are based on hybrid CISC-RISC architecture. These designs use a decoder to convert CISC instructions into RISC instructions before execution. They are then processed by a RISC core, which performs a few basic instructions very quickly. An example of this would be the AMD Athlon chips, and I suppose Intel does the same as well. RISC processors too are becoming CISCy. Heck, AltiVec added 162 instructions to the G4.
RISC processors generally have more registers, and they are truly GENERAL PURPOSE as opposed to the crap one encounters with IA-32... I still say though that Sparc is the best with its register windows...
But as you might have noted, technical and design superiority is a non-issue when it comes to marketing *sigh*. If it wasn't, then my beloved Alpha AXP wouldn't be dead, ARM wouldn't be confined to the embedded/handheld market and we would all be playing Counter-Strike on our ubiquitous Power boxen.
Lots of Windows vulnerabilites are due to employee incompetence and shoddy design (... see most priviledge escalation exploits on NT). Blaming it on x86 is something new... ^_^
Sure IA-32 is a dirty hack. But BIOS has nothing to do with IA-32 being a dirty hack - if anything, it is a vestigial DOS remnant currently used to a) bring up the hardware (chipset, memory, PCI) b) boot the first 512 bytes of your choice of media. I see nothing wrong with CISC, seriously - the RISC and CISC wars are over and at this point there are no difference to the end user. What do you mean the x86 is designed for handcoded assembly? I hope you realize that handcoded assembly will perform better than compiler-generated on ANY architecture... And if you mean the tons of complex task-specific redundant instructions under IA-32 which are remnants of 8086, then please realize that on both AMD and Intel chips, they are simply there for backwards compatibility - they do not give performance increases anymore. (they actually cause a performance decrease simply because the CPU manufacturers don't care about them since they are obsolete...)
Like it or hate it (I hate it... as a kernel-level developer), IA-32 (well x86-64 now) is to stay. Why? Because there aren't a lot of other cheap architectures around which I can build sub $200 machines. Sure, Apple has damn cheap PPC quality laptops (compared to other laptops) - but I can't build a sub $500 desktop around a non-obsolete chip.
My predictions are that in 10 years there will be 3 non-marginal architectures - some incarnation of IA-32 or x86-64, some incarnation of ARM and some incarnation of Power. Unless something radical happens, I don't expect Power to profilerate further than mainframes and (sorry) niche computers.
Okay... XMMS? If you want iTunes-like automatic song ranking and thus "weighted" randomized selection, there is a pluggin floating around for that somewhere. Check apt-cache :-).
:-P.
Of course, why make ONLY a jukebox? Make a PVR box with MythTV, or your other favorite OSS PVR UI (like Freevo, or something...), and set it up with a CIR receiver - Bam! You have the envy of all your friends
Thing is, its not a FireFox fault. Its the classic case of DLL (whoops! DSO) hell present in some Linux distributions *cough* SuSE *cough* where some ancient moz libraries installed conflict with new ones. Meh, use Debian or Slackware - never had an issue.
... I remember playing WAVs on me 16mhz PS/2 m55 using that Windows driver, which took me 3 hours at my public library's computers to find.... Quality was crap, but it was novel - impressed the hell out of me before I went back to listening to 192kbps MP3s on my Pentium Pro.
Simple (your idea is put to use by GIMP to export to html) - but it doesn't work as expected on way to many browsers... For example Firefox didn't display's GIMP's HTML export correctly.
l .html Here is a result of a conversion of a tiny image - http://alumni.imsa.edu/~andyw/projects/me.html. This is as bad (worse actually) than tables, since the output file becomes astronomical in size even for medium-sized pix.
Another problem is that you wind up with a giant file, which takes forever to download and tends to expose a lot of bugs in browsers, since they don't expect large files.
I made a variation on this idea where instead of using tables+gif I used CSS. Essentially I created bazilions of 1px-by-1px regions... Here is a proof-of-concept program that will convert any image supported by ImageMagick into CSS+XHTML - http://alumni.imsa.edu/~andyw/projects/image2xhtm