Or even more shocking... what if they FAKED the failed Mars missions... the missions to mars really were successful, and were powered by secret Scientology paraphernalia and immortality bracelets (not to mention the coral calcium)!
What if they FAKED the FAKED moon landing?!
Or maybe I need to lay off the special brownies...
CORBA fulfills essentially what you describe (not sure about #4). However, the CORBA spec is fairly large and baroque, so you are going to eat some overhead in complexity (not necessarily performance!) if you choose CORBA.
RMI is also a nice spec. Contrary to popular belief RMI is not a wire protocol but simply a spec for an RPC interface. The standard implementation uses a specific wire protocol and is tied to Java. However, RMI/IIOP also comes standard and is transparently interoperable with CORBA. I'm sure if you wanted to you could write your own transport implementation.
XML-RPC and SOAP are not really OO RPC mechanisms (despite SOAP containing the word "object" in it). SOAP is a bloated compromise spec created by committee by a few large players in the industry to satisfy all their requirements, and hence does not really enforce any sort of object or typing system. Already I see people addled by XML-think outright proposing this protocols. If it fits your project go for it, but XML is not the panacea people think it is.
I just finished 9:05 (or at least i THINK i finished it). Was this as short as I thought it was (like...ridiculously short)?? Or did I miss something?? I don't get it.
Same with Shrapnel. Um, I think I finished it, but it was so damn short I'm not sure. Maybe I did something wrong.
The ban only applies to feeding that excess remains to the SAME ANIMAL. I have it on good word from a soon-to-be-vet who just attended a lecture on that exact topic that "mad cow disease" first entered the cow population through SHEEP remains (scrapies). So maybe you can't feed the cow feed back to cows, but you can feed it to chickens or other animals.
So guess what? You think you are safe by just not eating beef? Think again. America has to thank large corporate agribusiness to whom you have given your tacit approval for all these years. (Oh yeah, and keep giving money to Republicans because they're for "farmers" right?....right?)
Me...i'm a vegetarian so I feel a bit safer, BUT the jury is still out on what prions can effect, so it might turn out milk and cheese are also at risk. Who the fuck knows - we allowed this to happen.
They are thinking: "Now that we have already sold the man who has a penile inferiority complex a grotesquely and outlandishly large boutique vehicle which serves no purpose, what can we sell him for christmas? I KNOW BIG BRIGHT FUCKING LIGHTS BECAUSE BEING AN ASSHOLE IS MANLY!"
Wow, I can just feel our roads becoming safer (for those entombed in SUV tanks with 1 foot thick lead walls and searchlights for headlights.. everybody else is screwed).
I don't doubt that our eyes are less responsive to red and blue (I already knew that) but isn't the example sort of contrived? I mean, if I showed you a completely RED square, and then proceeded to remove both the RED and, say, BLUE color components, would that be proving anything? Obviously removing all the RED in a primarily RED picture is going to have more of an affect than removing any other color. The question is was the blue component in that picture significant to begin with (and in reverse deduction, is blue in the environment significant to begin with).
when you are speaking about gnome having catched up to kde, you should not forget the backend.
while the original gtk+ core is c code, which gives good performance but makes developing bigger apps painful, the now really mature gtk-- library is a modern c++ toolkit. it does not depend on language extensions and preprocessors like moc, but rather uses modern c++ language features and programming techniques to fulfill the same requirements.
that's why i think gnome is the better desktop from a programming point of view, and that just because of this will continue to develop faster than kde (as it did in the recent time).
So which GTK is the real GTK? Is one an "old" deprecated version and one "new", or just different bindings to the same thing? Do the widgets act and look alike? Does the gtk-- have C backwards compatibility or does gtk+ have to be used? What sort of consistency guarantee is there accross apps then? It's interesting to hear that there is a C++ version, but I wonder how this is going to affect consistency. Is there a project-wide declaration to only build new stuff on gtk--? If not then I think there should be. There are enough toolkits to begin with, without having to worry about different versions for different languages, etc.
I really anticipate seeing how gtk-- will match up against Qt, if it is really as mature and modern as you say. Should be interesting.
"The biggest concern for me is that it more or less forces me to program in C++."
We are not talking about programmers. We are talking about users. This USERLinux, specifically aimed at users with open and acknowledged concessions towards them.
"Me making binary distributions would cause problems because of the ABI incompatibilities. Increasing the need to compile it with static libs. It would increase the binary. (binary by convencience. sources available)"
These are not insurmountable technical problems. Again, that has nothing to do with user interface/environment aspect. I don't think the future of C++-based apps are at all threatened. Support is getting better and better for C++ and ABI in GCC, etc. If anything the industry as a whole is migrated more AWAY from C than towards it, so the future is definately going to look less C-ish (if not C++, something else, C#, etc.).
Performance is fast becoming an obsolete excuse. Most desktop machines are "fast enough". What is more important is usability. Furthermore, if the target is the enterprise, the marginal cost of buying a faster machine is FAR outweighed by productivity gains. That is even if you subscribe to the notion that there are meaningful and non-mitigatable performance differences between programming languages/styles.
Restricting widget toolkit to a particular language is not a critique of end user experience! It is a critique that something is not fulfilling your particular geek fetish! Give it up, who the fuck cares if it has a better end user experience (which I'd wager Qt does, as it is pretty well reknowned for its quality and used in many applications (even commercial, where "sales" matter)).
"For my part, I think GNOME beats KDE by a long shot because it is based on C and not C++. The number of competetent C developers far outweighs the number of competent C++ developers."
So you immediately position the argument as what is best for programmers? Classic failure which is exactly why we need a USERLinux to begin with. While Gnome has wrestled with exposing widgets in so many APIs it is just a mess of tangled spaghetti, KDE from the beginning has started from the goal of making the end product seamless and intuitive for users, and chosing the single best way to do that instead of suffering death by a million cuts to whatever programming paradigms are required for whatever language has geek chic today.
The phrase "X beats Y because it is based on Z programming langauge" is a complete red herring when we are talking about end user experience.
It has always seemed to me like KDE was a much more seamlessly integrated environment. From the start, Qt seemed like a superior toolkit which has accommodated significant feature bumps without drastic reorganization or need for rewriting apps. It's all fine and good to say "GNOME/GTK is now technically equivalent", but while Gnome has been catching up KDE is now floating out a whole flotilla of new features which are *specifically* targeted at the very enterprise audience that UserLinux says it is targeted at: kiosk mode, remote access like VNC, etc.
KDE just seems like the more technically advanced and "end-user oriented" of the two.
Thank you. I had no idea that piping could be sophisticated enough to require tools like those used to design circuits. It's scary now that I think about it (hmm so instead of an Intel F00F bug, you get toxic gas/liquid dumped out in an inappropriate place? oops!).
Exactly...KDE seems much more seamless and integrated end to end which is exactly what you want the user experience to be for business users who don't care about flavors of their toolkit or how many bindings for sparklers you can hang off it. KDE seem leagues ahead of GNOME.
You will probably find that many many games require essentially "root"/Administrator/System access to hardware like CD players to verify whether there is really a CD in the drive. It is stupid and sucks. There are a couple of programs that allow you to mount CD images on disk...but I don't know how shady or legitimate such software is...and I still think some games somehow really really touch hardware...they do some out of band calls directly to hardware or something.
Um, that is most certainly NOT the case. I dont' care WHAT whatever file you read says. Winamp has had a free version since it existed as far as I know. Actually, back when I started using it, there wasn't even a non-free version or "lite" or anything like that. It was Winamp and it was free.
"Got me removed from all the junkmail lists because they thought I was dead."
I know you are lying because this, sir, will NEVER HAPPEN.
If you die they hire somebody to dig your grave up and stick shit in it (or on your headstone as the case may be). They probably install a PC down their so you can still get spam and messenger popups.
Slashdot Mirror
Or even more shocking... what if they FAKED the failed Mars missions... the missions to mars really were successful, and were powered by secret Scientology paraphernalia and immortality bracelets (not to mention the coral calcium)!
What if they FAKED the FAKED moon landing?!
Or maybe I need to lay off the special brownies...
CORBA fulfills essentially what you describe (not sure about #4). However, the CORBA spec is fairly large and baroque, so you are going to eat some overhead in complexity (not necessarily performance!) if you choose CORBA.
RMI is also a nice spec. Contrary to popular belief RMI is not a wire protocol but simply a spec for an RPC interface. The standard implementation uses a specific wire protocol and is tied to Java. However, RMI/IIOP also comes standard and is transparently interoperable with CORBA. I'm sure if you wanted to you could write your own transport implementation.
XML-RPC and SOAP are not really OO RPC mechanisms (despite SOAP containing the word "object" in it). SOAP is a bloated compromise spec created by committee by a few large players in the industry to satisfy all their requirements, and hence does not really enforce any sort of object or typing system. Already I see people addled by XML-think outright proposing this protocols. If it fits your project go for it, but XML is not the panacea people think it is.
I just finished 9:05 (or at least i THINK i finished it). Was this as short as I thought it was (like...ridiculously short)?? Or did I miss something?? I don't get it.
Same with Shrapnel. Um, I think I finished it, but it was so damn short I'm not sure. Maybe I did something wrong.
The ban only applies to feeding that excess remains to the SAME ANIMAL. I have it on good word from a soon-to-be-vet who just attended a lecture on that exact topic that "mad cow disease" first entered the cow population through SHEEP remains (scrapies). So maybe you can't feed the cow feed back to cows, but you can feed it to chickens or other animals.
....right?)
So guess what? You think you are safe by just not eating beef? Think again. America has to thank large corporate agribusiness to whom you have given your tacit approval for all these years. (Oh yeah, and keep giving money to Republicans because they're for "farmers" right?
Me...i'm a vegetarian so I feel a bit safer, BUT the jury is still out on what prions can effect, so it might turn out milk and cheese are also at risk. Who the fuck knows - we allowed this to happen.
How does this fare against Ogre (http://www.ogre3d.org/), the other major open source rendering engine?
They are thinking: "Now that we have already sold the man who has a penile inferiority complex a grotesquely and outlandishly large boutique vehicle which serves no purpose, what can we sell him for christmas? I KNOW BIG BRIGHT FUCKING LIGHTS BECAUSE BEING AN ASSHOLE IS MANLY!"
Wow, I can just feel our roads becoming safer (for those entombed in SUV tanks with 1 foot thick lead walls and searchlights for headlights.. everybody else is screwed).
Eeeeexcellent. Then you will never know the start date of the first wave of alien attack hidden in the red spectrum...
OH NO I'VE SAID TOO MUCH
I don't doubt that our eyes are less responsive to red and blue (I already knew that) but isn't the example sort of contrived? I mean, if I showed you a completely RED square, and then proceeded to remove both the RED and, say, BLUE color components, would that be proving anything? Obviously removing all the RED in a primarily RED picture is going to have more of an affect than removing any other color. The question is was the blue component in that picture significant to begin with (and in reverse deduction, is blue in the environment significant to begin with).
Isn't it charming how the democrats are just ripping each other to shreds. Yay, team spirit!
sigh
So which GTK is the real GTK? Is one an "old" deprecated version and one "new", or just different bindings to the same thing? Do the widgets act and look alike? Does the gtk-- have C backwards compatibility or does gtk+ have to be used? What sort of consistency guarantee is there accross apps then? It's interesting to hear that there is a C++ version, but I wonder how this is going to affect consistency. Is there a project-wide declaration to only build new stuff on gtk--? If not then I think there should be. There are enough toolkits to begin with, without having to worry about different versions for different languages, etc.
I really anticipate seeing how gtk-- will match up against Qt, if it is really as mature and modern as you say. Should be interesting.
"The biggest concern for me is that it more or less forces me to program in C++."
We are not talking about programmers. We are talking about users. This USERLinux, specifically aimed at users with open and acknowledged concessions towards them.
"Me making binary distributions would cause problems because of the ABI incompatibilities. Increasing the need to compile it with static libs. It would increase the binary. (binary by convencience. sources available)"
These are not insurmountable technical problems. Again, that has nothing to do with user interface/environment aspect. I don't think the future of C++-based apps are at all threatened. Support is getting better and better for C++ and ABI in GCC, etc. If anything the industry as a whole is migrated more AWAY from C than towards it, so the future is definately going to look less C-ish (if not C++, something else, C#, etc.).
Performance is fast becoming an obsolete excuse. Most desktop machines are "fast enough". What is more important is usability. Furthermore, if the target is the enterprise, the marginal cost of buying a faster machine is FAR outweighed by productivity gains. That is even if you subscribe to the notion that there are meaningful and non-mitigatable performance differences between programming languages/styles.
Restricting widget toolkit to a particular language is not a critique of end user experience! It is a critique that something is not fulfilling your particular geek fetish! Give it up, who the fuck cares if it has a better end user experience (which I'd wager Qt does, as it is pretty well reknowned for its quality and used in many applications (even commercial, where "sales" matter)).
"For my part, I think GNOME beats KDE by a long shot because it is based on C and not C++. The number of competetent C developers far outweighs the number of competent C++ developers."
So you immediately position the argument as what is best for programmers? Classic failure which is exactly why we need a USERLinux to begin with. While Gnome has wrestled with exposing widgets in so many APIs it is just a mess of tangled spaghetti, KDE from the beginning has started from the goal of making the end product seamless and intuitive for users, and chosing the single best way to do that instead of suffering death by a million cuts to whatever programming paradigms are required for whatever language has geek chic today.
The phrase "X beats Y because it is based on Z programming langauge" is a complete red herring when we are talking about end user experience.
It has always seemed to me like KDE was a much more seamlessly integrated environment. From the start, Qt seemed like a superior toolkit which has accommodated significant feature bumps without drastic reorganization or need for rewriting apps. It's all fine and good to say "GNOME/GTK is now technically equivalent", but while Gnome has been catching up KDE is now floating out a whole flotilla of new features which are *specifically* targeted at the very enterprise audience that UserLinux says it is targeted at: kiosk mode, remote access like VNC, etc.
KDE just seems like the more technically advanced and "end-user oriented" of the two.
Thank you. I had no idea that piping could be sophisticated enough to require tools like those used to design circuits. It's scary now that I think about it (hmm so instead of an Intel F00F bug, you get toxic gas/liquid dumped out in an inappropriate place? oops!).
Exactly...KDE seems much more seamless and integrated end to end which is exactly what you want the user experience to be for business users who don't care about flavors of their toolkit or how many bindings for sparklers you can hang off it. KDE seem leagues ahead of GNOME.
What is "piping"? At first I thought this guy wanted some CAD software to design plumbing or something...
You will probably find that many many games require essentially "root"/Administrator/System access to hardware like CD players to verify whether there is really a CD in the drive. It is stupid and sucks. There are a couple of programs that allow you to mount CD images on disk...but I don't know how shady or legitimate such software is...and I still think some games somehow really really touch hardware...they do some out of band calls directly to hardware or something.
On Linux solitaire is replaced by many configuration utilities that essentially serve the same purpose :p
Well, I hate the world and I generally want to ruin everybody's self esteem...
Or maybe I was just joking?
Only on slashdot would we have a news item on essentially placing a small cube into a bigger cube. ;)
Um, that is most certainly NOT the case. I dont' care WHAT whatever file you read says. Winamp has had a free version since it existed as far as I know. Actually, back when I started using it, there wasn't even a non-free version or "lite" or anything like that. It was Winamp and it was free.
So...what would this game be like...you sit back and refrain from voting, and it just picks a candidate for you? EA Voter Apathy 2004!
"Got me removed from all the junkmail lists because they thought I was dead."
I know you are lying because this, sir, will NEVER HAPPEN.
If you die they hire somebody to dig your grave up and stick shit in it (or on your headstone as the case may be). They probably install a PC down their so you can still get spam and messenger popups.