| I can only shake my head in disbelief when I heard Rails or Django developers touting their framework and saw their actual codebase (ever see FatCRM codebase back in the days? it has been improved significantly these days, but it used to be ... hard to read). I even shake my head faster when I read the split in opinions in Rails world: the Rails DHH and the DCI/Service Rails. Moreover, I keep shaking my head when the Django and Rails community voiced their complain over their so-called bloated framework just because they want an API service. Last but not least, I shake my head again whenever I heard that Django and Rails is not like NodeJS. C'mon guys... you guys speak a lot of bad things about JAVA yet you've become Java Enterprise Edition. I suppose JavaEE (especially 6 and 7) does work better in terms of writing maintainable code. Stuff like Service pattern, Repository pattern, Data mapping pattern, DTO, Value Objects, Mocking are pretty much "common" in most Java projects I've seen or worked on. I felt that no matter how cool Rails and Django are, when it comes to medium-to-large codebase, Rails/Django are definitely either following the patterns that pretty much common in JavaEE or may not be so comfortable to use anymore. |