2 ms·
inherited a grails codebase from a team who mostly hated groovy/java, and tried to recreate rails/ruby in almost all the code. all external supporting librarie
by mgkimsal 10y ago
inherited a grails codebase from a team who mostly hated groovy/java, and tried to recreate rails/ruby in almost all the code. all external supporting libraries and tools were ruby, and it had more than a few "groovy sucks because it's not ruby" comments scattered around. Apparently just the top CTO guy there liked grails, started the project, brought on people, but they all hated it. and built a massive monstrosity that was neither idiomatic ruby, groovy or java. :/
- vorg 10y ago> a team who mostly hated groovy/java Sounds like they hated Java rather than specifically Apache Groovy, which is really a scripting language for systems already built with Java code.
- mgkimsal 10y agoprobably a bit of both, but the bulk of the code (grails code) was almost all groovy, and there was enough complaints about how 'slow' groovy was that there was some groovy-specific hate going on as well. Granted, especially then, groovy wasn't the fastest around, but for most of what was being done, it wasn't a bottleneck (and... ruby at that point wouldn't have been any faster - there was some prototypal stuff in ruby to try to make some processing faster, and it wasn't).