would've said that it's not possible given it's a website, but with event polling it actually is, same goes for their phone applications.
on one hand it seems unnecessary and dumb to store so much data that's effectively 'scratch' anyway, but on the other it would be useful to them for extracting marketing data if they could reconcile the cost of storing and processing it against possible profitability
actually I have a friend that work/s/ed for facebook, might be worth asking him
java could be compiled at deployment, not runtime and still be cross platform
profiling a website here and it's optimised extremely poorly; trying to work out how to clean it up but I didn't realise ASPX compiles chunks as they're requested which effectively punches the processor in the dick, hard and fast
"Improvements in compiler technology can have an impact on existing programs. A better C compiler does not help you at all with programs already deployed. A better JIT-compiler will improve the performance of existing programs. The Java code you wrote ten years ago will run faster today."
the only argument I've seen so far that makes any real sense
Specifically ASPX, by default, compiles a page the first time it's requested, then the compiled application segment is cached for a short period - further requests within that period go to the compiled segment. after expiry next request recompiles.
what the hell is the benefit of this over pre-compiling things?
