What do you think about integrating https://github.com/charliesome/better_errors directly into rails?
Good suggestion!
Ask HN: What do you want to see in Rails 4.1?
11–20 of 94 posts
Re: Ask HN: What do you want to see in Rails 4.1?
#12Replace turbolinks with pjax.
Considering dhh created Turbolinks specifically to improve upon PJAX, I think we both know how likely that idea is. Thanks for the suggestion though!
Re: Ask HN: What do you want to see in Rails 4.1?
#13Please finish https://github.com/rails-api/active_model_serializers according to http://jsonapi.org/ and distribute it officially with Rails 4.1
Re: Ask HN: What do you want to see in Rails 4.1?
#14What do you think about integrating https://github.com/charliesome/better_errors directly into rails?
It's a super neat gem. Improving error pages is always a good idea, I'm actually really happy with the relatively minor changes we added in 4.0, so I could totally see this or something like it, thanks.
Re: Ask HN: What do you want to see in Rails 4.1?
#15Unicorns, ponies and rainbows please.
Why would you want unicorns AND ponies? unicorns are superior to ponies; adding them both would just bloat the framework.
Re: Ask HN: What do you want to see in Rails 4.1?
#16* Improved migration format:
make it possible to create new initial migrations as a project evolves by rebasing. Meaning there's no need to keep or execute the whole migration history every time. On my current project running migrations from starch takes 30mins :(
* Improvement in performance in regarding to JSON generation or other thing is always welcome. following benchmarks can be taken as reference where rails stands currently. Any improvement in the above stats would be awesome http://www.techempower.com/benchmarks/#section=data-r6
Re: Ask HN: What do you want to see in Rails 4.1?
#17Thanks for asking Steve! I think Rails is already very complete. I would like to see an included state machine, rails-api integration, commands (baby-zeus) integration and GitLab secret storage ( https://github.com/gitlabhq/gitlabhq/pull/4040 ). But I realize these are all very controversial. The most important thing is the core-team stays happy, so no problem if these can't make it.
I would love for Rails to address keeping secrets/tokens out of source control by default - so every project can do it easily in the same way
Re: Ask HN: What do you want to see in Rails 4.1?
#18Please finish https://github.com/rails-api/active_model_serializers according to http://jsonapi.org/ and distribute it officially with Rails 4.1
AMS is currently undergoing a major internal refactoring, possible even a near re-write, but getting it in line with what's up at JSON-API is real important. Also, ember-data is undergoing a major push this month, so while this is in flux, it should improve soon.
As for getting it into core Rails, well, considering it was originally pulled out, I wouldn't hold your breath, as much as I'd prefer that personally.
Re: Ask HN: What do you want to see in Rails 4.1?
#19Hey 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. Sort of like how engines work: main_app.users_path is IMO better than users_path.
* I guess instance variables in views are a given forever, but I still don't like them. Why can't these be simple methods on objects as well? Simplify, simplify, simplify. Also, deprecate helpers. (Hey, I can dream!)
* I would help if my app was defined as a (singleton) class that I can see and use somewhere. It would be better if this were always a Gem, without me doing anything special. Then I could make all kinds of gem dependencies explicit.
* Fix mailers to allow them to work with async delivery out of the box. (Bringing back queues? Yes please!)
* Make mailers work with Markdown and friends to produce multipart emails out of the box. Write a pretty(ish) plaintext mail, and get HTML formatted for free. (There are gems for this, it would be nice if it were standard)
* 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!
* Fix the log file format. One line per event would be nice. Proper timestamps would be nice. Use standard Ruby loggers with a good format that the rest of the industry understands.
Re: Ask HN: What do you want to see in Rails 4.1?
#20Thanks for asking Steve! I think Rails is already very complete. I would like to see an included state machine, rails-api integration, commands (baby-zeus) integration and GitLab secret storage ( https://github.com/gitlabhq/gitlabhq/pull/4040 ). But I realize these are all very controversial. The most important thing is the core-team stays happy, so no problem if these can't make it.
What is baby-zeus?
I'm personally very interested in the secret_token issue, and so is the rest of the team, but it's tricky to get the balance right. Working on it!