Viewing profile — Doradus

Your history is a little mixed up there. The original author of Turbo Pascal, and Chief Architect of Delphi, became the Lead Architect of C#. It’s not like Microsoft came out of no…

His youth is remarkable, so they remarked on it. I'm not sure what about this troubles you.

Depends on the elevation of the horizon.

> I expect discriminating by amount of relevant experience is fair, but that's not the same as age. As someone who started coding at age 9, I agree. :-) It's not about hiring someo…

Agreed. I remember being in my early 20s, watching my more experienced colleagues, and realizing this. I had had a different (incorrect) mental model: I had thought intellect was a…

It seems absurd that an article claims to disprove a hypothesis linking structure to communication patterns without even the slightest mention of trying to observe those patterns. …

This. I used to work at IBM, and I can't tell you how many different (mutually inconsistent) narratives about "how IBM is".

Huh? That's funny--I would have said the opposite. It was from watching Obama's speeches that I learned that silent pauses can be much less annoying than "umms". If you want to see…

It doesn't take long to get used to that style. It took me maybe three weeks of playing with Java 8 streams in my spare time before I got quite comfortable with it.

Easy, there. Librarians aren't the bad guys in this story.

Nope. Transactions, in the sense of the article, bear no relation to goroutines. The right answer is that Java's generational collector supports this transaction lifetime reasonabl…

RAII is using one C++ misfeature (destructors) to work around another misfeature (inability to do cleanup when leaving a lexical scope). Go has a far more elegant solution to the l…

I'm not sure you've grasped the write barrier part. That's the really new part.

Did you read the article? It answers your question. Take a look at the section that begins with this: The problem is called a paradox because two analyses that both sound intuitive…

(Whoops, I've misunderstood you twice. I think my other reply answered the wrong question. Let me try again.) I didn't say synchronization can prevent EA. I said that calling a fin…

I must have misunderstood you. You made a statement that I parsed as follows: "If (this stuff isn't escaping) then (the JIT can prove that it isn't using a lock)." That is logicall…

Your argument proves that the time taken can be no less than O(n) in the number of object references in live objects. The (potentially billions of) unreachable objects are never to…

I seem to have hit a nerve here. Perhaps I haven't been clear about some of the points I'm making, which I don't think are all that contentious. I'm not saying a fast GC can reduce…

Well, it's hard to deny that the work done by the program is O(n) (or even Ω(n)) in the number of objects created by the program. That's almost tautological. The thing that is inte…

The JVM doesn't release the memory to the OS when garbage is collected; only when the heap shrinks. Any zeroing the OS might do is proportional to the size change in the heap, not …

I think you're referring to a mark and sweep collector. Java's garbage collector uses better algorithms. The collector never even looks at objects that are not referenced from the …

Actually, synchronization is not an escape. Objects can be stack-allocated in methods that do synchronization.

"Go compiles to native code. Java, ultimately, does too, but compilation happens at runtime, which is an overhead that Go doesn’t have, so in principle Go should be faster." Oh boy…

Poof! There goes finite automata, and therefore regular expressions. :-)

It's hard to say. The finalization spec is subtle. To make this work, the JIT would need to perform escape analysis on the finalizer too (since the finalizer can make an object esc…