On Linux, I switched from Netscape to Mozilla around M18, I think, and quite frankly although it's taken forever to get there it's now just about the best browser around (for me anyway).
At work the desktops are all NT4, but I use Mozilla there as well, rather than IE. Why?
- Tabs. Can't live without them, and on Windows it means that your taskbar isn't cluttered with 10,000 unidentifiable icons. - Keyboard operation. Open a new tab (Ctrl-T), type your URL, switch back to what you were reading (Ctrl-PageUp) and wait for the new tab to stop spinning. Switch back (Ctrl-PageDown), read it and close it (Ctrl-W). I know you can control IE with the keyboard as well, but to switch windows you have to use Ctrl-Tab, which is an incredible pain if you've got a bunch of windows open. - Speed. It's damn quick.
I just wish they'd build for more platforms... anybody got an Alpha build that doesn't need glibc2.2?
Re:Seems slow, first link text:
on
Tiqit Handheld PC
·
· Score: 2, Informative
First Handheld Computer to Run Windows, Linux or Unix OS
Funny how everyone seems to have forgotten the IBM PC110...
It was 6.25 x 4.5 x 1.3 inches in size, making it only fractionally larger than the eightythree.
Well, considering a 36-processor SGI Challenge with 5GB of RAM would have cost you several multiples of six figures in 1996, I don't really think the comparison's valid...
I'd just like to say one thing: "Quantity != Quality". Just because you read/write comments more than anyone else on/. does not necessarily mean that you're contributing more than anyone else.
The Microsoft LCD AA is ClearType. Many people seem to think that ClearType makes their text look better on a CRT, though... the power of suggestion is remarkable...
Unfortunately, there's a BIT of a DIFFERENCE between rendering for overlay ON video (which means you can take AS long AS you like), and DOING anti-aliasing for a semi-REAL-time user INTERfAcE.
You can be sure that if this is verified a lot of big money will go to work in figuring out ways of making it a useful power source.
More like, a lot of big money (from the petroleum industry) will be invested in making sure that practical applications of any such advances will never see the light of day.
It's not just a language problem either. I get (or used to get before my spam filters went up) technical requests (in English) from Asia as the result of USENET postings and FAQs I wrote.
...and OBVIOUSLY the people spamming you are the same ones who are asking you questions. I mean, it just stands to reason, doesn't it?
Perhaps he should look at the Jargon Filke for a proper definition.
15 Q. What is Foo? You mentioned Foo 1 a 16 moment ago and I -- 17 A. Hmm? 18 Q. Foo, F-o-o. Are you familiar with 19 that name, code name, label, whatever it might be? 20 A. Used a hundred times a day around 21 Microsoft. If I just used it you'd have to read 22 back the quote to tell me Foo is -- 23 It's kind of like a variable to the 24 mathematician. Instead of -- when something -- you 25 know --
Check out the references for that page... "J. A. Van Allen", as in Van Allen belts... it's sobering to remember that we knew so little about space before the probe program.
If you can read Japanese (and if you can't just look at the pictures), how about OpenBlockS?
It's tiny (look at the picture about halfway down the page to get an idea of how small it really is - those are RJ-45 ports), runs Linux, and you can fit it with a HD if you really want to (although I don't see why you would).
I think you're being deliberately misleading - he agreed that AA's MM has reached the point where it is useable and that it was Linus' right to choose to use it, but he still didn't agree with the original decision.
The fact of the matter is that 2.4.12-acX was a high point in MM stability (witness the RH kernels based on the ac patches), whereas the AA MM gave us a half dozen absolutely abysmal releases of something that was supposed to be a stable kernel. Considering that Rik has said that Linus was dropping patches from him meant to stabilise his 2.4 MM, and then turns around and replaces it with something entirely different, it was probably the incident that most contributed to the "discussion" on l-k regarding patch penguins/source management.
Now, try and imagine what might have happened if Linus had accepted Rik's patches in a timely fashion and he'd been allowed to stabilise it. If Linus had wanted to replace it anyway, he could have done it in 2.5.
2.2.17 is recent if you've been using Linux since 1.3.x days... and what does you supposedly being in "embedded research" (can I call you an embedded researcher? Is that some sort of mutant gnome that lives in a box?) have to do with whether or not OSS can be compiled in?
application access was always via direct access to/dev/* nodes, requiring all format conversion and other "fancy" code to reside in the kernel
I'd like to see more info on this - what exactly would require format conversion to be in the kernel? Linus and Alan explicitly rejected such an approach for the v4l code, requiring that all format conversion be done in userspace. I find it hard to believe that the kernel sound code did all conversion between 8/16bit, big-endian/little-endian, etc.
Slashdot Mirror
I use the middle-button feature as well, but I generally prefer not to take my hands off the keyboard, if I can avoid it.
On Linux, I switched from Netscape to Mozilla around M18, I think, and quite frankly although it's taken forever to get there it's now just about the best browser around (for me anyway).
At work the desktops are all NT4, but I use Mozilla there as well, rather than IE. Why?
- Tabs. Can't live without them, and on Windows it means that your taskbar isn't cluttered with 10,000 unidentifiable icons.
- Keyboard operation. Open a new tab (Ctrl-T), type your URL, switch back to what you were reading (Ctrl-PageUp) and wait for the new tab to stop spinning. Switch back (Ctrl-PageDown), read it and close it (Ctrl-W). I know you can control IE with the keyboard as well, but to switch windows you have to use Ctrl-Tab, which is an incredible pain if you've got a bunch of windows open.
- Speed. It's damn quick.
I just wish they'd build for more platforms... anybody got an Alpha build that doesn't need glibc2.2?
First Handheld Computer to Run Windows, Linux or Unix OS
Funny how everyone seems to have forgotten the IBM PC110...
It was 6.25 x 4.5 x 1.3 inches in size, making it only fractionally larger than the eightythree.
Well, considering a 36-processor SGI Challenge with 5GB of RAM would have cost you several multiples of six figures in 1996, I don't really think the comparison's valid...
I'd just like to say one thing: "Quantity != Quality". Just because you read/write comments more than anyone else on /. does not necessarily mean that you're contributing more than anyone else.
The Microsoft LCD AA is ClearType. Many people seem to think that ClearType makes their text look better on a CRT, though... the power of suggestion is remarkable...
Unfortunately, there's a BIT of a DIFFERENCE between rendering for overlay ON video (which means you can take AS long AS you like), and DOING anti-aliasing for a semi-REAL-time user INTERfAcE.
I believe that flourescent lights containing mercury have mostly been phased out now (although I couldn't tell you what it's been replaced with).
You can be sure that if this is verified a lot of big money will go to work in figuring out ways of making it a useful power source.
More like, a lot of big money (from the petroleum industry) will be invested in making sure that practical applications of any such advances will never see the light of day.
I'm glad to see the /. crowd is as open-minded and non-judgemental as ever... *sigh*
It's not just a language problem either. I get (or used to get before my spam filters went up) technical requests (in English) from Asia as the result of USENET postings and FAQs I wrote.
...and OBVIOUSLY the people spamming you are the same ones who are asking you questions. I mean, it just stands to reason, doesn't it?
*sigh*
That's Jargon File, of course.
Perhaps he should look at the Jargon Filke for a proper definition.
15 Q. What is Foo? You mentioned Foo 1 a
16 moment ago and I --
17 A. Hmm?
18 Q. Foo, F-o-o. Are you familiar with
19 that name, code name, label, whatever it might be?
20 A. Used a hundred times a day around
21 Microsoft. If I just used it you'd have to read
22 back the quote to tell me Foo is --
23 It's kind of like a variable to the
24 mathematician. Instead of -- when something -- you
25 know --
ANother ex-VIC20 user... remember, though, that you could only use 3.5KB of that 5KB RAM from BASIC!
Of course, all those ZX-81 users (Timex-Sinclair something-or-other to you 'Merkens) had us beaten soundly in the crappy computer stakes.
Check out the references for that page... "J. A. Van Allen", as in Van Allen belts... it's sobering to remember that we knew so little about space before the probe program.
If you can read Japanese (and if you can't just look at the pictures), how about OpenBlockS?
It's tiny (look at the picture about halfway down the page to get an idea of how small it really is - those are RJ-45 ports), runs Linux, and you can fit it with a HD if you really want to (although I don't see why you would).
I love you more then I can describe
Close, oh so close...
I think you're being deliberately misleading - he agreed that AA's MM has reached the point where it is useable and that it was Linus' right to choose to use it, but he still didn't agree with the original decision.
The fact of the matter is that 2.4.12-acX was a high point in MM stability (witness the RH kernels based on the ac patches), whereas the AA MM gave us a half dozen absolutely abysmal releases of something that was supposed to be a stable kernel. Considering that Rik has said that Linus was dropping patches from him meant to stabilise his 2.4 MM, and then turns around and replaces it with something entirely different, it was probably the incident that most contributed to the "discussion" on l-k regarding patch penguins/source management.
Now, try and imagine what might have happened if Linus had accepted Rik's patches in a timely fashion and he'd been allowed to stabilise it. If Linus had wanted to replace it anyway, he could have done it in 2.5.
Was it? The ac kernels with Rik's MM was a lot more stable than Linus's tree a lot quicker.
Well, AA's MM just plain didn't work for about six releases...
It wasn't really an updated version of the 2.2 code, unless by updated you mean "rewritten from scratch but kind of similar if you squint".
And Rik's MM was a lot better documented than AA's.
2.2.17 is recent if you've been using Linux since 1.3.x days... and what does you supposedly being in "embedded research" (can I call you an embedded researcher? Is that some sort of mutant gnome that lives in a box?) have to do with whether or not OSS can be compiled in?
Thanks for that, it explained the problem nicely.
What on Earth are you talking about? Until recently (as in 2.2.17 or so) I always compiled the sb driver in.
application access was always via direct access to /dev/* nodes, requiring all format conversion and other "fancy" code to reside in the kernel
I'd like to see more info on this - what exactly would require format conversion to be in the kernel? Linus and Alan explicitly rejected such an approach for the v4l code, requiring that all format conversion be done in userspace. I find it hard to believe that the kernel sound code did all conversion between 8/16bit, big-endian/little-endian, etc.