One thing that google has done is to make web applications a legitimate thing for good programmers to do. Up until now, web applications have been written by imbecile teenagers because no real programmer would touch them with a ten foot pole.
Google has raised the quality of the user interface of web applications by several orders of magnitude, and they did this by having real developers and real user interface designers do them, rather than elite php haxors.
When other companies figure this out it will among other things cause web applications to become faster.
Many projects currently under GPL2-or-later will probably just upgrade the whole thing to GPL3-or-later. If they like GPL3, that is. If they don't, then they'll probably just not take any GPL3 code at all.
I am in possession of another mysterious media, said to be more than twenty years old. It is a black disk, perhaps 50cm diameter, made of a mysterious material that I have not been able to identify. The disk is light and has a small (~5 mm) hole in the middle. It has a spiral shaped groove covering the entire disk with and what looks like 'bands" where the spiral groove is cut deeper. In the outermost and the innermost bands it looks like there is longer between the windings.
Any idea what this could be? Could it be a media left behind by aliens trying to communicate with us?
The point is that using Yes/No forces the user to read the entire dialog. By using a verb, the user can in many cases read just the button.
For example an alert saying
"Are you sure you want to delete [foo]"
[yes] [no]
requires the user to parse a long sentence, then locate the right response by scanning *both* the yes and the no button. Contrast with the correct way, where the user sees something like this:
which is enough to make the decision to push delete, in particular if the delete button is located in the lower right corner along with all the other affirmative buttons.
KDE does not get this and they probably never will.
At his presentation at the Desktop Developers Conference in Ottawa, the Inkscape guy said that unlike previous versions, this one should be very stable. YMMV.
It's a fact that graphics cards for many years have required interrupts and DMA to be programmed well, and that is just not something you can do from userspace. Several other things that X does today are at least dubious to do in userspace.
A good graphics driver these days need some sort of help from the kernel, but moving the *entire* driver into ring 0 is indeed a bad idea. The things that can safely and sanely be done from userspace should be.
It's ironic that making the button order a preference is something the GTK+ developers want because GTK+ has a win32 backend. See
http://bugzilla.gnome.org/show_bug.cgi?id=74669
The bug has been open for ages. If somebody would actually come up with the simple patch needed, people could have a gconf preference for the button order.
It makes absolutely *no* sense to fork GNOME for this reason.
I think it is worth pointing out that back in 1998 The Open Group (now known as X.org) changed the licensing of X R6.4 to be proprietary, and only backed down when XFree86 and David Dawes explained exactly what they could with their proprietary server.
XFree86 is the reason we have a free software X server today. It is quite ironic that slashdot is now hating XFree86 because of licensing.
Slashdot Mirror
So, does it explode before or after the rootkit kicks in?
I have one of those. Now if only I could find it ...
Reminds me of a joke from the cold war:
- Mr. President! The Russians have landed on Mars and they are busy are
painting it red!
- Don't worry. We'll just wait until they finish; then we'll write "Drink
Coca-Cola" in big white letters on it.
One thing that google has done is to make web applications a legitimate thing for good programmers to do. Up until now, web applications have been written by imbecile teenagers because no real programmer would touch them with a ten foot pole.
Google has raised the quality of the user interface of web applications by several orders of magnitude, and they did this by having real developers and real user interface designers do them, rather than elite php haxors.
When other companies figure this out it will among other things cause web applications to become faster.
Many projects currently under GPL2-or-later will probably just upgrade the whole thing to GPL3-or-later. If they like GPL3, that is. If they don't, then they'll probably just not take any GPL3 code at all.
Because in Korea, only old people use Google.
> Now, guess who created exa. That's right. A
> Trolltech employee who they hired to work on X.
Exa is nothing more than a sed job on kaa which was created by Keith Packard, Anders Carlsson and Eric Anholt.
I am in possession of another mysterious media, said to be more than twenty years old. It is a black disk, perhaps 50cm diameter, made of a mysterious material that I have not been able to identify. The disk is light and has a small (~5 mm) hole in the middle. It has a spiral shaped groove covering the entire disk with and what looks like 'bands" where the spiral groove is cut deeper. In the outermost and the innermost bands it looks like there is longer between the windings.
Any idea what this could be? Could it be a media left behind by aliens trying to communicate with us?
GNOME doesn't assume you are unable to read dialogs. It assumes you have a life.
The point is that using Yes/No forces the user to read the entire dialog. By using a verb, the user can in many cases read just the button.
For example an alert saying
"Are you sure you want to delete [foo]"
[yes] [no]
requires the user to parse a long sentence, then locate the right response by scanning *both* the yes and the no button. Contrast with the correct way, where the user sees something like this:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[xxxxx][delete]
which is enough to make the decision to push delete, in particular if the delete button is located in the lower right corner along with all the other affirmative buttons.
KDE does not get this and they probably never will.
At his presentation at the Desktop Developers Conference in Ottawa, the Inkscape guy said that unlike previous versions, this one should be very stable. YMMV.
"If I have not seen as far as others, it is because I was standing in the footprints of giants"
> Moving the drivers into the kernel is crazy.
It's a fact that graphics cards for many years have required interrupts and DMA to be programmed well, and that is just not something you can do from userspace. Several other things that X does today are at least dubious to do in userspace.
A good graphics driver these days need some sort of help from the kernel, but moving the *entire* driver into ring 0 is indeed a bad idea. The things that can safely and sanely be done from userspace should be.
... I already can't wait for "Revenge of the Seveth".
> What about the rest of the planet?
What, BOTH of them?
I read somewhere that he only called it 'Apple' to get before 'Atari' in the phone book.
> I am of the opinion that linux is ugly, ...
Try 2.6.9-pre1. It is much prettier.
> of ugly effects as the toolkit takes it's sweet time handling the expose events.
Please explain why this doesn't happen on xfce. It uses the same toolkit.
> You must be new here... Step 3 is Profit!
Normally yes, but not when Step 1 is "Buy a Mac".
It's ironic that making the button order a preference is something the GTK+ developers want because GTK+ has a win32 backend. See
http://bugzilla.gnome.org/show_bug.cgi?id=74669
The bug has been open for ages. If somebody would actually come up with the simple patch needed, people could have a gconf preference for the button order.
It makes absolutely *no* sense to fork GNOME for this reason.
> And don't even ask about Metafont...
Why not? It uses the same scheme, only the series converges to e, not pi.
I think it is worth pointing out that back in 1998 The Open Group (now known as X.org) changed the licensing of X R6.4 to be proprietary, and only backed down when XFree86 and David Dawes explained exactly what they could with their proprietary server.
XFree86 is the reason we have a free software X server today. It is quite ironic that slashdot is now hating XFree86 because of licensing.
> Here I sit back, reading slashdot ...
And there's your problem.
No, that was David Wexelblatt.
David Dawes was the one who explained to The Open Group what they could with their X server when they tried to make it non-free.
In your face, Andromeda!