I mentioned Firefox specifically because i can open a crapload of tabs on other browsers without these issues. I've posted a pic of my workstation upper in the thread, where Opera is shown behaving very nicely in these situations.
Again, i like FF a lot. The developers seem have started addressing these issues since version 6, but still, i keep finding out it leaks memory like crazy after a while.
...since they let Carly Fiorina run HP. It's been downhill since then, with a continuous stream of screwups. And now that HP is, essentially, focusing only on services i expect them to continue loosing relevance with each passing day.
I mean, what's the logic behind buying WebOS (a great, but ultimately dying platform) for $1.2 billion just to drop the platform entirely 6 months later?
It's hard to use the computer when you find up the damn browser is eating half of your 4 Gigs of RAM:) I like Firefox overall, but they really need to start addressing their memory management issues.
Look at the computer from the next casual person you have? You'll notice that they're using 5% of their RAM and 2% of their cpu(s).
If only. Try firing up Firefox with 10-12 tabs and see it slowly, but steadly, eating you memory up. A browser is one of the many apps i run on my systems, so good peformance and memory handling has a definite impact on my user experience.
I wouldn't buy an Apple product if my life depended on it, but Jobs is undoubtly the best CEO of the past 25 years. I have a lot of respect for him and his work.
I love Python, don't get me wrong, but it is nowhere near Java regarding raw performance. Even the developers acknowledge this, with stuff like the Google sponsored Unladen swallow and PyPy.
Haven't toyed much with Ruby these days though. I should:)
I don't think there's a single language today out there that isn't compiled to bytecode prior to execution on a VM. Even Perl does it AFAIK. The code is still being interpteted, just not from the text sourcecode directly.
No. C++ generates binary machine code. It is not portable. It is loaded directly into memory where it is executed directly by the CPU. There's no "just in time" there, at all.
The difference is in the how. JIT gives huge improvements in stuff like loops and basic constructs because these are easily translated into machine code. But for Java bytecodes dealing with OOP constructs (new, for example) this basically means that the JIT has to embed a lot of machine code as an abstraction layer. The improvements there are minimal because this code is doing pretty much the same the JVM would do processing that bytecode on the fly.
Making a very loose comparison, i could easily bundle a JVM implementation and Java bytecode into an.EXE and call that "compiling". In fact, there's software that does exactly this. Quick Basic did it too back in the DOS days.
JIT is great, but it is not a compiling by any stretch. Is a hybrid approach that works pretty well, but every time you fire up your Java code the JVM will process it for you, interpret it and translate it, when possible, to native machine code on the fly. In fact, for big files this process can add a significant start up time penalty.
Bytecode IS interpreted (by the JVM), sorry. Jazelle was the only attempt of a hardware JVM implementation that i know of and even that was short lived.
Amen to that. I generally dislike Apple products, but this guy was (is) the best CEO in the IT business in the past years. I have a lot of respect for his work and dedication.
Maybe the power management on the stock HTC Tatto is crap (wouldn't surprise me at all), but i can attest that the battery life on this phone is noticeably better using CM. Switching the CPU governor to powersave squeezes it even a bit more, and being a low-end device i honestly can't tell the difference between the default one (ondemand).
+1. CyanogenMod is ridiculously good and showcases how good the Android platform can be when it is not crippled or loaded with bloatware. I installed it recently on an old HTC Tattoo, which is a "low end" Android with no official updates from HTC, and the difference with the stock 1.6 version is astonishing.
It's almost like a brand new phone. Hell, even battery life is better.
Slashdot Mirror
Yeah, i guess other browsers are just magical...
So true. And i this is from someone who wouldn't buy an Apple product if his life depended on it.
I mentioned Firefox specifically because i can open a crapload of tabs on other browsers without these issues. I've posted a pic of my workstation upper in the thread, where Opera is shown behaving very nicely in these situations.
Again, i like FF a lot. The developers seem have started addressing these issues since version 6, but still, i keep finding out it leaks memory like crazy after a while.
I usually get along using way less than that. For example, this is my (crappy) desktop at work, right now...
...since they let Carly Fiorina run HP. It's been downhill since then, with a continuous stream of screwups. And now that HP is, essentially, focusing only on services i expect them to continue loosing relevance with each passing day.
I mean, what's the logic behind buying WebOS (a great, but ultimately dying platform) for $1.2 billion just to drop the platform entirely 6 months later?
It's hard to use the computer when you find up the damn browser is eating half of your 4 Gigs of RAM :) I like Firefox overall, but they really need to start addressing their memory management issues.
Look at the computer from the next casual person you have? You'll notice that they're using 5% of their RAM and 2% of their cpu(s).
If only. Try firing up Firefox with 10-12 tabs and see it slowly, but steadly, eating you memory up. A browser is one of the many apps i run on my systems, so good peformance and memory handling has a definite impact on my user experience.
Touché :)
http://en.wikipedia.org/wiki/Ionizing_radiation
I wouldn't buy an Apple product if my life depended on it, but Jobs is undoubtly the best CEO of the past 25 years. I have a lot of respect for him and his work.
Thank you for making the Internet a much more interesting place, Cmdr. We are all in debt here.
I wish you the very best of luck in your future endeavors.
I love Python, don't get me wrong, but it is nowhere near Java regarding raw performance. Even the developers acknowledge this, with stuff like the Google sponsored Unladen swallow and PyPy.
Haven't toyed much with Ruby these days though. I should :)
I don't think there's a single language today out there that isn't compiled to bytecode prior to execution on a VM. Even Perl does it AFAIK. The code is still being interpteted, just not from the text sourcecode directly.
I was *almost* tempted to ask you to enlighten me there. Nice job! Now doze the fuck off please.
I was referring to speed alone, where Java runs circles around Lisp. But yes, if we're talking elegance Lisp makes Java look like Flavor Flav.
No. C++ generates binary machine code. It is not portable. It is loaded directly into memory where it is executed directly by the CPU. There's no "just in time" there, at all.
The difference is in the how. JIT gives huge improvements in stuff like loops and basic constructs because these are easily translated into machine code. But for Java bytecodes dealing with OOP constructs (new, for example) this basically means that the JIT has to embed a lot of machine code as an abstraction layer. The improvements there are minimal because this code is doing pretty much the same the JVM would do processing that bytecode on the fly.
Making a very loose comparison, i could easily bundle a JVM implementation and Java bytecode into an .EXE and call that "compiling". In fact, there's software that does exactly this. Quick Basic did it too back in the DOS days.
JIT is great, but it is not a compiling by any stretch. Is a hybrid approach that works pretty well, but every time you fire up your Java code the JVM will process it for you, interpret it and translate it, when possible, to native machine code on the fly. In fact, for big files this process can add a significant start up time penalty.
Bytecode IS interpreted (by the JVM), sorry. Jazelle was the only attempt of a hardware JVM implementation that i know of and even that was short lived.
AFAIK it is planned to be fixed on update 2. Which is kinda retarded - even for Oracle standards.
It sounds like even Oracle, itself, doesn't think Java 7 is ready for the public!
And they are right indeed...
To be fair here compared to other interpreted languages Java is still the king of the hill. By far.
Disclaimer: Yes, interpreted. Bytecode is interpreted, even with stuff like JIT.
Amen to that. I generally dislike Apple products, but this guy was (is) the best CEO in the IT business in the past years. I have a lot of respect for his work and dedication.
Apple almost died the last time he left. But i agree about the stock tip - it will go back up again in as soon as a new product is announced.
Maybe the power management on the stock HTC Tatto is crap (wouldn't surprise me at all), but i can attest that the battery life on this phone is noticeably better using CM. Switching the CPU governor to powersave squeezes it even a bit more, and being a low-end device i honestly can't tell the difference between the default one (ondemand).
+1. CyanogenMod is ridiculously good and showcases how good the Android platform can be when it is not crippled or loaded with bloatware. I installed it recently on an old HTC Tattoo, which is a "low end" Android with no official updates from HTC, and the difference with the stock 1.6 version is astonishing.
It's almost like a brand new phone. Hell, even battery life is better.