21–30 of 30 posts
Why is beanstalk often looked over? Has anyone ha problems with it before? Or is it just marketing problems..
That said, that was before Resque and Sidekiq existed. I now use Sidekiq for my new project since I'd rather not reinvent the wheel. I suspect most people think the same way.
Earlier quoted context omitted.
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.
But that comes from rather extended use, I'm definitely not claiming it's the best. There are plenty of things I dislike about HAML, but it does mean I read less, and I spend quite a bit of time reading and writing view code.
Mind if I ask if you've done PHP programming? If you have, ERB's <% would seem to be a tax you've already paid.
Earlier quoted context omitted.
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.
On a couple big projects, I've generally liked it - since there's less boilerplate (" " and closing tags in particular) and the primary identifying bits (- or %ul or .class) are at the far left of each line, I can generally read things more quickly and more easily than e.g. straight HTML or ERB's . But that comes from rather extended use, I'm definitely not claiming it's the best. There are plenty of things I dislike…
@{
// code
another example:
@user.Name
It feels very natural to write and is simple to read/pickup. Now that microsoft has open sourced it, someone should make a version in ruby. Might be a good side project for me actually :)
I'm glad I finally (mostly) have a grip on it all but boy did it take a while.
Why is beanstalk often looked over? Has anyone ha problems with it before? Or is it just marketing problems..
Why is beanstalk often looked over? Has anyone ha problems with it before? Or is it just marketing problems..
I used Beanstalkd for a few years and I can testify that it's an awesome piece of software. That said, that was before Resque and Sidekiq existed. I now use Sidekiq for my new project since I'd rather not reinvent the wheel. I suspect most people think the same way.
Rats. I was rooting for Uptilt: http://uptilt.r12.railsrumble.com/
Nine out of the ten winning teams wrote their JavaScript in CoffeeScript? Wow, that's pretty incredible -- I would never have expected it.
gem 'sass-rails'
gem 'coffee-rails'
gem 'jquery-rails'I 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.