Yammer moving from Scala to Java

Re:Yammer moving from Scala to Java by jshen on Tuesday November 29, 2011 @08:22PM (#3293202)

I wrote a medium sized project in clojure at my last job and it was a good experience. The team was small (under 5) so the hiring and training wasn't an issue for us. I never had a problem reading clojure code, and the only major headache I can remember, which was our fault, was that clojure keywords (think ruby symbols) used to be turned into interned strings which are stored in permgen and we were running out of permgen space. I believe this has been fixed in recent versions of clojure, but I'm not 100% sure about that.

http://eigenjoy.com/2011/03/02/clojures-keyword-can-fill-up-...

[ Parent | on HN ]

Re:Yammer moving from Scala to Java by SWengineer on Wednesday November 30, 2011 @12:32AM (#3293894)

Jdk 7 puts interned Strings into the old generation instead of the permgen. Maybe give that a try.

[ Parent | on HN ]

Re:Yammer moving from Scala to Java by jes5199 on Tuesday November 29, 2011 @11:33PM (#3293736)

ruby (MRI ruby, even!) has that same bug.

[ Parent | on HN ]

Re:Yammer moving from Scala to Java by getsat on Wednesday November 30, 2011 @04:20AM (#3294381)

So does Erlang, but it's not really a bug. Symbols (atoms, whatever) are guaranteed to be a unique identifier, so the fact that they're allocated and exist for the duration of execution isn't really surprising.

It's just something you need to be aware of.

[ Parent | on HN ]

Re:Yammer moving from Scala to Java by gtani on Wednesday November 30, 2011 @04:41AM (#3294434)

not a bug, a known issue: interned strings aren't GC'd in python, erlang BEAM, many runtimes.

[ Parent | on HN ]