The most important feature of Longhorn is replacement of the familiar DOS/Windows filesystem with an object database (W0). You will no longer copy files to a floppy or CD-ROM or attach them to an email, because there will be no files. Database records will be copied from one database to another, probably through a.NET server. Large organizations will have their own.NET servers, but everyone else will use one of Microsoft's, a service for which you will pay a fee.
Uh huh. DB based file system != files will be stored on a server (microsoft or otherwise).
A few weeks ago someone posted a link to a KDE fork. The project was supposed to make a new UI that didn't look windowsesque (it looked a bit like OSX). The website had flash animation demos of the "start menu" and "dock". Does anyone know what I'm talking about? I lost the link:(.
Except when you introduce "themes" a la 99% of X users or more and more Windows users (as XP is adopted). This renders Swing more or less useless if you want the application to blend in to the rest of the windowing system.
Bullcrap. The XP theme for Java can simply call Windows metrics/theming apis to do proper theming. A similar thing could be done for GTK etc.
X is based on a networking concept where anyone can access anyone else's screen as a network resource. This leads to multi-threading issues as it is possible for two people to use the same desktop, even same application, simultaneously. As a result, toolkits that have their origins in that environment like GTK and wxwindows have strong multi-threading support not to mention strong networking support
Your conclusion doesn't follow from your premise. The X *protocol* isn't the reason why GTK and wxWindows have strong multithreading support.
This results in the base windowing subsystem's reliance on processes as the fundamental object of execution (as opposed to threads).
What a load of crap. Processes as the fundamental object of execution as opposed to threads? Do you even know what a thread is? Every process in Windows has at least one thread.
So toolkits built upon Windows (MFC, OWL, QT) are able to harness Windows's windowing support in a way that more easily and effectively takes advantage of the features of the subsystem.
Yeah, whatever. QT works the same on Windows as it does on Unix.
Attempting to port one toolkit from its home platform to a foreign platform leads to problems of "look and feel".
Well this doesn't even have anything to do with the networking issues you raised before. It's all about how you draw the UI widgets.
AWT and Swing are prime examples of toolkits that look strange whereever they are used.
Idiot. AWT uses native widgets. And Swing could be made to look practically identical to the native OS. It's all about how you draw the widgets and there's not much stopping Swing from getting it pixel perfect.
Likewise, wxwindows feels funny running on Windows and GTK looks funny. Hell, MFC doesn't even run on X.
What about wxWindows 'feels funny'? And MFC *does* run on X, there are Unix ports. Though, why you would ever want to use a monstrosity like MFC is beyond me.
About 500 years ago, a guy named Martin Luther decided to translate the operating system into German, thus was born the Protestant revolution. The point being, that before this, if you were German and could not read Latin, you had to have a priest translate the words of Money AKA the Operating System.
A Brit named William Tyndale had the same idea, he printed 50 copies of the Operating System *in English*, the establishment was that shocked at this idea, they burnt him at the stake. Probably because they thought the idea of the common people having direct access to the 'holy writ' would lead to them thinking for themselves and having dangerous ideas.
Some evil smelly hippy must have managed to slip into the presentation and take pictures of the secret Microsoft manifesto using SOVIET RUSSIA era spy equipment.
The only photo they didn't manage to take was the one of the map of Western Europe....:P
Slashdot Mirror
The most important feature of Longhorn is replacement of the familiar DOS/Windows filesystem with an object database (W0). You will no longer copy files to a floppy or CD-ROM or attach them to an email, because there will be no files. Database records will be copied from one database to another, probably through a
Uh huh. DB based file system != files will be stored on a server (microsoft or otherwise).
So much for credibility.
I watched TNG all my teenaged years and I looked up to Wesley!
It's so cool that you're a geek in real life!
Cheers!
A few weeks ago someone posted a link to a KDE fork. The project was supposed to make a new UI that didn't look windowsesque (it looked a bit like OSX). The website had flash animation demos of the "start menu" and "dock". Does anyone know what I'm talking about? I lost the link :(.
I read that as "Girls Gone Wild - Spring Break #19 - The one where the shave the turkey".
That wouldn't work.
The segway balances itself by moving forward and backwards. The gyroscopes are only for sensing.
Someone once said: "You're only a victim of something once. After that you're an accomplice".
BTW, learn to understand that you live in a *society*.
It's CPUs not CPU's.
Even Tom's Hardware got it right.
A language doesn't need source; it's a syntax
Uh. And grammar.
Compilers need source, not languages. 'Open Source Language' sounds like more hype to me
Well open source language simply means a langauge where the compiler is OSS. It doesn't make less sense than saying "Perl is open source".
Does it have rapid auto fire like some of those old C64 joysticks?
I don't think so.
Our friend "Willy" is in a lot of trouble.
Damn you Wonka!
http://www.idleworm.com/nws/2002/11/iraq2.shtml
Got to be my all time favourite.
It's the one where homer gets hair and suddenly becomes rich and successful. He has that assistant (Karl) who guides him to success.
It highlights some facets of society and life so well.
Ofcourse it's actually *slower* than using a temporary variable.
Just to carify...
The Mono C# compiler (mcs) is licensed under the GPL, the runtime is licensed under LGPL and the class library is licensed under X11.
Where did I say that Swing is going to solve all cross platform GUI development problems?
So?
Except when you introduce "themes" a la 99% of X users or more and more Windows users (as XP is adopted). This renders Swing more or less useless if you want the application to blend in to the rest of the windowing system.
Bullcrap. The XP theme for Java can simply call Windows metrics/theming apis to do proper theming. A similar thing could be done for GTK etc.
What a load of crap.
X is based on a networking concept where anyone can access anyone else's screen as a network resource. This leads to multi-threading issues as it is possible for two people to use the same desktop, even same application, simultaneously. As a result, toolkits that have their origins in that environment like GTK and wxwindows have strong multi-threading support not to mention strong networking support
Your conclusion doesn't follow from your premise. The X *protocol* isn't the reason why GTK and wxWindows have strong multithreading support.
This results in the base windowing subsystem's reliance on processes as the fundamental object of execution (as opposed to threads).
What a load of crap. Processes as the fundamental object of execution as opposed to threads? Do you even know what a thread is? Every process in Windows has at least one thread.
So toolkits built upon Windows (MFC, OWL, QT) are able to harness Windows's windowing support in a way that more easily and effectively takes advantage of the features of the subsystem.
Yeah, whatever. QT works the same on Windows as it does on Unix.
Attempting to port one toolkit from its home platform to a foreign platform leads to problems of "look and feel".
Well this doesn't even have anything to do with the networking issues you raised before. It's all about how you draw the UI widgets.
AWT and Swing are prime examples of toolkits that look strange whereever they are used.
Idiot. AWT uses native widgets. And Swing could be made to look practically identical to the native OS. It's all about how you draw the widgets and there's not much stopping Swing from getting it pixel perfect.
Likewise, wxwindows feels funny running on Windows and GTK looks funny. Hell, MFC doesn't even run on X.
What about wxWindows 'feels funny'? And MFC *does* run on X, there are Unix ports. Though, why you would ever want to use a monstrosity like MFC is beyond me.
So? What if Microsoft decided that they want to move on an abandon a product? You're screwed there.
At least with OSS you can just contract out someone to continue the work.
Any many OSS projects are paid for directly or indirectly by various business entities anyway.
he may be right in saying that Windows can be described as a Windowing system on top of a kernel
The APIs define windows than the windowing system.
About 500 years ago, a guy named Martin Luther decided to translate the operating system into German, thus was born the Protestant revolution. The point being, that before this, if you were German and could not read Latin, you had to have a priest translate the words of Money AKA the Operating System.
A Brit named William Tyndale had the same idea, he printed 50 copies of the Operating System *in English*, the establishment was that shocked at this idea, they burnt him at the stake. Probably because they thought the idea of the common people having direct access to the 'holy writ' would lead to them thinking for
themselves and having dangerous ideas.
Hmmm...still doesn't make sense.
Comeon, all these dupes are getting ridiculous. All of these articles have been posted to slashdot before!
Some evil smelly hippy must have managed to slip into the presentation and take pictures of the secret Microsoft manifesto using SOVIET RUSSIA era spy equipment.
:P
The only photo they didn't manage to take was the one of the map of Western Europe....
Next year will also be a big year for Mono and DotGnu.