Rails Rumble Winners - Gem Teardown
dwellable.com
Rails Rumble Winners - Gem Teardown
1–10 of 30 posts
Re: Rails Rumble Winners - Gem Teardown
#2I put this together yesterday, with help from the ten winning teams. It's kind of like the occasional HN post that looks at hosting decisions made by YC companies. Maybe I'm just a gems geek, but I find this sort of thing fascinating.
Re: Rails Rumble Winners - Gem Teardown
#3Very interesting information. Definitely going to have a look at a few gems after this. Thanks for sharing.
On a side note, HAML is the best example of technology for technologies sake. It adds a small amount of value while adding the complexity of a new language. I've never felt the "juice was worth the squeeze" so to speak. Curious as to why it has the following that it does.
Re: Rails Rumble Winners - Gem Teardown
#4Very interesting information. Definitely going to have a look at a few gems after this. Thanks for sharing. On a side note, HAML is the best example of technology for technologies sake. It adds a small amount of value while adding the complexity of a new language. I've never felt the "juice was worth the squeeze" so to speak. Curious as to why it has the following that it does.
Never making invalid markup is handy, and if you have easy access to attributes you can:
.a_class{ attrs } some text
some text
Re: Rails Rumble Winners - Gem Teardown
#5Very interesting information. Definitely going to have a look at a few gems after this. Thanks for sharing. On a side note, HAML is the best example of technology for technologies sake. It adds a small amount of value while adding the complexity of a new language. I've never felt the "juice was worth the squeeze" so to speak. Curious as to why it has the following that it does.
Never making invalid markup is handy, and if you have easy access to attributes you can: .a_class{ attrs } some text which can save a lot when you would otherwise have to write: some text The never-invalid markup is probably the bigger win, though. Primitive type checking for your HTML is arguably better than none. What I would really like is something similarly terse but faster - HAML can get pretty slow.
I cannot say I have had many problems with incorrect HTML. Since using HAML, I have had tabbing issues, inline javascript issues, a new syntax to learn (and translate). The last one is my main issue. 80% of your time spent with HTML is in the browser, the mental translation is more of a tax than anything.
I have used HAML on three projects and it always feels like it gets in the way more than it helps.
Re: Rails Rumble Winners - Gem Teardown
#6Very interesting information. Definitely going to have a look at a few gems after this. Thanks for sharing. On a side note, HAML is the best example of technology for technologies sake. It adds a small amount of value while adding the complexity of a new language. I've never felt the "juice was worth the squeeze" so to speak. Curious as to why it has the following that it does.
Never making invalid markup is handy, and if you have easy access to attributes you can: .a_class{ attrs } some text which can save a lot when you would otherwise have to write: some text The never-invalid markup is probably the bigger win, though. Primitive type checking for your HTML is arguably better than none. What I would really like is something similarly terse but faster - HAML can get pretty slow.
Re: Rails Rumble Winners - Gem Teardown
#7Very interesting information. Definitely going to have a look at a few gems after this. Thanks for sharing. On a side note, HAML is the best example of technology for technologies sake. It adds a small amount of value while adding the complexity of a new language. I've never felt the "juice was worth the squeeze" so to speak. Curious as to why it has the following that it does.
Never making invalid markup is handy, and if you have easy access to attributes you can: .a_class{ attrs } some text which can save a lot when you would otherwise have to write: some text The never-invalid markup is probably the bigger win, though. Primitive type checking for your HTML is arguably better than none. What I would really like is something similarly terse but faster - HAML can get pretty slow.
https://github.com/stonean/slim#benchmarks
Slim is mentioned in the writeup. It's faster than Haml. I like it better.
Re: Rails Rumble Winners - Gem Teardown
#8Nice breakdown. Just a critique, I'm willing to bet that people were using therubyracer to compile CoffeeScript.
Re: Rails Rumble Winners - Gem Teardown
#9Rats. I was rooting for Uptilt:
Re: Rails Rumble Winners - Gem Teardown
#10Nice 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.