62 karma · joined March 5, 2012
More predictable, very likely. Much faster, this is simply not true. E.g., quotes from an article by Brian Goetz[1]:
The common code path for new Object() in HotSpot 1.4.2 and later is
approximately 10 machine instructions, whereas the best performing
malloc implementations in C require on average between 60 and 100
instructions per call. ... "Garbage collection will never be as efficient
as direct memory management." And, in a way, those statements are right
-- dynamic memory management is not as fast -- it's often considerably faster.
> allocation to the stack, something that effectively ceases to exist in GC'd languages.*Not true, either. With escape analysis, Hotspot JVM can do stack allocation. The flag of doing escape analysis is actually turned on by default now.
[1] http://www.ibm.com/developerworks/java/library/j-jtp09275/in...
If codebase is that large, language alone can't solve all the problems. Be it compiling time, testing time, or whatever problems large codebase may have. I guess that's exactly what Steve Yegge tried to say in his famous Platform Rant blog post.
How come? Your interpretation of what I said amuses me, sir. And the way you do it, quoting single sentence without context, seriously?
http://news.ycombinator.com/item?id=3702253
http://news.ycombinator.com/item?id=3700277
I'd like to share this essay from Simon Phipps that has enlightened me from time to time on such matters.Please, at least read what you reply to.
I submitted a ticket from outside as an alumnus. It is a fact. Credit to Google for setting this up. That being said, if there is anyone gets delusional, it is you.
I'm an engineer and used to work for Sun Microsystems. It was awesome. So I have pretty good idea about what it takes and what to expect working for a good silicon valley company in general, including Google. It just didn't apply to what happened to me in Google.
Speak for yourself, would you? I'm myself a victim, unfortunately. I never even knew my Perf when I was with the company, only discovered it accidentally after I left. The process is very broken for me. Thanks @michaelochurch, I now know better about what had happened.
Is Datomic just for JVM languages? At the moment, yes. We have ideas for how to enable Datomic on non-JVM languages while preserving as much of the embedded power as possible.