Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 94 posts

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

#31

Post by steveklabnik »

tilsammans wrote: post #19

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.…

* the tension between 'rails' and 'rake' has always been there, and I see it trip up beginners. There is a gem that sorta does this, I'll give this some thought.

* Making apps no longer a singleton has been happening on master already, so expect to see a bunch of that.

* I like multipart emails too, since I prefer plaintext emails.

* Working on the tokens issue, I already commented about it elsewhere in this thread.

* As of Rails 4, you can slip in your own Logger, so this is pretty easy to customize if we don't change anything.

* Queues were explicitly brought back to 4.1, that's a feature that we (and I, maintaining Resque) really want to get in.

Thanks! <3

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

#32

Post by sytse »

steveklabnik wrote: post #18
thepumpkin1979 wrote: post #13

Please 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.

Thanks for commenting, good to hear Ember compatibility is also in scope.

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

#34

Post by [deleted] »

steveklabnik wrote: post #20
sytse wrote: post #10

Thanks 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!

[deleted]

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

#35

Post by sytse »

steveklabnik wrote: post #31
tilsammans wrote: post #19

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.…

* the tension between 'rails' and 'rake' has always been there, and I see it trip up beginners. There is a gem that sorta does this, I'll give this some thought. * Making apps no longer a singleton has been happening on master already, so expect to see a bunch of that. * I like multipart emails too, since I prefer plaintext emails. * Working on the tokens issue, I already commented about it elsewhere in this thread.…

Yey for bringing queues back!

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

#39

Post by cheald »

gary4gar wrote: post #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 s…

The oj gem helps json generation a ton. The circular reference checks are still slow though.

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

#40

Post by cheald »

gary4gar wrote: post #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 s…

The oj gem helps json generation a ton. The circular reference checks are still slow though.
Post reply on HN