USB (seems to) work on the mac, but the most popular OS that supports USB has, well, dubious reliability. Mice and keyboards don't gain much, if anything, by using USB vs. PS/2 ports. I've even heard horror stories from USB periphs in Be, which has official mice and keyboards.
Don't know about BIOS-level support, but the drivers need to give us about as much flak as the current keyboard.INFs before I see this as a real replacement to my PS/2 ports.
For a PC to be truly legacy free what must you get rid of?
[could_be_dead_wrong] AFAIK....
ISA PS/2 FDD serial and parallel ports
...and anything that uses an IRQ.
once we get rid of these, we might get a performance gain on non-legacy busses, etc.
the website states that "reasonable upgrades" won't break office, but if the case and a modem are the only parts in common with a before and after of a massive upgrade, then it'll break, definitely.
The connection-req'd editions will be [initally?] released in "high-piracy" markets, e.g. China, Brazil, student discounted versions.
the trouble with #3 (and other non-popular projects) is that--
they'll be shoved aside for more popular things that the coder wanted to put in anyway.
I suggest that we get a GNOME and KDE accesibility libraries (or something to that effect) in order to get these things out to everybody. this will help new projects out as
- the development team won't have to deal hwith another thing taht should be done
- a standard "look and feel" that these libraries would go a long way in order to migrate Win9x/Office97/IE4 users (that is, of course, if anybody wants people like me in the linux club...
dagnabbit, there's no red wavy lines and F7 doesn't do anything. excuse my typos.
The thing that I like about GUIs is that it is possible to give clues as to what the user can do, e.g. tooltips, underlined words that allow alt key shortcuts, etc. this allows for fast navigation--well, at least as fast as the increased resource strain allows. DOS, and therefore Windows, came from this line of thinking that things need to be navigable and fully usable with a keyboard--WP for DOS users didn't have a mouse to use, generally. I can press win, u, s, Enter to shut down the computer, and I found this out by _simply looking around_, not poring over manpages in my free time.
One of the things I liked when IE4 came out was the address bar in the local navigation--I can type the damn thing in myself if I want to.
One thing that the CLI could use to help out would be a line somewhere to show the arguments that need passing. the TI-89 has a basic help built in--maybe that could help as I wouldn't have to consult a manpage every time I wanted to do something but forgot something. on the other hand, this would annoy anybody that knows the commands like the back of their hand.
Red Herring's latest issue has a substancial bit in it on Tidal Wave's Orecchio, a dongle that sits around the ear like a hearing aid. their site is at www.thinkyourmail.com , but they don't have much there now. Probably best to wait for the RH issue to come out on the web.
The trouble with most apps is that there is little compromise b/t blindly going around in the command line and having nice, user-friendly toolbars and pull-down menus. Yes, command line power is valuable, but the steep learning curve and lack of hints that keep you from screwing up aren't there. A rudimentary windowing system _looks_ good, but one has to use the mouse for _everything_. one thing that Windows has that many X11-type software doesn't is hints for keyboard navigation, one thing that seems to be the last worked on, reducing the Power of Linux to a primitive Mac UI. If nothing else, Windows' insistence on backward compatibility allows for 99.99% navigation with the keyboard, so that I can shutdown with , u, s, . short of modifying some.rc file somewhere (which is beyond my current level), I am tied to the mouse beside my keyboard.
Tangent and bait: "I don't read books any more..."
on
Review:Open Sources
·
· Score: 1
palmtops aside (which might come into play later) it's difficult to move e-text around in the real world. I'd rather not have to take my Newton into the bathroom or to the beach or to...wherever. even an easy chair can be problematic if the screen glare/LCD brightness/is not optimal.
Slashdot Mirror
USB (seems to) work on the mac, but the most popular OS that supports USB has, well, dubious reliability. Mice and keyboards don't gain much, if anything, by using USB vs. PS/2 ports. I've even heard horror stories from USB periphs in Be, which has official mice and keyboards.
.INFs before I see this as a real replacement to my PS/2 ports.
Don't know about BIOS-level support, but the drivers need to give us about as much flak as the current keyboard
For a PC to be truly legacy free what must you get rid of?
[could_be_dead_wrong]
AFAIK....
ISA
PS/2
FDD
serial and parallel ports
...and anything that uses an IRQ.
once we get rid of these, we might get a performance gain on non-legacy busses, etc.
[/could_be_dead_wrong]
Anybody know more than I do?
the website states that "reasonable upgrades" won't break office, but if the case and a modem are the only parts in common with a before and after of a massive upgrade, then it'll break, definitely.
The connection-req'd editions will be [initally?] released in "high-piracy" markets, e.g. China, Brazil, student discounted versions.
Hurry up with Koffice already!
the trouble with #3 (and other non-popular projects) is that--
they'll be shoved aside for more popular things that the coder wanted to put in anyway.
I suggest that we get a GNOME and KDE accesibility libraries (or something to that effect) in order to get these things out to everybody. this will help new projects out as
- the development team won't have to deal hwith another thing taht should be done
- a standard "look and feel" that these libraries would go a long way in order to migrate Win9x/Office97/IE4 users (that is, of course, if anybody wants people like me in the linux club...
dagnabbit, there's no red wavy lines and F7 doesn't do anything. excuse my typos.
BTW, what does the c statement at the end mean?
The thing that I like about GUIs is that it is possible to give clues as to what the user can do, e.g. tooltips, underlined words that allow alt key shortcuts, etc. this allows for fast navigation--well, at least as fast as the increased resource strain allows. DOS, and therefore Windows, came from this line of thinking that things need to be navigable and fully usable with a keyboard--WP for DOS users didn't have a mouse to use, generally. I can press win, u, s, Enter to shut down the computer, and I found this out by _simply looking around_, not poring over manpages in my free time.
One of the things I liked when IE4 came out was the address bar in the local navigation--I can type the damn thing in myself if I want to.
One thing that the CLI could use to help out would be a line somewhere to show the arguments that need passing. the TI-89 has a basic help built in--maybe that could help as I wouldn't have to consult a manpage every time I wanted to do something but forgot something. on the other hand, this would annoy anybody that knows the commands like the back of their hand.
Red Herring's latest issue has a substancial bit in it on Tidal Wave's Orecchio, a dongle that sits around the ear like a hearing aid. their site is at www.thinkyourmail.com , but they don't have much there now. Probably best to wait for the RH issue to come out on the web.
The trouble with most apps is that there is little compromise b/t blindly going around in the command line and having nice, user-friendly toolbars and pull-down menus. Yes, command line power is valuable, but the steep learning curve and lack of hints that keep you from screwing up aren't there. A rudimentary windowing system _looks_ good, but one has to use the mouse for _everything_. one thing that Windows has that many X11-type software doesn't is hints for keyboard navigation, one thing that seems to be the last worked on, reducing the Power of Linux to a primitive Mac UI. If nothing else, Windows' insistence on backward compatibility allows for 99.99% navigation with the keyboard, so that I can shutdown with , u, s, . short of modifying some .rc file somewhere (which is beyond my current level), I am tied to the mouse beside my keyboard.
palmtops aside (which might come into play later) it's difficult to move e-text around in the real world. I'd rather not have to take my Newton into the bathroom or to the beach or to...wherever. even an easy chair can be problematic if the screen glare/LCD brightness/is not optimal.