All Things Microsoft > Microsoft Software
The Vandalisation of Windows
piratePenguin:
--- Quote from: Aloone_Jonez ---
All I know is that Windows isn't as bad as the Linux community say it is or want it to be so I'll [take] what you've said very loosely.
--- End quote ---
Windows is really bad. You mightn't think so, because you don't do 3D rendering (infact, one of my older brothers was asking me about GNU/Linux once. He does do a loada 3D rendering and stuff. On Windows (really the only OS he uses), he mainly uses 3D Studio Max. It doesn't run on GNU/Linux, but Maya, another cool program that he'd be able to use, and that would be fit replace 3D Studio Max, did. And he'd heard that running it on GNU/Linux is somehow faster or otherwise better (can't remember exactly) than running it on Windows (which is interesting. I might look into this, someday.). Needless to say, he's still using Windows and 3D Studio Max. He seems to quite-like 3D Studio Max, and doesn't wanna switch to Maya.), and you've never opened The GIMP, Inkscape, Firefox, GAIM, AmaroK, Konqueror, Glade, monodevelop, KDevelop, KWord and KSpread all in one go.
worker201:
The average user doesn't ever get into the serious Windows memory management problems. Hell, the average Linux user doesn't ever really drive their machine either. But if you do, you'll notice the difference right away. If Windows is rendering something, forget about it doing anything else. Data crunching, same thing. Opening really huge files causes it to flub as well.
Real life experience: I had an Encapsulated PostScript file. It was only about 40MB, but it was 40MB of text, like way over a million lines of code. Using a Windows machine, with 1.5GB RAM and a Pentium4, Adobe Illustrator would not open this file. The amount of memory taken up by Windows combined the amount of memory taken up by Illustrator probably left plenty of room in the memory. But in order for Illustrator to interpret the file, it had to load each and every line separately. Eventually, even 1.5GB RAM fills up, and it starts to swap, but it can't deallocate memory to accomodate moving stuff from RAM to swap. I let it go on like this for over 8 hours before I finally gave up. It just sat there and thrashed the whole time.
So, I put the file on a USBstick and took it home. Loaded it onto my Mac, and attempted to open it in Illustrator. Took about 10 minutes, but it finally came up. And within another 10 minutes, the RAM had been cleared, and I could move around at full speed and get some work done. My Mac has 640MB RAM and a G3 900MHz processor.
Granted, I don't get monster files like this that often. Most people don't. But if you do, you're going to need better memory allocation and deallocation than Windows can provide. Issues that you take for granted, like apps taking forever to minimize/maximize, or thrashing for a few minutes before accepting responses, these things just don't happen in Linux or OSX.
piratePenguin:
--- Quote from: piratePenguin ---Feck that is cool. I wonder is anyone working on bringing this to GNU/Linux...
--- End quote ---
Well it looks like this OLE stuff was one of the original goals of the famous GNOME project.
--- Quote from: http://developer.gnome.org/doc/GGAD/z2.html ---"Gnome" is actually an acronym: GNU Network Object Model Environment. Originally, the project was intended to create a framework for application objects, similar to Microsoft's OLE and COM technologies. However, the scope of the project rapidly expanded; it became clear that substantial groundwork was required before the "network object" part of the name could become reality. The latest development versions of Gnome include an object embedding architecture called Bonobo, and Gnome 1.0 included a fast, light CORBA 2.2 ORB called ORBit.
--- End quote ---
I don't know exactly how this stuff works and what uses it, yet, but I'll eventually find out, and post my findings.
(At least now I have an idea of what that Bonobo Component Browser (under Applications > System Tools) thing is)
EDIT: Yes, I know this stuff wouldn't be consistent accross all GNU/Linux systems, but it would be consistent accross GNOME.
Aloone_Jonez:
--- Quote from: piratePenguin --- Yes, I know this stuff wouldn't be consistent accross all GNU/Linux systems, but it would be consistent accross GNOME.
--- End quote ---
That's just the problem and it will remain the case unless the majority of developers adopt Gtk as a standard or it gets integrated into KDE - I think the two desktop enviroments need to be unified.
One of the great thing about Linux is it offers people lots of choices but this is also one of tis biggest downfalls. Someone might innovate and come up with a new then another developer might think of a better way of doing it but they don't even consider making it compatabile with the other person's system.
piratePenguin:
--- Quote from: Aloone_Jonez ---That's just the problem and it will remain the case unless the majority of developers adopt Gtk as a standard or it gets integrated into KDE - I think the two desktop enviroments need to be unified.
One of the great thing about Linux is it offers people lots of choices but this is also one of tis biggest downfalls. Someone might innovate and come up with a new then another developer might think of a better way of doing it but they don't even consider making it compatabile with the other person's system.
--- End quote ---
I wouldn't like to see KDE and GNOME unified. Each user has their own preference, because the enviornments are different and different people like different things. Certain things are standardized (e.g. by freedesktop.org and they usually obey these standards (*cough*unlike Windows*cough*). Things that haven't been standardized might or might not be standardized in the future, depending on their importance, and how easy/hard they would be to standardize.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version