I'm willing to bet it's much easier for you to fix Nouveau's implementation than to get access to Nvidia's code and fix the bug in the proprietary driver.
Which is really the point of not completely relying on proprietary code in the kernel.
Why? Because it's a sane method of delivering software, which is becoming widely used (i.e. Steam, iTunes Store, etc) vs the traditional "Herpes" model used by Windows?
Can you name a faster and more reliable implementation? Didn't think so.
Java held out the promise of write it once run it anywhere, but that promise has yet to be fulfilled as there are still differences from platform to platform that make developing in it a chore rather then enjoyable work.
If you use pure java code the cross platform stuff just works. Period.
Most of the problems are with the various implementations of both JIT's and VM's and mostly having to do with how things are abstracted eg: big -v- little endian, file access and those sorts of things.
What does this nonsensical gibberish mean?
The tons of lib's that are mentioned as a god send have their own problems as well but that has more to do with programmer quality then anything else, but even the well designed and written ones still overlook the JIT and VM problems and then you end up having damn quirky behavior that can take weeks to track down, hence the problem of everyone sending out a complete JRE with their program and you end up in JRE hell with 14 different versions of JRE's on your system.
If you target older jre's you'll get very good compatibility across the board. There used to be issues caused by Microsoft's JRE... but that's why they built it. If you target a bleeding edge ANYTHING, you're going to have compatibility problems.
I liked the IDEA of having SUN control Java because at least things would have been consistent but that failed as well with to damn many versions being released. Now we have everyone and their grandmother writing JVM's JIT's and JRE's and none of them do anything exactly the same which has thrown ever more variability into the mix and just made everything messier since suddenly you now had to install vendor X's JRE or VM because some fool decided that it made everything 1% faster and they JUST had to have it or alternatively it had a COOL name.
Why do you keep randomly throwing the acronym "JIT" everywhere? Again, you just poorly restated your earlier comment which isn't true and makes little sense.
I see the biggest problem with WEB development today as two things. 1. Lack of a statefull connection and 2. The proliferation of languages with linguistic and syntactual differences but little else to set them apart except a fan club. PHP, Ruby, Python, VB, Perl, all of them doing the same thing, serving the content.
1) ???? How does this affect Java in anyway? 2) ???? How does this affect Java in anyway?
The fundamental paradigm of the web is broken and needs repair badly. The solution is to split it, as I have said before, into two distinct camps, the Application Web and the Text and Pretty Picture Web because trying to mix the two has proven to be a miserable failure.
????? WTF
In summary,
FlyingGuy, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone on this site is now dumber for having read to it. I award you no points, and may God have mercy on your soul.
"javascript" is essentially just a language specification, how it manages memory and other resources is implementation dependant.
A javascript program could be interpreted as has been in many web browsers, JIT compiled to native code like Java (which is getting more popular) or even be fully compiled to native code ahead of time.
The GF100 is clearly nuclear powered, which would explain the massive heatsink and PCB, which takes up a majority of the standard size PC case and conveniently covers all available SATA and all other types of peripheral interface connectors.
Slashdot Mirror
I don't think the word "parody" means what you think it means.
I'm willing to bet it's much easier for you to fix Nouveau's implementation than to get access to Nvidia's code and fix the bug in the proprietary driver.
Which is really the point of not completely relying on proprietary code in the kernel.
The official closed source driver creates a proprietary dependency on an otherwise open OS kernel.
This irks some free software hippies and it also makes using Nvidia hardware on unsupported hardware platforms more difficult.
Why? Because it's a sane method of delivering software, which is becoming widely used (i.e. Steam, iTunes Store, etc) vs the traditional "Herpes" model used by Windows?
It's the YEAR OF THE LINUX desktop! It's official! /Happy Ubuntu User
Agreed, it's perfectly cromulent.
It's more like PPBA in reality.
Hopefully it's because you have cancer.
???
Uh, you forgot the last line of your post:
"Get off my lawn, you damn kids and your rock and roll music, social equality and your high level programming languages!"
You're blaming Java because Linux sound sucks?
I use Ubuntu daily and I don't think a day goes by without me cursing the names ALSA and PulseAudio.
Especially PulseAudio.
Unfortunately the implementation is poor.
Can you name a faster and more reliable implementation? Didn't think so.
Java held out the promise of write it once run it anywhere, but that promise has yet to be fulfilled as there are still differences from platform to platform that make developing in it a chore rather then enjoyable work.
If you use pure java code the cross platform stuff just works. Period.
Most of the problems are with the various implementations of both JIT's and VM's and mostly having to do with how things are abstracted eg: big -v- little endian, file access and those sorts of things.
What does this nonsensical gibberish mean?
The tons of lib's that are mentioned as a god send have their own problems as well but that has more to do with programmer quality then anything else, but even the well designed and written ones still overlook the JIT and VM problems and then you end up having damn quirky behavior that can take weeks to track down, hence the problem of everyone sending out a complete JRE with their program and you end up in JRE hell with 14 different versions of JRE's on your system.
If you target older jre's you'll get very good compatibility across the board. There used to be issues caused by Microsoft's JRE... but that's why they built it. If you target a bleeding edge ANYTHING, you're going to have compatibility problems.
I liked the IDEA of having SUN control Java because at least things would have been consistent but that failed as well with to damn many versions being released. Now we have everyone and their grandmother writing JVM's JIT's and JRE's and none of them do anything exactly the same which has thrown ever more variability into the mix and just made everything messier since suddenly you now had to install vendor X's JRE or VM because some fool decided that it made everything 1% faster and they JUST had to have it or alternatively it had a COOL name.
Why do you keep randomly throwing the acronym "JIT" everywhere? Again, you just poorly restated your earlier comment which isn't true and makes little sense.
I see the biggest problem with WEB development today as two things. 1. Lack of a statefull connection and 2. The proliferation of languages with linguistic and syntactual differences but little else to set them apart except a fan club. PHP, Ruby, Python, VB, Perl, all of them doing the same thing, serving the content.
1) ???? How does this affect Java in anyway? 2) ???? How does this affect Java in anyway?
The fundamental paradigm of the web is broken and needs repair badly. The solution is to split it, as I have said before, into two distinct camps, the Application Web and the Text and Pretty Picture Web because trying to mix the two has proven to be a miserable failure.
????? WTF
In summary,
FlyingGuy, what you've just said is one of the most insanely idiotic things I have ever heard. At no point in your rambling, incoherent response were you even close to anything that could be considered a rational thought. Everyone on this site is now dumber for having read to it. I award you no points, and may God have mercy on your soul.
Java's big problems are a much too large standard library that has to be loaded on startup and an old bytecode verifier.
It has little to do with the JIT, as all applications runs in interpreted mode first anyway.
You're talking out of your ass.
Well you can't legally install OSX on a machine.... on sell it.
I think Apple would have a quite an up hill battle going after home EULA violators, as rare as they are. Plus, I doubt Apple really cares anyway. ;)
Rhino and JScript.NET
Personally, I fucking hate Javascript.
So fys.
"javascript" is essentially just a language specification, how it manages memory and other resources is implementation dependant.
A javascript program could be interpreted as has been in many web browsers, JIT compiled to native code like Java (which is getting more popular) or even be fully compiled to native code ahead of time.
Yep and apparently they've figured out a way to make water from ice.
Man, what science can do these days is amazing!
Oh and "Microsoft" is now called "Google."
I can't wait to see how Google is viewed in 10-15 years. :)
Except now "PC" is called "Android."
I'm a mac.
I'm a PC.
and I'm here to serve you a fucking isummons to court for violating our EULA. Oh whats that bitch? Did I hear you say PsyStar? Thought so.
REHABILITATION!
I'm totally with you scro!
None of the above, you simpleton!
The GF100 is clearly nuclear powered, which would explain the massive heatsink and PCB, which takes up a majority of the standard size PC case and conveniently covers all available SATA and all other types of peripheral interface connectors.
Do you work for Microsoft?
Employers don't seek out recessions so they can fire people.
Hi, you must be new here.
fys