GCC and Visual Studio are only used at compile time, not when deployed to end users during execution. They are limited in what they can optimize at this point in time.
Example: Java and other optimizing JITs can devirtualize methods at runtime, effectively removing lots of lookups (possibly expensive branches) thus cache misses and other hazards resulting from heavy OO/polymorphism. GCC and Visual Studio cannot do this because they have no way of knowing what type a call site may be at an arbitrary execution point. This is one of the reasons C++ tends to really suck if you use a lot of OO in your application design.
There are literally hundreds (or MILLIONS) of these optimizations that are impossible to do with static compilers like GCC and VS.
JIT is going to more memory because you'll have both native and vm instructions in memory, whereas before you'd only have interpreted code. It's worth the tradeoff of course and will become more valuable as phone memory grows.
Dalvik's JIT compilation is going to allow future Android applications to meet and exceed the performance of applications compiled ahead of time ("native" applications). Native is really a bad term because both dynamically JIT'd code and statically compiled code is native. The main difference is the JIT can do all kinds of fancy optimizations and reoptimizations (OSR/devirtualization) to the native code that can't be done ahead of time by a static compiler (i.e. gcc).
Lets see, I fired up Firefox (chrome user here) and opened slashdot, shacknews and a couple of other sites (you know, porn).
Memory Usage: 90MB
I have 8GB of RAM, probably more than your average user, which comes out to roughly 1% of my system memory. Even someone with half that could run dozens and dozens of Firefox instances with intensive pages open and still use other apps without an issue.
Remember Bob, baby steps to Google, baby steps to the search box. You don't need to obsess over every last bit of memory. Baby steps.
Slashdot Mirror
So you're saying pacman turns you on.
And it wasn't Mrs. Pacman.
It was Mr. Pacman.
Mark Twain had to have been one of the coolest guys who ever lived.
Oh we'll see about THAT!
No one suspects the Digital Millennium Copyright Act!
Or they'll just get drunk at lunch and call it a day!
Awww, I bet if we ask nicely they could have the robot play the world's smallest violin.
Or that can playing something other than pentatonic scales!
You clearly don't understand what we're talking about.
They're designed by Japanese people who are typically fairly small statured.
So you must be some kind of midget or wear *really* tight pants.
GCC and Visual Studio are only used at compile time, not when deployed to end users during execution. They are limited in what they can optimize at this point in time.
Example: Java and other optimizing JITs can devirtualize methods at runtime, effectively removing lots of lookups (possibly expensive branches) thus cache misses and other hazards resulting from heavy OO/polymorphism. GCC and Visual Studio cannot do this because they have no way of knowing what type a call site may be at an arbitrary execution point. This is one of the reasons C++ tends to really suck if you use a lot of OO in your application design.
There are literally hundreds (or MILLIONS) of these optimizations that are impossible to do with static compilers like GCC and VS.
*going to use, dammit
JIT is going to more memory because you'll have both native and vm instructions in memory, whereas before you'd only have interpreted code. It's worth the tradeoff of course and will become more valuable as phone memory grows.
Dalvik's JIT compilation is going to allow future Android applications to meet and exceed the performance of applications compiled ahead of time ("native" applications). Native is really a bad term because both dynamically JIT'd code and statically compiled code is native. The main difference is the JIT can do all kinds of fancy optimizations and reoptimizations (OSR/devirtualization) to the native code that can't be done ahead of time by a static compiler (i.e. gcc).
But how else will your robots check their MySpace accounts?
Sounds like a plan to me.
When the robot uprising starts, there'll be a million ways to crash the fuckers.
No joke.
Satan would probably be standing there like "I just *knew* you guys would come back some day! Yay!"
I'd definitely like to see IRS personnel inside an active volcano.
I submit that, you sir, are quite good at reading comprehension.
Amazingly good in fact.
You should win some type of award. Can you post your phone number? I know people, maybe we can get something rolling.
Riiiiight and I'm sure the feature set between the two is nearly identical.
Lets see, I fired up Firefox (chrome user here) and opened slashdot, shacknews and a couple of other sites (you know, porn).
Memory Usage: 90MB
I have 8GB of RAM, probably more than your average user, which comes out to roughly 1% of my system memory. Even someone with half that could run dozens and dozens of Firefox instances with intensive pages open and still use other apps without an issue.
Remember Bob, baby steps to Google, baby steps to the search box. You don't need to obsess over every last bit of memory. Baby steps.
You realize that 10MB of RAM is less than 1% of the total memory in most desktops these days, right?
I know, I know, I'll get off your lawn now.
Oooh, I'm totally scared.
I'm not so sure I'd jump to the conclusion that this is useful.
Determining the amount of sarcasm in bird calls doesn't seem to be an effective way to use research money IMO.
Good fucking god, $700 for the Drobo FS?
You could build a capable home server box AND buy some of the drives for that much.
Think of the poor strippers man!
You must be using a different t-mobile than I am.
Right but outside of cell provider fantasy land, it's more like 60k on average with 3000ms latency.