HN user
Awesome. Let me know how it goes, please. :)
> The Hypermedia stuff is most exciting to me,
Me too. There's nothing concrete here yet, but there's lots of space to explore and good things to build. I really want us to be a leader in this space.
It's the exact same as Sinatra vs. Rails: build it all yourself vs. using a framework that has it built for you.
I've responded to your sibling.
Basically, as it stands, you have to put your {Ember,Backbone,..} app in `app/assets/javascripts/app/models`, for example, which is kinda crazy. I'd like to see JavaScript become an actual first-class citizen.
Also, the pipeline has been re-written for Rails 4, but historically it's been kinda slow and buggy.
For an example of what I'm thinking about, rake-pipeline-web is interesting.
The organization includes ActiveModel::Serializers, which is really important for giving you normalized JavaScript output. Rabl is slow and manual, which is the opposite of the Rails philosophy. Convention over Configuration wins every time.
The asset pipline isn't removed, so you don't need to do anything special.
That said, I don't think that it's ideal for heavy JS apps. Lots of possible work that could be done in this area.
Roger. I'll add one, thanks.
The problem with benchmarks is that they don't really correspond to reality. Your app is not a simple test app. Your site will not be running on my MacBook Air. Your users won't have the usage patterns my script does.
> Does the hypermedia support exist now, or is that a future goal?
Future goal. There's nothing at the moment, but it's a case that we're interested in. I'd love to talk about exactly what we need to do on the mailing list.
> Also, LOL at steveklabnik2 ;)
Yeah, steveklabnik would still be almost in top 100 to this day, I just looked. Sigh.
Thanks! Do you need something more than what's in the README[1], or do you mean I should have linked it from my post?
Awesome. Please let me know how I can help you build your apps more effectively.
So sorry about this. I was travelling back from Europe, and we had to coordinate between everyone who owned the various gems, so there was a bit of overlap there.
I hope to not be encouraging people to use HEAD soon.
It already is: https://github.com/rails-api/rails-api#for-new-apps
This is not a fork of Rails, it's just a set of plugins that work together nicely. Luckily, all the work on Rails 3 means that Rails is super modular, and it's easy to break off just the bits that you want. See Crafting Rails Applications[1] for more on this topic.