People still use Rails?
Yes. Thousands and thousands of engineers still use Rails to be produce valuable web applications and APIs. For a large number of use cases, there is little benefit to moving to a different stack.
Modern Front-end in Rails
21–30 of 150 posts
Re: Modern Front-end in Rails
#22This website is total crab on my Laptop. The font is huge and zooming with ctrl +/- doesn't work (firefox 57).
Edit: Sorry for my harsh words. I just get kinda angry when I come across websites that don't allow me to zoom in or out, especially when the default font size is way off the standard.
Re: Modern Front-end in Rails
#23Honestly, as a Rails dev, this just seems more complicated than creating a Rails app in API mode and using #{React||Vue||Ember}} for the front-end. It's extremely easy to get started with a front-end app using vue-cli. This article spends a lot of time changing Rails' default functionality to achieve behavior similar to what vue-cli gives you by typing `vue init webpack` and answering a few questions. I understand th…
The downside there is that you're then forced to build your application as a completely separate service and static site. With this approach, you can stick single page app where the UI needs to be more stateful and then use traditional server-templating for other things. I'm doing this w/ phoenix now and its nice because my typeahead search is done as a JS component, but the corresponding index and show pages are still mostly the same as what was scaffolded.
Not to mention, the combined approach is 100% necessary if you are going to require a server render for your react||vue|ember stuff.
Re: Modern Front-end in Rails
#24Honestly, as a Rails dev, this just seems more complicated than creating a Rails app in API mode and using #{React||Vue||Ember}} for the front-end. It's extremely easy to get started with a front-end app using vue-cli. This article spends a lot of time changing Rails' default functionality to achieve behavior similar to what vue-cli gives you by typing `vue init webpack` and answering a few questions. I understand th…
Agree in principle, but any technique is frigthening at first. Clearly for the authors this is a usual workflow - they're productive with it, and they only had to pay the complexity cost once (when figuring out things). Once you get an integrated frontend-backend system and codebase, you start to get unique benefits: - Server-rendered data, for avoiding superfluous ajax requests - Simpler deployments (fewer moving pi…
To your first point, you can still server side render if you use an API by serving your frontend through a server that fetches data from the API before rendering
Re: Modern Front-end in Rails
#25This is precisely what was always wrong with the “Rails philosophy”. Front end should be completely independent to any kind of backend. The level of integration proposed here is an absolute nightmare to maintain and extend.
Re: Modern Front-end in Rails
#26This is precisely what was always wrong with the “Rails philosophy”. Front end should be completely independent to any kind of backend. The level of integration proposed here is an absolute nightmare to maintain and extend.
It’s not just a backend, Rails is a full stack framework - from database administration to data modeling, business logic to frontend. It literally has built in frontend templating in the form of erb.
That said, I think that frontend development has evolved into a place where frontend development is better done separately. As part of its evolution, Rails integrated Rails API and can be configured minimally to be a backend API only.
Re: Modern Front-end in Rails
#27Rails is still a truly incredible framework and it still moving very fast in terms of development. It’s front end stuff has always felt wrong to me and many others and we found weird ways to doing what we wanted. Rails 5 added support for a lot of them as the article points out but it still feels complicated. Rails is awesome bc it’s opinionated but the fact that it’s ruby still lets you do what you want. I think rai…
The webpack integration coming in Rails 5.2 starts to do exactly what you suggest. We’ve had the beta in general use for weeks and I’d say the framework is going in the direction you want.
This article seems a bit of overengineering by comparison and isn’t representative of what’s new out-of-the-box.
Re: Modern Front-end in Rails
#28Looks like a solid approach. I'm going to try it out tonight.
Re: Modern Front-end in Rails
#29Honestly, as a Rails dev, this just seems more complicated than creating a Rails app in API mode and using #{React||Vue||Ember}} for the front-end. It's extremely easy to get started with a front-end app using vue-cli. This article spends a lot of time changing Rails' default functionality to achieve behavior similar to what vue-cli gives you by typing `vue init webpack` and answering a few questions. I understand th…
The downside there is that you're then forced to build your application as a completely separate service and static site. With this approach, you can stick single page app where the UI needs to be more stateful and then use traditional server-templating for other things. I'm doing this w/ phoenix now and its nice because my typeahead search is done as a JS component, but the corresponding index and show pages are sti…
>Not to mention, the combined approach is 100% necessary if you are going to require a server render for your react||vue|ember stuff
Why’s that?
Re: Modern Front-end in Rails
#30Honestly, as a Rails dev, this just seems more complicated than creating a Rails app in API mode and using #{React||Vue||Ember}} for the front-end. It's extremely easy to get started with a front-end app using vue-cli. This article spends a lot of time changing Rails' default functionality to achieve behavior similar to what vue-cli gives you by typing `vue init webpack` and answering a few questions. I understand th…
Agree in principle, but any technique is frigthening at first. Clearly for the authors this is a usual workflow - they're productive with it, and they only had to pay the complexity cost once (when figuring out things). Once you get an integrated frontend-backend system and codebase, you start to get unique benefits: - Server-rendered data, for avoiding superfluous ajax requests - Simpler deployments (fewer moving pi…
I'm in the middle of converting a small production Rails API + Ember app to Rails Views + Vue.js using webpacker and a lot of the techniques discussed. It's certainly been a learning curve, but I'm definitely happier with the new setup for all of the reasons you mentioned.
It's not a one-size-fits-all solution, but for a single dev / small team working on a web-only application it can make a lot of sense.
For anyone interested, Gorails has a series on Vue + Rails that's been very helpful. https://gorails.com/series/using-vuejs-with-rails