Your analogy is flawed. It was the users that were rear-ended, not Torvalds. Torvalds is the judge throwing the book at the driver who rear-ended you when he keeps trying to say it was all *your* fault.
>> but in this case I do feel especially bad for Asian's and Whites given the higher requirement for them.
You've got it backwards: Feel bad for the other races, who won't be pushed to excel to the same level and will therefore be stuck in menial low-pay jobs for the rest of their lives.
Yeah... why use the latest version of a working engine you've been constantly improving for 8 years that already has OpenGL support and a lot of the other necessary components done? Why not throw it all away and creating a Linux engine that's not compatible with any of your existing games and has to be maintained separately from the engine being used on the other platforms?
Maybe because it makes a hell of a lot more sense?
Valve may be working on Source2, but it's not near ready and most likely none of the existing games will be updated to use it (though we'll likely see new installments for the existing franchises use it).
> "Either Steam sucks as a platform or Linux sucks for doing game-oriented graphics."
That's a false dichotomy. You're missing the option that your understanding of Linux and what a kernel developer does "sucks". There are actually many good reasons they would want a kernel dev or two, and none of them require Steam or Linux to suck.
If the rumors are true and they really are releasing their own console, someone's got to write the device drivers for their unique hardware. The controllers will probably be of their own design, so that's the first thing that comes to my mind.
Device drivers in Linux are kernel modules and live in kernel space. Undoubtedly they will also want these developers to be expert at building custom kernels, as they would want an image with all the standard hardware modules compiled in place, and the non-relevant memory-consuming bits (support for file systems they won't use, etc.) removed.
No, this will be great if they can keep it as far away from WINE as possible.
You can *already* install WINE today, use it to install Steam and Windows games, and the vast majority work with very little hassle (I own dozens of Steam games that I play exclusively on Linux via WINE).
*This* will be better, because you won't have to suffer through any problems with bugs in the abstraction layer the next time Valve patches their game clients. Things will just work, without those occasional hiccups that only the hardcore can workaround.
There's absolutely no reason for WINE to be involved with this at all, and if it were it would put us back to right were we already are. WINE is a *great* project, and indispensable to most people switching to Linux - but its function should be to fill the gaps when a native solution isn't available - not to slow or dissuade native Linux development.
This could be the start of much better video driver support, and improvements all around for platform agnostic APIs.
This is good news: Because obviously Oracle hired mentally challenged lawyers.
Not only is what their lawyer said obvious hyperbole, but it is totally irrelevant. I don't care how much time it would take for a non-programmer to do it: how long does it take a real programmer to do it.
The answer to that is of course on the order of seconds, since validating input is something every programmer has done thousands of times.
The launcher on the left side of the screen shows running apps.
>> Moving tray items is a must.
Grab the items in the launcher, drag to the right, and re-insert them back into the launcher wherever you want.
>> Synaptic package manger [sic] is a must.
If you want that, use the much prettier Software Centre to install it with a simple click.
>> It's so complicated to make it look like my 10.10 desktop.
Then install your old desktop manager or don't upgrade.
As a long-time KDE user who couldn't stand working with Gnome for extended periods, I actually find Unity quite enjoyable. Of course, I customize it with things like cairo-dock and make it fit my own workflow - rather than just bitch that the default is too simple for me to use.
>> "Why the hell are people so obsessed with the OtherOS crap?"
Because we paid for it, and then got treated to a surprise game of Sophie's Choice with OtherOS or network connectivity for the games we already owned.
If Sony came into your house and disabled even just a seldomly-used button on your remote control, I'll bet you'd bitch about it every time their name was mentioned - regardless of whether you could go out and buy a separate remote for that button or not.
It's not so much about OtherOS as the principle of ownership.
Don't feel left out: they won't work on Linux either.:)
compile_and_link: x86_64-unknown-linux-gnu/stage0/lib/rustc/x86_64-unknown-linux-gnu/lib/librustc.so error: internal compiler error unexpected failure note: The compiler hit an unexpected failure path. This is a bug. Try running with RUST_LOG=rustc=0,::rt::backtrace to get further details and report the results to github.com/mozilla/rust/issues make: *** [x86_64-unknown-linux-gnu/stage0/lib/rustc/x86_64-unknown-linux-gnu/lib/librustc.so] Error 101
I know you're joking, but as a Texan I must point out that we'd never bypass the justice system unless the video from the drone showed with a high degree of probability that the suspect appeared to be mentally retarded.
Seriously. If your using 13-year old cards in your system, you're probably not running the latest software anyway.
And, since it's open source - you're free to keep compiling in support on your own. It's not like it's Windows where you would be SOL when a manufacturer doesn't release a driver compiled for the latest x-bit version processor.
You totally missed the point. You're talking about copyright on the code implementing the API - while the real topic here is whether or not the API calls (function names) themselves can be copywritten.
And of course the answer is 'no', because that prevents any and all compatible implementations. In fact, you'd be in violation simply for writing a program that called the API - since you have to use the function names in the calling program.
Oracle's lawyers know nothing about programming, apparently. If things worked like they're trying to say they do, Microsoft could sue anyone that made software for Windows because at some point you used a header that included the Windows API function names.
Or, it's an ancient superfungus that had been locked in an iceshelf after killing all life on the planet hundreds of millions of years ago... set free by global warming.
Slashdot Mirror
Your analogy is flawed. It was the users that were rear-ended, not Torvalds. Torvalds is the judge throwing the book at the driver who rear-ended you when he keeps trying to say it was all *your* fault.
>> but in this case I do feel especially bad for Asian's and Whites given the higher requirement for them.
You've got it backwards: Feel bad for the other races, who won't be pushed to excel to the same level and will therefore be stuck in menial low-pay jobs for the rest of their lives.
Yeah... why use the latest version of a working engine you've been constantly improving for 8 years that already has OpenGL support and a lot of the other necessary components done? Why not throw it all away and creating a Linux engine that's not compatible with any of your existing games and has to be maintained separately from the engine being used on the other platforms?
Maybe because it makes a hell of a lot more sense?
Valve may be working on Source2, but it's not near ready and most likely none of the existing games will be updated to use it (though we'll likely see new installments for the existing franchises use it).
You didn't expect them to list it as HL3, did you?
Reading about other IP decisions, I'm under the opinion that German courts are the East Texas of Europe.
(Written from East Texas)
> How does it make sense to push a buggy product out the door before it's ready?
Because this way you get to sell them Windows 8, then tout the fix for the problems as major features when you sell them Windows 9.
I mean, what else are they going to do? Switch to Linux? Ha!
You do realize that FOX News is going to quote you and credit you as The Official Spokesman for The Open Source Community, right?
Absurd? I don't know what you're talking about.
[posted from Quantal Quetzal 12.10b1]
> "Either Steam sucks as a platform or Linux sucks for doing game-oriented graphics."
That's a false dichotomy. You're missing the option that your understanding of Linux and what a kernel developer does "sucks". There are actually many good reasons they would want a kernel dev or two, and none of them require Steam or Linux to suck.
If the rumors are true and they really are releasing their own console, someone's got to write the device drivers for their unique hardware. The controllers will probably be of their own design, so that's the first thing that comes to my mind.
Device drivers in Linux are kernel modules and live in kernel space. Undoubtedly they will also want these developers to be expert at building custom kernels, as they would want an image with all the standard hardware modules compiled in place, and the non-relevant memory-consuming bits (support for file systems they won't use, etc.) removed.
No, this will be great if they can keep it as far away from WINE as possible.
You can *already* install WINE today, use it to install Steam and Windows games, and the vast majority work with very little hassle (I own dozens of Steam games that I play exclusively on Linux via WINE).
*This* will be better, because you won't have to suffer through any problems with bugs in the abstraction layer the next time Valve patches their game clients. Things will just work, without those occasional hiccups that only the hardcore can workaround.
There's absolutely no reason for WINE to be involved with this at all, and if it were it would put us back to right were we already are. WINE is a *great* project, and indispensable to most people switching to Linux - but its function should be to fill the gaps when a native solution isn't available - not to slow or dissuade native Linux development.
This could be the start of much better video driver support, and improvements all around for platform agnostic APIs.
In my mind, I like to picture this spat ending with them shouting "INDUBITABLY!" at each other and throwing tea.
This is good news: Because obviously Oracle hired mentally challenged lawyers.
Not only is what their lawyer said obvious hyperbole, but it is totally irrelevant. I don't care how much time it would take for a non-programmer to do it: how long does it take a real programmer to do it.
The answer to that is of course on the order of seconds, since validating input is something every programmer has done thousands of times.
If they are delivered that way, I don't care what they cost. But yes, sooner, please.
>> Task bar is a must.
The launcher on the left side of the screen shows running apps.
>> Moving tray items is a must.
Grab the items in the launcher, drag to the right, and re-insert them back into the launcher wherever you want.
>> Synaptic package manger [sic] is a must.
If you want that, use the much prettier Software Centre to install it with a simple click.
>> It's so complicated to make it look like my 10.10 desktop.
Then install your old desktop manager or don't upgrade.
As a long-time KDE user who couldn't stand working with Gnome for extended periods, I actually find Unity quite enjoyable. Of course, I customize it with things like cairo-dock and make it fit my own workflow - rather than just bitch that the default is too simple for me to use.
>> "Why the hell are people so obsessed with the OtherOS crap?"
Because we paid for it, and then got treated to a surprise game of Sophie's Choice with OtherOS or network connectivity for the games we already owned.
If Sony came into your house and disabled even just a seldomly-used button on your remote control, I'll bet you'd bitch about it every time their name was mentioned - regardless of whether you could go out and buy a separate remote for that button or not.
It's not so much about OtherOS as the principle of ownership.
"Spam will be a thing of the past in two years' time."
Don't feel left out: they won't work on Linux either. :)
Meet the new boss, same as the old boss?
I'm a doctor, not a bricklayer!
>> They are designed to spoof the carrier's tower in order to ascertain only the location of a mobile device
By virtue that corporations are people, I suppose this makes them guilty of identity theft.
I know you're joking, but as a Texan I must point out that we'd never bypass the justice system unless the video from the drone showed with a high degree of probability that the suspect appeared to be mentally retarded.
>> What the hell does law enforcement need a 37mm/40mm grenade launcher attached to a remote-controlled UAV for? Whatever, moving on.
Enforcing software patents.
Seriously. If your using 13-year old cards in your system, you're probably not running the latest software anyway.
And, since it's open source - you're free to keep compiling in support on your own. It's not like it's Windows where you would be SOL when a manufacturer doesn't release a driver compiled for the latest x-bit version processor.
You totally missed the point. You're talking about copyright on the code implementing the API - while the real topic here is whether or not the API calls (function names) themselves can be copywritten.
And of course the answer is 'no', because that prevents any and all compatible implementations. In fact, you'd be in violation simply for writing a program that called the API - since you have to use the function names in the calling program.
Oracle's lawyers know nothing about programming, apparently. If things worked like they're trying to say they do, Microsoft could sue anyone that made software for Windows because at some point you used a header that included the Windows API function names.
Or, it's an ancient superfungus that had been locked in an iceshelf after killing all life on the planet hundreds of millions of years ago... set free by global warming.
Whichever.