Live data from Hacker News

Go GC: Solving the Latency Problem in Go 1.5

sourcegraph.com

131–132 of 132 posts

Re: Go GC: Solving the Latency Problem in Go 1.5

#131
post #127

Earlier quoted context omitted.

Yes, Java developers still hand code their getters and setters. What era are you from, again? Also, those "brain dead" Java developers still write code that smoke your dog slow Python code regardless of how meticulously you hand crafted your code. So yeah, I would be bitter too.

> What era are you from, again? Uh, the one following hordes of brain-dead Java developers hand-coding getters and setters? > Also, those "brain dead" Java developers still write code that smoke your dog slow Python code regardless of how meticulously you hand crafted your code. And is delivered 2 years later, requires 5 times more people and costs 10 time more to develop. And Python can be plenty fast if you use the…

>Uh, the one following hordes of brain-dead Java developers hand-coding getters and setters?

I can only image what they think of you and it's probably not very good. You must be a nightmare to work with and be around. Which is probably why they keep you away from people.

>And is delivered 2 years later, requires 5 times more people and costs 10 time more to develop. And Python can be plenty fast if you use the right libraries.

Sounds very anecdotal. This seems to be your modus operandi. I could say the same thing about worthless Python developers. No wonder that language is in decline and seldom used in the enterprise.

>What do I have to be bitter about? I get paid well to write Python, C and Go on bespoke and interesting back-end systems and don't have to attend daily stand-ups with brain-dead Java developers and Oracle DBAs and listen to them duke it out over who's fault it is queries are running slow. No thanks.

Again with the idiotic anecdotes. You must have been exposed to a work environment that was not congruent to that of your own, but somehow think it's the blueprint. But, make no mistake, you are a bitter man and if Java contributed to that then I'm thankful for its existence.

Re: Go GC: Solving the Latency Problem in Go 1.5

#132
post #87

Earlier quoted context omitted.

I think the advantage of ARC is not the potential for longer pause times but the fact that things are predictable & somewhat easier to debug. I think it's too bad that the GC/ARC choice also implies a language choice. For e.g. if we had the ability to choose between GC & ARC in Java, we would be able to get a better understanding of which memory model developers of Java enterprise software end up preferring.

There are JVMs with RC, http://users.cecs.anu.edu.au/~steveb/downloads/pdf/rcix-oops...

Very interesting, thanks for sharing.

Often, the problem with this kind of academic work is that they don't have a real world system to gather data and study different algorithms. I don't really care if javac (one of the application they benchmark) takes 10% more or less time. I want to know how much time engineers save when using ARC vs tracing GC over a long period of time (development + maintenance).

Post reply on HN