3 ms·

As someone who is just now learning Rails, I'm loving it. Is this an actual issue that should push me away from the technology? What other technologies are th

As someone who is just now learning Rails, I'm loving it. Is this an actual issue that should push me away from the technology? What other technologies are there that streamline the development process as much as rails?

tmo9d 14y ago
No, please don't let this article affect your experience with Rails. Rails is awesome. It is. It's a great framework to learn and the problems that the author of this piece was discussing are really just a critique of his own faults. He made some awful decisions about architecture and framework and now he's paying the price. Ignore this idiot and continue on. Also, I wrote the original piece.
static_typed 14y ago
If you love constant patching for the daily critical security holes, stick with Rails. If you love worrying where they have stuck yet another Yaml parser, and where else they are eval-ing user supplied data, stick with Rails. If you prefer a bit of an easier, less-stressful life, there is hope with many of the Perl, Python and PHP frameworks.
- squidsoup 14y ago
  Like the Django patch that was released yesterday? (https://www.djangoproject.com/weblog/2013/feb/19/security/ https://www.djangoproject.com/weblog/2013/feb/19/security/) The fact that the Rails team quickly responds to vulnerabilities should be reassuring not a disincentive to use the framework. All software is subject to vulnerabilities - the recent issues with YAML are a class of exploit common across many frameworks in different ecosystems (Django's TastyPie had a similar issue in the past).
  - static_typed 14y ago
    Yes, Django took a solid step to properly fix the underlying issue, rather than apply many small sticky-plasters over several days instead, leaving the same basic vector open in the meantime. In fact, the Django issue reported was posted on HN yesterday and the comments on that posting underline what I just said here. Remember - Python for Pros, Ruby to pose.
    - slurgfest 14y ago
      I'm a big Python fan but that closing remark is just an incredibly obnoxious thing to say and is only going to feed the Python haters

tmo9d 14y ago

No, please don't let this article affect your experience with Rails. Rails is awesome. It is. It's a great framework to learn and the problems that the author of this piece was discussing are really just a critique of his own faults. He made some awful decisions about architecture and framework and now he's paying the price. Ignore this idiot and continue on. Also, I wrote the original piece.

static_typed 14y ago

If you love constant patching for the daily critical security holes, stick with Rails. If you love worrying where they have stuck yet another Yaml parser, and where else they are eval-ing user supplied data, stick with Rails. If you prefer a bit of an easier, less-stressful life, there is hope with many of the Perl, Python and PHP frameworks.

squidsoup 14y ago
Like the Django patch that was released yesterday? (https://www.djangoproject.com/weblog/2013/feb/19/security/ https://www.djangoproject.com/weblog/2013/feb/19/security/) The fact that the Rails team quickly responds to vulnerabilities should be reassuring not a disincentive to use the framework. All software is subject to vulnerabilities - the recent issues with YAML are a class of exploit common across many frameworks in different ecosystems (Django's TastyPie had a similar issue in the past).
- static_typed 14y ago
  Yes, Django took a solid step to properly fix the underlying issue, rather than apply many small sticky-plasters over several days instead, leaving the same basic vector open in the meantime. In fact, the Django issue reported was posted on HN yesterday and the comments on that posting underline what I just said here. Remember - Python for Pros, Ruby to pose.
  - slurgfest 14y ago
    I'm a big Python fan but that closing remark is just an incredibly obnoxious thing to say and is only going to feed the Python haters