“Start Rails 5 development”
github.com
“Start Rails 5 development”
1–10 of 67 posts
Re: “Start Rails 5 development”
#2Is there a good summary of the main goals of taking Rails from 4 to 5?
Re: “Start Rails 5 development”
#3I think it's shipping with its own background processor, Active Jobs. Sounds good!
Re: “Start Rails 5 development”
#4I think it's shipping with its own background processor, Active Jobs. Sounds good!
Re: “Start Rails 5 development”
#5I think it's shipping with its own background processor, Active Jobs. Sounds good!
Re: “Start Rails 5 development”
#6Is there a good summary of the main goals of taking Rails from 4 to 5?
Re: “Start Rails 5 development”
#7I'm curious about the fate of Rails(and other frameworks like Django) in a few years, seeing that many web applications are moving to the Single-Page-Application model and the server simply acts as a rest backend.
Perhaps there will still be a large demand for sites that aren't SPA applications. Interesting times.
Re: “Start Rails 5 development”
#8I'm curious about the fate of Rails(and other frameworks like Django) in a few years, seeing that many web applications are moving to the Single-Page-Application model and the server simply acts as a rest backend. Perhaps there will still be a large demand for sites that aren't SPA applications. Interesting times.
I really don't think SPAs are very common, though following news of what's hot wouldn't suggest that. Honestly, I'd bet 95% of all web apps being built every day are traditional full request/response apps.
Re: “Start Rails 5 development”
#9I'm curious about the fate of Rails(and other frameworks like Django) in a few years, seeing that many web applications are moving to the Single-Page-Application model and the server simply acts as a rest backend. Perhaps there will still be a large demand for sites that aren't SPA applications. Interesting times.
I think you really need to differentiate between web applications and websites. Websites still are a lot better off with primarily static websites in terms of SEO and performance (caching static pages is easier). For web applications a SPA approach definitely has advantages; for the biggest part in usability. Given that a vast majority of content on the web are pretty plain websites I'm sure Rails will stay relevant for quite a while longer.
Re: “Start Rails 5 development”
#10I'm curious about the fate of Rails(and other frameworks like Django) in a few years, seeing that many web applications are moving to the Single-Page-Application model and the server simply acts as a rest backend. Perhaps there will still be a large demand for sites that aren't SPA applications. Interesting times.
> Perhaps there will still be a large demand for sites that aren't SPA applications. Interesting times.
It's isnt perhaps,99% of websites outthere arent SPAs.I'm pretty sure a majority of website you visit arent either.
> I'm curious about the fate of Rails(and other frameworks like Django) in a few years, seeing that many web applications are moving to the Single-Page-Application model and the server simply acts as a rest backend.
Why would you need a different framework for a "rest-backend" and a website that displays html? I dont understand.I pretty sure Rails has a "content negociation" like feature when it comes to json,xml,or html content types.