Live data from Hacker News

Ask HN: What do you want to see in Rails 4.1?

news.ycombinator.com

91–94 of 94 posts

Re: Ask HN: What do you want to see in Rails 4.1?

#91

Hey Steve, great of you to ask! Here are some suggestions: * Streamline the command line. Why rake to migrate, but rails to generate a migration? I know, I know. But new folks to Rails do not know. And it would be better if there was just one tool that does it all. * Get rid of the global magic functions. users_path is nice and sweet, but where is it defined? Object? Kernel? Why can't I just call a method on my app.…

Get rid of all hardcoded tokens in source code. Especially the session secret. Require dotenv gem and move all config into ENV. Including the database configuration!

Better yet, make it as 12factor compliant as possible, out of the box.

Re: Ask HN: What do you want to see in Rails 4.1?

#92
post #28

Earlier quoted context omitted.

Considering dhh created Turbolinks specifically to improve upon PJAX, I think we both know how likely that idea is. Thanks for the suggestion though!

More realistically, commenting it by default would be IHMO a good idea. A friend of mine who currently learn rails and angular by himself got bitten by it. And angular is definitely not the only JavaScript framework / plugin that don't work well with Turbolinks. It's a very nice gem for some use cases but a terrible default.

I'd have to agree, having it on by default doesn't seem like such a good idea, omakase or not. There are tons of situations where using turbolinks spells trouble.

Re: Ask HN: What do you want to see in Rails 4.1?

#93

Thanks for putting this together Steve. Your work, and those of the Rails contributors is amazing stuff. I know this past year has been a pain from a security perspective but as a framework matures and adds n+ features, it is an inevitable outcome. For me, my wish list would be: - Down with helpers. Or, at least the ability to arbitrarily set them. Maybe push presenter as alternatives? - Some native performance tunin…

Thanks! I'm sure you know that I'm a big fan of presenters, maintaining one of the most popular gems that implements them, but they've generally been deemed a bit too heavy of a pattern in the past. What do you mean by 'arbitrarily set them'? There were performance tests, but nobody used them, so we pulled them out to a gem in 4.0. Can you give me an example of the eval problem? Not familliar with it.

Steve, thanks for following-up.

For point one, I mean that developers have free range with helper definitions and that they eventually find their way into controllers.

Interesting news about performance tests in The eval problem is as follows (typically if you have to eval something in a gem):

    class Foo 
It's not a big deal, just adds clutter. Thanks again!

Re: Ask HN: What do you want to see in Rails 4.1?

#94

1) Support minitest/spec with ActiveSupport::TestCase 2) Make rails indenpendent of testing framework, why should I case about minitst if I prefer rspec?

1) was specifically reverted by David, so that won't be happening. 2) How is it not agnostic now? What's the problem with just using rspec?

Regarding point 2), I don't think it is very agnostic though.

Because ActiveSupport::Testcase is extension of Minitest. Thus, rspec won't be able to use all helpers of AS. I am fully aware of there are rspec-rails with equivalent matchers.

Sadly, majority of commercial companies are now using rspec/rspec-rails for the dev job, this makes AS::TS a second-class citizen. So if we could not abstractify AS::TS, my vote is to extract it to a separate gem and let user choose the test framework they want.

Post reply on HN