> if you don't feed data straight to the local AGP-bus you're losing time... but it already is under most current Xfree installations (i.e, the driver is using XAA or some other way of directly conversing with the hardware-- like NVIDIA's recent set of drivers)
Yes, and already one such relatively stable element exists-- a single atom of element 114 with 114 protons and 175 neutrons was created that lasted for 30 (!) seconds. This might not be much, but is MUCH greater than lasting for one thousanth of a second like many other elements (z > 100) have.
Theoretically, an atom of element 114 with 114 protons and 183 neutrons is supposed to be perfectly stable (or have a uber-long half life).. 114 and 183 are so called magic numbers where stablity occurs.
> I mean if the scientists create a new element that is extremely reactive
This is unlikely to happen, because many of these elements exist for only 1/1000000000th of a second before they decay into something else. There are a few applicable uses for some of these elements though. Elements 92-94 are used in Nuclear weapons and power, and Element 95 (americium) is used in smoke detectors.
I've found that I can simply get work done in KDE (> 2.0), while I can't get much done in GNOME (> 2.0). It's not a difference in usability, but rather in intuitiveness.
I consistently look around in GNOME 2.x to find how to do things, and often, I can't figure it out. With KDE, at least, there might be lots of interface fuzz to deal with, but I can usually figure it out.
I also find WinXP to be _much_ more intuitive than OSX. I don't think I'm alone either... I see people avoiding OSX boxes at my local library because they just can't figure out how to do basic things with it.
> I think that I would rather have one Linux GUI that is as functional and intuitive as Mac OS X's, instead of three or four that are greatly inferior.
I dunno about that. After using KDE on my Linux boxen, and switching to my Mac running Panther, I always miss many things from KDE.
Both KDE/GNOME can learn things from XP/OSX, while XP/OSX can also learn a few things from KDE/GNOME.
Yup, the GNOME project has used the wm-spec since 2.0, but people on slashdot still seem to think there is some funky GNOME-only WM hint system out there.
One problem is that neither KDE nor GNOME nor all window managers authors seem to have gotten a 100% perfect implementation of the wm-spec hints. Try running Metacity with KDE or kwin in GNOME and see it break in many things. The most close, I think, is kwin's "kwin-iii" branch, which will be in kde 3.2.
> Actually they're all on the wrong frikkin' side, which is very annoying if you run traditional applications as well as GNOME2 applications, or even for your GNOME applications when you first upgrade. IMO that gratuitous change was a very poor HIG decision.
Completely agreed. I wish there was a way to put them into the normal side.
If you are indeed an active WindowMaker developer (which I doubt, judging from your comment), you should know that WindowMaker was never a fork of AS, but rather a complete new window manager. It was made because indeed, there were problems with AS 1.0's codebase. Ultimatly, WindowMaker continuted strong because it had different goals and ideals than AS did.
Note that Afterstep 2.0, just released, is a complete new implementation, and I imagine there are not many problems with it anymore. Of course, I have no idea; I haven't mucked in AfterStep source in a loooong time, I'm a KDE user now:)
> kde/gnome are desktop environments, not window managers. KDE includes KWM window manager, and gnome prefers sawmill, but both will work with most any window manager.
You seem to be stuck back in 2000. KDE 2.0 replaced KWM with kwin, which is completely from the ground up.
GNOME 2.0, similiarly, changed it's perference from Sawfish to Metacity. The two are completley independent.
> Trolls that flame down GNOME in favor of KDE get modded up, while people who complain that Slashdot is full of anti-KDE trolls get modded up *too*.
Slashdot pro-GNOME era: 1997-early 2000 Slashdot KDE-lalaland era: early 2000-late 2001 (all of the slashdot editors were using KDE, and were complaining how Mozilla suX0rs ass compared to Konqueror.. most of the editors eventually switched to OSX) Neutral ground- 2002- 2003
The origional Karamba is practically dead in terms of users and development compared to SuperKaramba. It's webpage is at http://netdragon.sourceforge.net/.
> the fact that it doesn't let you use any c preprocessor macros for things like header include files make it difficult to support cross compilation for a wide variety of platforms without doing additional non-cpp
Huh? Qt lets you use C preprocessor macros in header include files.
> The difference is that on Windows a wxWindows application feels exactly like other native apps, because it _is_ a native app. A Qt app will look almost like a Windows app, but it will be noticable that it isn't using native widgets. This is probably also true on OS X.
Obviously you haven't used Qt in a while...
1. On OSX (and previously on classic MacOS), Qt uses the Apple Appearance Manager.. it feels exactly like Carbon or Cocoa-written apps... 2. On WinXP, Qt uses Visual Styles.. it feels exactly like any wxWindows or MFC-written apps. 3. On X11, of course, there is nothing that is non-native. 4. On Windows versions before XP, it was pathetically easy to to have a Windows-like style, and therefore, Qt emulated it. Keep in mind that Trolltech had five years to perfect it, and perfect is what they did. Try downloading Psi for Windows for example and tell me that it doesn't feel like a Windows app:)
That hasn't been true for quite some time. Certain states, however, will not provide "Indian Residency" status to non-Indian nationals. The states of the south, where the Indian IT industry is located, generally will.
The original laws pertaining to non-Indian immigration to India stemmed from a fear of recolonization of India by the british or other western powers in the 1950's.
1. 2. Windows says that a new modem has been found and proceeds to install it. 3. Create a new connection-- no more seperation between Dialup Networking and regular networking in XP's interface.
This is of course a rough sketch of what happens, but I've found XP to be *much* better than older versions of Windows or MacOSX for automatically installing hardware.
Slashdot Mirror
> if you don't feed data straight to the local AGP-bus you're losing time. .. but it already is under most current Xfree installations (i.e, the driver is using XAA or some other way of directly conversing with the hardware-- like NVIDIA's recent set of drivers)
Yes, and already one such relatively stable element exists-- a single atom of element 114 with 114 protons and 175 neutrons was created that lasted for 30 (!) seconds. This might not be much, but is MUCH greater than lasting for one thousanth of a second like many other elements (z > 100) have.
Theoretically, an atom of element 114 with 114 protons and 183 neutrons is supposed to be perfectly stable (or have a uber-long half life).. 114 and 183 are so called magic numbers where stablity occurs.
> I mean if the scientists create a new element that is extremely reactive
This is unlikely to happen, because many of these elements exist for only 1/1000000000th of a second before they decay into something else. There are a few applicable uses for some of these elements though. Elements 92-94 are used in Nuclear weapons and power, and Element 95 (americium) is used in smoke detectors.
I've found that I can simply get work done in KDE (> 2.0), while I can't get much done in GNOME (> 2.0). It's not a difference in usability, but rather in intuitiveness.
I consistently look around in GNOME 2.x to find how to do things, and often, I can't figure it out. With KDE, at least, there might be lots of interface fuzz to deal with, but I can usually figure it out.
I also find WinXP to be _much_ more intuitive than OSX. I don't think I'm alone either... I see people avoiding OSX boxes at my local library because they just can't figure out how to do basic things with it.
> I think that I would rather have one Linux GUI that is as functional and intuitive as Mac OS X's, instead of three or four that are greatly inferior.
I dunno about that. After using KDE on my Linux boxen, and switching to my Mac running Panther, I always miss many things from KDE.
Both KDE/GNOME can learn things from XP/OSX, while XP/OSX can also learn a few things from KDE/GNOME.
Yup, the GNOME project has used the wm-spec since 2.0, but people on slashdot still seem to think there is some funky GNOME-only WM hint system out there.
One problem is that neither KDE nor GNOME nor all window managers authors seem to have gotten a 100% perfect implementation of the wm-spec hints. Try running Metacity with KDE or kwin in GNOME and see it break in many things. The most close, I think, is kwin's "kwin-iii" branch, which will be in kde 3.2.
> Actually they're all on the wrong frikkin' side, which is very annoying if you run traditional applications as well as GNOME2 applications, or even for your GNOME applications when you first upgrade. IMO that gratuitous change was a very poor HIG decision.
Completely agreed. I wish there was a way to put them into the normal side.
> I really thought everyone knew by now that the GTK file selection dialog will be replaced in GTK 2.4 (gnome 2.6).
People have been saying that since gtk+ 1.2. (and gtk 2.0, gtk 2.2, etc..)
I seriously doubt it'll be done before gtk 3.0
> As an active WindowMaker developer
:)
If you are indeed an active WindowMaker developer (which I doubt, judging from your comment), you should know that WindowMaker was never a fork of AS, but rather a complete new window manager. It was made because indeed, there were problems with AS 1.0's codebase. Ultimatly, WindowMaker continuted strong because it had different goals and ideals than AS did.
Note that Afterstep 2.0, just released, is a complete new implementation, and I imagine there are not many problems with it anymore. Of course, I have no idea; I haven't mucked in AfterStep source in a loooong time, I'm a KDE user now
> kde/gnome are desktop environments, not window managers. KDE includes KWM window manager, and gnome prefers sawmill, but both will work with most any window manager.
You seem to be stuck back in 2000. KDE 2.0 replaced KWM with kwin, which is completely from the ground up.
GNOME 2.0, similiarly, changed it's perference from Sawfish to Metacity. The two are completley independent.
Sawmill itself was the old name for Sawfish.
> Trolls that flame down GNOME in favor of KDE get modded up, while people who complain that Slashdot is full of anti-KDE trolls get modded up *too*.
Slashdot pro-GNOME era: 1997-early 2000
Slashdot KDE-lalaland era: early 2000-late 2001 (all of the slashdot editors were using KDE, and were complaining how Mozilla suX0rs ass compared to Konqueror.. most of the editors eventually switched to OSX)
Neutral ground- 2002- 2003
> 2)Use of the computer is mostly restricted to specific applications in a practically homogenous surronding.
This is usually how all usability research is done.
> People that were spoon fed windows are never going to try out KDE and think its actually MORE usable.
Well, evidently, people in the study considered KDE and XP pretty close.
The origional Karamba is practically dead in terms of users and development compared to SuperKaramba. It's webpage is at http://netdragon.sourceforge.net/.
:)
And it explains a lot too
> this one you site has a sample size of 600 developers
hello? statistically speaking, a sample size of 600 developers is quite enough.
The article was about X Window Toolkits.. What does X11 have to do with win32 or other systems?
> the fact that it doesn't let you use any c preprocessor macros for things like header include files make it difficult to support cross compilation for a wide variety of platforms without doing additional non-cpp
Huh? Qt lets you use C preprocessor macros in header include files.
~ 6.0% ownership of a PRIVATE company is not control at all. Especially when ~65% of the company is owned by employees.
-1.0000 FUD.
> So where can I get safari for AIX or konqueror for Solaris?
KDE runs on both platforms, and as such, khtml browsers such as Konqueror also do.
> Konqueror sucks and Safari is not 100% open source.
It's subjective but I much perfer the rendering of Safari to the rendering firebird/mozilla/Camino.
I think a lot more Linux/UNIX users will also start to prefer Konqueror once all the Safari changes are rolled in.
KHTML is wicked fast, and I've noticed perhaps 3 pages since I made Safari my only-primary browser in May. I was pretty happy with Camino before that.
looks um.... blurrrrrrrrrrrrrrrrrry.
Do you have a LCD or CRT?
> The difference is that on Windows a wxWindows application feels exactly like other native apps, because it _is_ a native app. A Qt app will look almost like a Windows app, but it will be noticable that it isn't using native widgets. This is probably also true on OS X.
:)
Obviously you haven't used Qt in a while...
1. On OSX (and previously on classic MacOS), Qt uses the Apple Appearance Manager.. it feels exactly like Carbon or Cocoa-written apps...
2. On WinXP, Qt uses Visual Styles.. it feels exactly like any wxWindows or MFC-written apps.
3. On X11, of course, there is nothing that is non-native.
4. On Windows versions before XP, it was pathetically easy to to have a Windows-like style, and therefore, Qt emulated it. Keep in mind that Trolltech had five years to perfect it, and perfect is what they did. Try downloading Psi for Windows for example and tell me that it doesn't feel like a Windows app
Actually, if Trolltech goes out of business, Qt would automatically be placed under a BSD-type license.
Qt (for x11 and osx) is already completely GPL'd.
That hasn't been true for quite some time. Certain states, however, will not provide "Indian Residency" status to non-Indian nationals. The states of the south, where the Indian IT industry is located, generally will.
The original laws pertaining to non-Indian immigration to India stemmed from a fear of recolonization of India by the british or other western powers in the 1950's.
Make linux viable? Sun pretty much wishes Linux would die a slow painful death. Their OS strategy is still well entrenched around Solaris.
In WinXP, it's mostly:
1.
2. Windows says that a new modem has been found and proceeds to install it.
3. Create a new connection-- no more seperation between Dialup Networking and regular networking in XP's interface.
This is of course a rough sketch of what happens, but I've found XP to be *much* better than older versions of Windows or MacOSX for automatically installing hardware.