In 1992 we already had CD players that skipped tracks when you press the next-button shortly and seeked through the current track when you kept the button pressed...
Thanks for the nice and long reply. I have to say that I guessed most of the things you said already, the point I was making was more that people who think vim==vi will have troubles too when they have to use the classic version of vi one time. And you seem to agree on that.:-)
Re:VI is everywhere.
on
JOE Hits 3.0
·
· Score: 4, Interesting
You know, when you know how to use vim, you certainly don't automatically know how to use vi. Just try to edit a file on BSD using the default version of vi.
- Backspace key won't work correctly when you want to delete text which was there already before you entered insert mode. - Forget about the delete key, you'll have to quit insert mode and use x. (And for some reason, when you leave insert mode, the cursor magically moves one position to the left) - When you accidentally use your arrow keys at an unexpected moment, your file gets messed up and/or you sometimes automatically leave insert mode.
And well, I can imagine that it'll be even worse on older machines.
Re:Great news, but..
on
JOE Hits 3.0
·
· Score: 2, Insightful
There are more Joe-users than you'd expect. When I started with Linux, about seven years ago, I tried out all editors, and joe was the only sane editor I could find. And once you get hooked, it's hard to switch to something else.
And so far I haven't found any reason to switch to a new editor. Not even joe 3.0. Joe 2.8 is almost completely bug-free, while the version currently available at SourceForge is quite buggy, not very portable anymore, and in fact it just doesn't really have any new feature worth upgrading...
Just on Unix? When you learn to magnetize your hard disk by hand with just the help of a magnet, you can use that knowledge on every computer ever made!
Seriously, knowing about vi is good for emergencies, but I don't want to be bothered by modes and lack of support for all those nice arrow keys on my keyboard.
> There's no reason for me or anyone else to buy Longhorn EVER
Just as there was no reason to buy Windows XP. But still, many people did it. And new computers come with Windows XP, so there is no easy way to avoid it.
Especially when the first applications are written that only run on that version of Windows. (Either XP or Longhorn.)
I'm very sorry to say, just can't resist, but you're just confirming their point here, it seems. Gaim has nothing to do with AOL, and certainly none of the Gaim developers work for AOL.
That's probably what many people thought when watching TV for the first time, but suddenly the computer got invented.
And well, our fore-fore-fore-fathers probably thought the stone they used to make fire was fantastic, and that nobody could ever come up with a better invention, until the lighter was invented a "couple" of years later...
Not that I got any idea about what to invent next, but I'm sure that something will happen soon.;-)
When I heard about the WP5.1 classic mode, I (and especially my mother) was quite interested. So I downloaded a demo from Corel and installed it, and was quite disappointed.
All it can give you is a White-on-Blue screen with WP5.1-like keybindings. But as soon as you open a dialog, you'll have to grab the mouse anyway.
That's the Crusoe chip. These machines have a new chip, the Efficeon. Quoting from the article:
"The new Efficeon TM8600 is designed to improve performance while maintaining the low power consumption required by ultraportable notebooks--such as the 2-pound MM20. Sharp's tests showed that Efficeon delivers about 1.4 times the performance of Crusoe, Hanly says."
I don't know if 1.4 times the Crusoe should be considered fast, but at least it's faster...
I don't know, the only thing I know about Windows Media Player is that it usually attempts to download the necessary codec, and sometimes it even succeeds and gets the file playing.
But for QuickTime on Windows, AFAIK the Apple software is really needed, yes. So actually this is not just a Linux problem. The only problem is that you can download Windows QuickTime straight from the Apple website, while they still probably don't distribute Linux MPlayer modules on their site.
It would be nice to put a little downloader-and-installer for these modules in the fool-proof distributions though.
Yes, but to make them work, you have to install some additional codec files which can't be distributed freely with the operating system because the license does not allow this.
How did you compile the exploit? It didn't work on my machine either, initially, but when I compiled it correctly (-fomit-frame-pointer seems to be important), it did work.
I'm sure there are more with a name like this. Filenames have absolutely nothing to do with "stolen code", and I expect any sane SlashDotter to know and understand that. If they don't, they should also do a very good job at believing everything SCO says.
How often do you *upgrade* your software? I suppose you have to recompile KDE when a new version comes out too, and that probably happens more than once a year.
> Also metadata needs to be created by the user, I aint gonna be entereing data on a keypad on my camera for every photo.
That's why the next version of Microsoft Photo[tm] will send every photo you make to the Microsoft headquarters so they can add the metadata for you.;-)
Slashdot Mirror
In 1992 we already had CD players that skipped tracks when you press the next-button shortly and seeked through the current track when you kept the button pressed...
Thanks for the nice and long reply. I have to say that I guessed most of the things you said already, the point I was making was more that people who think vim==vi will have troubles too when they have to use the classic version of vi one time. And you seem to agree on that. :-)
You know, when you know how to use vim, you certainly don't automatically know how to use vi. Just try to edit a file on BSD using the default version of vi.
- Backspace key won't work correctly when you want to delete text which was there already before you entered insert mode.
- Forget about the delete key, you'll have to quit insert mode and use x. (And for some reason, when you leave insert mode, the cursor magically moves one position to the left)
- When you accidentally use your arrow keys at an unexpected moment, your file gets messed up and/or you sometimes automatically leave insert mode.
And well, I can imagine that it'll be even worse on older machines.
There are more Joe-users than you'd expect. When I started with Linux, about seven years ago, I tried out all editors, and joe was the only sane editor I could find. And once you get hooked, it's hard to switch to something else.
And so far I haven't found any reason to switch to a new editor. Not even joe 3.0. Joe 2.8 is almost completely bug-free, while the version currently available at SourceForge is quite buggy, not very portable anymore, and in fact it just doesn't really have any new feature worth upgrading...
Just on Unix? When you learn to magnetize your hard disk by hand with just the help of a magnet, you can use that knowledge on every computer ever made!
Seriously, knowing about vi is good for emergencies, but I don't want to be bothered by modes and lack of support for all those nice arrow keys on my keyboard.
> There's no reason for me or anyone else to buy Longhorn EVER
Just as there was no reason to buy Windows XP. But still, many people did it. And new computers come with Windows XP, so there is no easy way to avoid it.
Especially when the first applications are written that only run on that version of Windows. (Either XP or Longhorn.)
I'm very sorry to say, just can't resist, but you're just confirming their point here, it seems. Gaim has nothing to do with AOL, and certainly none of the Gaim developers work for AOL.
My iRiver CD/MP3 player supports Ogg Vorbis (beta) and has an FM-tuner. I don't know whether the Flash/HDD iRiver players have a tuner though...
That's probably what many people thought when watching TV for the first time, but suddenly the computer got invented.
;-)
And well, our fore-fore-fore-fathers probably thought the stone they used to make fire was fantastic, and that nobody could ever come up with a better invention, until the lighter was invented a "couple" of years later...
Not that I got any idea about what to invent next, but I'm sure that something will happen soon.
And now I'm wondering how long it will take before the protocol will be changed slightly to lock out this program...
Can't check the link in the article, but I guess it's about this post. (Message-ID: )
They are! Just read the testimonials. :-)
When I heard about the WP5.1 classic mode, I (and especially my mother) was quite interested. So I downloaded a demo from Corel and installed it, and was quite disappointed.
:-(
All it can give you is a White-on-Blue screen with WP5.1-like keybindings. But as soon as you open a dialog, you'll have to grab the mouse anyway.
It could've been a lot better...
You don't know SCO yet, do you? ;-)
That's the Crusoe chip. These machines have a new chip, the Efficeon. Quoting from the article:
"The new Efficeon TM8600 is designed to improve performance while maintaining the low power consumption required by ultraportable notebooks--such as the 2-pound MM20. Sharp's tests showed that Efficeon delivers about 1.4 times the performance of Crusoe, Hanly says."
I don't know if 1.4 times the Crusoe should be considered fast, but at least it's faster...
That must have been a coincidence... At least, I tried the official client to (be it the Macintosh version), and it also didn't work.
I don't know, the only thing I know about Windows Media Player is that it usually attempts to download the necessary codec, and sometimes it even succeeds and gets the file playing.
But for QuickTime on Windows, AFAIK the Apple software is really needed, yes. So actually this is not just a Linux problem. The only problem is that you can download Windows QuickTime straight from the Apple website, while they still probably don't distribute Linux MPlayer modules on their site.
It would be nice to put a little downloader-and-installer for these modules in the fool-proof distributions though.
Yes, but to make them work, you have to install some additional codec files which can't be distributed freely with the operating system because the license does not allow this.
How did you compile the exploit? It didn't work on my machine either, initially, but when I compiled it correctly (-fomit-frame-pointer seems to be important), it did work.
I'm sure there are more with a name like this. Filenames have absolutely nothing to do with "stolen code", and I expect any sane SlashDotter to know and understand that. If they don't, they should also do a very good job at believing everything SCO says.
That hosts file existed in Win9x already. Just the presence of this single file doesn't mean the codebase was "stolen".
;-))
Gee, Windows has a filesystem with directories, I think they copied SysVFS. Maybe SCO can try to sue Microsoft?
So anyway, Windows 2000 having the BSD IP stack is a well known thing. I'm not going to say "fact" because I'm not 100% sure, just 99%.
How often do you *upgrade* your software? I suppose you have to recompile KDE when a new version comes out too, and that probably happens more than once a year.
Yeah, but I don't expect the Microsoft PR-team to talk about that in their anti-OSS campaigns...
> Also metadata needs to be created by the user, I aint gonna be entereing data on a keypad on my camera for every photo.
;-)
That's why the next version of Microsoft Photo[tm] will send every photo you make to the Microsoft headquarters so they can add the metadata for you.
Because most people are stupid enough to click Yes/OK without reading the message at all. That's what they usually do, right?...
But then again, they should've read the message. It's their own fault that evil guys get their credit card numbers.