Haha, they put glibc 2.2 and gcc 2.96 in (both still beta) and you're talking about putting untested software in a stable distribution??? Take your own advice.:)
Did you check out their flash presentation? Please, tell me this is a joke. What is it, the latest in SolarBabies fashion? It looks like a bad 80's movie.
Exactly. What we *really* need is an IMDB for music. A complete database of genres, tempos, production credits, everything you can ever know about an artist, cd, song, whatever.
It would be pure heaven being able to cross-link at that kind of level.
You should have gotten an e-mail with a username and password to get it from a URL at QNX. I signed up pretty much right away, as well, and got my e-mail last week.
Err... isn't the point that Transmeta is supposed to do better when you are using it in real-world situations, where it's idle 90% of the time? So, if you're running a Q3 demo that maxes the CPU out constantly, how, exactly, is that going to show that Toshiba is wrong?
:wq!
Re:GNOME vs KDE Episode 18: Pointlessness
on
KDE Strikes Back
·
· Score: 1
What if LifeKDE sprang into being and created a phone with a steering wheel? Would I be better off?
Isn't that a rotary phone?:)
Personally, I agree with you to some extent, but not to the point of going out of our way to come up with "different" ways of making a UI when you can take advantage of being used to what else is there. I tend to be a command-line only guy, except when booting into X for web browsing that I can't do in lynx. However, I do like the L&F of Helix Gnome, and I've recently played with the KDE2 betas, and I have to say, KDE2 does seem to do some things better than Windows -- somewhat in contrast to what you're saying, consistency is one of it's strong points.
True, File->Save As doesn't make sense for everything, but if you're doing weird stuff like that, can't you still use the kde libs but not use their drawing routines? There *is* a point where a "different" UI that takes some time to learn becomes useful, but for most apps, there's plenty of space before that point.:)
Blender is a good example in your favor (or Lightwave -- I won't use 3DSMax in my example because if we're talking about UI darwinism, 3DSMax is the mutant that should have died years ago). Hell, vi and/or emacs is another. There *are* some interfaces that take a long time to master but are worth the effort.
I don't have any real goal here, just rambling, but I do agree that not every application has to be consistent. But when there's no reason not to be consistent, it's great to see people adhering to the standards. It makes things easier for new users, and for power users. If you can use that already-stored-muscle-memory File->Save As, it cuts down on the learning time.
OpenBSD's code includes all of the user-land utilities that make up a UNIX system as well. Linux is just a kernel. OpenBSD (or any of the *BSDs) are more the equivalent of a Linux "distribution".
You may want to check out the relevant handhelds.org mailing lists. I know I've seen at least one of the PocketLinux developers posting there regularly, and since most of these systems are still at the "getting a reasonable system bootstrapped" level, they're all working together a lot.
I think the difference that makes my PocketPC actually useful is WinCE 3.0's support for handwriting recognition. The thing that kept me going back to my Palm III when I had a WinCE 2.11 machine (took it back and got an iPAQ) is that text entry was *so* much faster with graffitti than the lame on-screen keyboard in WinCE.
But now they have handwriting recognition, and it just "happens" to understand graffitti, and all is well.:)
Despite the fact that there are 2 major contenders for handheld devices (PalmOS and Windows CE), there are at least 4 or 5 different CPU architechtures. Motorola dragonball (68k) on Palms and Visors, and NEC Vxxxx, MIPS, SH3, and ARM chips on WinCE. If you could have the base "OS" handle java, handheld applications will work on all of them without recompiling. That's a definite plus.
Does this mean that WinCE will still be there after it runs down? I'm really looking forward to messing with Linux on my iPAQ, but I don't want to lose WinCE and irreversibly screw up the flash ROM before the flashing stuff stabilizes...
What he meant was that iPAQ is a product line, not just one product (it's like saying "I'm washing dishes with a Whirlpool" when Whirlpool makes washers, dryers, dishwashers, toasters, and whatever.
The iPAQ H3630 and H3650 palmtops run it, but the iPAQ embedded system, mp3 player, and whatever probably can't.
Slashdot Mirror
It would be pure heaven being able to cross-link at that kind of level.
apt-get is not analogous to rpm, it's analogous to dpkg. apt-get is more like rpmfind, except it actually works. :)
Write? What do you mean by wri... ahh, that's that old analog medium of communication. You mean people still use that? :)
Isn't that a rotary phone? :)
Personally, I agree with you to some extent, but not to the point of going out of our way to come up with "different" ways of making a UI when you can take advantage of being used to what else is there. I tend to be a command-line only guy, except when booting into X for web browsing that I can't do in lynx. However, I do like the L&F of Helix Gnome, and I've recently played with the KDE2 betas, and I have to say, KDE2 does seem to do some things better than Windows -- somewhat in contrast to what you're saying, consistency is one of it's strong points.
True, File->Save As doesn't make sense for everything, but if you're doing weird stuff like that, can't you still use the kde libs but not use their drawing routines? There *is* a point where a "different" UI that takes some time to learn becomes useful, but for most apps, there's plenty of space before that point. :)
Blender is a good example in your favor (or Lightwave -- I won't use 3DSMax in my example because if we're talking about UI darwinism, 3DSMax is the mutant that should have died years ago). Hell, vi and/or emacs is another. There *are* some interfaces that take a long time to master but are worth the effort.
I don't have any real goal here, just rambling, but I do agree that not every application has to be consistent. But when there's no reason not to be consistent, it's great to see people adhering to the standards. It makes things easier for new users, and for power users. If you can use that already-stored-muscle-memory File->Save As, it cuts down on the learning time.
C'mon, everyone knows the best quote from that movie is "We must not allow a mine-shaft gap!!" :)
Spoooon!
But now they have handwriting recognition, and it just "happens" to understand graffitti, and all is well.
The iPAQ H3630 and H3650 palmtops run it, but the iPAQ embedded system, mp3 player, and whatever probably can't.