I'm an organiser of Rumble. If the writers are reading this, I am sure we could try and work out more if they ever want to play with more metrics. :)
Rails Rumble Winners - Gem Teardown
11–20 of 30 posts
Re: Rails Rumble Winners - Gem Teardown
#12Nice breakdown. Just a critique, I'm willing to bet that people were using therubyracer to compile CoffeeScript.
Yes, I recognize that. Perhaps I didn't explain it clearly in the post. Nine of the teams used coffeescript, but only six used therubyracer. What did they use for js if not therubyracer? I'm guessing node.
Edit: 9=>6 per the blog post
Re: Rails Rumble Winners - Gem Teardown
#13This is great. I am putting my own list of gems from all the participants, I will list it once done.
Re: Rails Rumble Winners - Gem Teardown
#14Why is beanstalk often looked over? Has anyone ha problems with it before? Or is it just marketing problems..
Re: Rails Rumble Winners - Gem Teardown
#15Nice breakdown. Just a critique, I'm willing to bet that people were using therubyracer to compile CoffeeScript.
Actually, the twitter-bootstrap-rails[1] gem requires therubyracer[2] in order to compile LESS -> CSS. [1] https://github.com/seyhunak/twitter-bootstrap-rails [2] https://github.com/cowboyd/therubyracer
It depends on how you integrate bootstrap: there's a SCSS conversion of Bootstrap that avoids the dependency on therubyracer, (it just requires sass):
https://github.com/anjlab/bootstrap-rails
Re: Rails Rumble Winners - Gem Teardown
#16I'm an organiser of Rumble. If the writers are reading this, I am sure we could try and work out more if they ever want to play with more metrics. :)
Author here. Sounds like fun, drop me an email (in my profile).
Re: Rails Rumble Winners - Gem Teardown
#17jquery and bootstrap are great for putting together a rails app really quick, but I wish there was a better way that didn't add bloat. I find that jquery and bootstrap add significant download latency to a webpage even if they are gzipped.
Re: Rails Rumble Winners - Gem Teardown
#18Why is beanstalk often looked over? Has anyone ha problems with it before? Or is it just marketing problems..
The collaboration and navigation tools of Beanstalk are not up to par, last I checked. The file browsers on GitHub and Bitbucket are very responsive. The "pull request" feature is extremely useful for managing large teams where features are being developed concurrently. Beanstalk's best feature is its automatic deployment, but you can duplicate this in a more powerful way with post-commit hooks or continuous integration processes.
Re: Rails Rumble Winners - Gem Teardown
#19Why is beanstalk often looked over? Has anyone ha problems with it before? Or is it just marketing problems..
The collaboration and navigation tools of Beanstalk are not up to par, last I checked. The file browsers on GitHub and Bitbucket are very responsive. The "pull request" feature is extremely useful for managing large teams where features are being developed concurrently. Beanstalk's best feature is its automatic deployment, but you can duplicate this in a more powerful way with post-commit hooks or continuous integrat…
Ah, sorry about that, I meant beanstalkd, the work queue.
Re: Rails Rumble Winners - Gem Teardown
#20Isn't Devise older than OmniAuth?