20 ms·
The post-Rails Ruby ecosystem is definitely a high-energy place where stability is traded for rapid development. Like any community it has its idiosyncrasies.
by dasil003 16y ago
The post-Rails Ruby ecosystem is definitely a high-energy place where stability is traded for rapid development. Like any community it has its idiosyncrasies. Rubyists compared to Pythonistas perhaps monkey patch a bit too much, are overly fond of novelty, and tend to have pretty strong yet sometimes objectively unsupportable ideas about the proper way to do testing.
All of these things have annoyed me from time to time over the past 5 years of working almost exclusively with Ruby. However the community also has its strengths which are extremely appealing for passionate programmers.
For one thing, the fact that Rails emphasizes improvement over maturity has made Rails 3 an amazingly modular framework, able to better fit enterprise requirements better than 2004's DHH ever would have wanted or acknowledged the need for. Also, consider the rise of the RSpec and Cucumber frameworks despite the fact that Test::Unit and Mocha already had the bases pretty well covered. In other communities, yes, you get better maintained libraries, but you also get stagnation from having too high a bar for new ideas. In Ruby you have to deal with constant deprecation, but at least you get better chances that your entire ecosystem won't be obsoleted by the next hot language or framework.
- Jd 16y agoIs a better fit a good fit?
- dasil003 16y agoWell, if you're asking about the ability of a language to prevent the ability of a corporate army of 1000 developers to blow it's collective foot off, then no, Ruby and almost every other language will forever pale in comparison to Java. On the other hand, if you're talking about the ability to mix, match, configure and replace components of Rails in order to meet your particular requirements, then Rails 3 shows real promise, though it's not yet officially released and a lot of the modularity needs battle-testing.
- jrockway 16y agomodularity needs battle-testing Don't worry, the Perl and Python web frameworks have been doing this for years, and it works great.
- dasil003 16y agoI'm confused, are you suggesting that Rails 3 architecture is influence by Perl and Python frameworks? Or are just talking about modularity in general? Because I was just talking about Rails 3 getting out in the wild and people getting to actually start using it with heavy customization to shake out some of the bugs. The re-archtecting to this point is quite impressive, but it's still living in a bit of a vacuum.
- jshen 16y ago"Well, if you're asking about the ability of a language to prevent the ability of a corporate army of 1000 developers to blow it's collective foot off, then no, Ruby and almost every other language will forever pale in comparison to Java." This is the common wisdom about java, but I don't think it's true. I have a far harder time dealing with other peoples java code than I do dealing with other people's ruby code. And yes, I work in a corporate army that happens to do both java and ruby. Libraries change over time. In java, if you realize your interface needs to change then you're fucked if someone else is using your code. If you're using someone else's code and it doesn't do exactly what you need it to do then in java you have to get their code, change it, compile your own custom version, and in many java shops upload it to your companies maven repo with some version like foo-lib.jshens-fork-1.0.1. In ruby you'd just monkey patch it. This has it's risks, but those risks are under your control, you don't have to ask someone else for a favor to update their lib. (using other people's monkey patching is a different animal) Spring, need I say more? In our corporate army there are 1000's of developers with 1000 page tomes telling them how to glue their libraries together in java. Think about that for a minute. Some of the "problems" that java doesn't have are really still there. They're just pushed into things like maven, ant, and spring. At the end of the day, bad java code makes my life much harder than bad ruby code. On a side note, what's up with the recent spate of people complaining about rails because they used some shitty library that isn't a part of rails? Here's a hint, you should do some due diligence before using some random library.
- dasil003 16y agoThis may well be true. I don't have any corporate Java experience. However I do believe from my limited Java experience that it's nearly impossible for a bug to occur that the average programmer can not trace back to it's source using more less standard methods (race conditions and other concurrency nastiness notwithstanding). In Ruby on the other hand, real head scratchers can and do occur on a regular basis that require a higher level of debugging skill than some mass-educated code monkeys are capable of.
- jshen 16y agoIt's just a different way of doing it. In java you ctrl-b your way into method calls using your IDE. In ruby (assuming it's not C code or eval'd code) you use ruby-debug. Set a break point and start stepping. In minutes you'll stop scratching your head. I've seen the "code monkeys" you speak of hit a brick wall with spring. Java the language simply pushes these problems into it's tools. I've spent countless hours getting my java tools to play nice. I don't have that problem in ruby. There really is a law of conservation here.