3 ms·
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 f
by jshen 15y ago
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-your-permgen-space/ http://eigenjoy.com/2011/03/02/clojures-keyword-can-fill-up-...
- jes5199 15y agoruby (MRI ruby, even!) has that same bug.
- getsat 15y agoSo 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.
- gtani 15y agonot a bug, a known issue: interned strings aren't GC'd in python, erlang BEAM, many runtimes.
- SWengineer 15y agoJdk 7 puts interned Strings into the old generation instead of the permgen. Maybe give that a try.