Unicorns, ponies and rainbows please.
Unicorns and God for me.
Ask HN: What do you want to see in Rails 4.1?
41–50 of 94 posts
Re: Ask HN: What do you want to see in Rails 4.1?
#42rails package - dockerization of app, but this rather goes beyond of responsibilities of Rails and I should complain at capistrano guys ;-)
True, that's sorta outside of the scope of the framework.
Re: Ask HN: What do you want to see in Rails 4.1?
#43* 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…
+1 for this. My team "rolls up" migrations akin to spring cleaning, because the migration files often have more important information that the db schema, and are easier for team members to learn quickly. I'll contribute $50 if this feature is accepted for Rails 4.1.
Re: Ask HN: What do you want to see in Rails 4.1?
#44I'd love to see a move away from the activerecord model, towards a datamapper / mongoid / declared format. It just makes more sense in multiple ways Some defaults for: queueing background jobs timers Will come back at this tomorrow.
Background jobs are something we explicitly punted from 4.0 with the intention of 4.1, so hopefully this will happen.
Thanks!
Re: Ask HN: What do you want to see in Rails 4.1?
#45I would love to see rails-api become a first-class player in the Rails ecosystem.
Re: Ask HN: What do you want to see in Rails 4.1?
#46I consult for a number of startups, both at seed stage and with significant revenue. Mostly I do web applications, as opposed to "sites."
I'm seeing more organizations learning towards frameworks like Ember.js and Angular.js. I'm also hearing lots of things like, "When I update the data in this browser, I want the changes to automatically propagate to other browsers."
Among other things, this means I need robust plugins like ember-rails that integrate into the asset pipeline and provide appropriate generators. I also need libraries similar to Socket.io that can notify the browsers when the model changes.
I don't necessarily want these features to be in the Rails 4.1 core. But I suspect that I'll be building more and more apps like this over the next two years, and I'd love to see Rails be a strong competitor on the back end.
Re: Ask HN: What do you want to see in Rails 4.1?
#47* 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…
+1 for this. My team "rolls up" migrations akin to spring cleaning, because the migration files often have more important information that the db schema, and are easier for team members to learn quickly. I'll contribute $50 if this feature is accepted for Rails 4.1.
> I'll contribute $50 if this feature is accepted for Rails 4.1.
Oh yeah? I wonder if others would also pay for bug bounties.
Re: Ask HN: What do you want to see in Rails 4.1?
#48Minitest 5. I'm getting great results with Minitest Spec.
Re: Ask HN: What do you want to see in Rails 4.1?
#49Thanks for asking!
Are queues ready for prime-time yet?
Another vote for async mailers please - also sending more than one mail at once would be nice.
Sorting out secret_token.rb would be good - not sure what would work, ENV variable, auto-generating a file in production if not there, but there must be a better solution which lets you work both on Heroku and let's people avoid having secrets stored in version control by default.
Also, I know this has been a really thorny issue in the past, but the thing I add first to every single app I make is authorisation and authentication. Usually I use devise and cancan, but it'd be great to just have default rails generators for this - they could be very basic, just covering the most basic use-cases, and would obviously have to be optional. Not everyone would use them, but it would at least help a lot of beginners avoid mistakes like this:
https://www.computerworld.com/s/article/9186579/Facebook_wan...
and it would also provide guidelines for people on how to approach those topics - at present they'll tend to google a solution. That would help to emphasise that you need both of these things separately, and give us a baseline from which more complex bespoke solutions could easily be built.
Re: Ask HN: What do you want to see in Rails 4.1?
#50I wish there was some way to call the asset pipeline with parameters. E.g. "render that stylesheet with the dark theme".
How would this be an improvement over setting environment variables?