3 ms·

Is anyone still developing multi-page architecture apps? Seems like you could still develop simple applications a multiple of times faster with Ruby on Rails or

by jetsnoc 10y ago

Is anyone still developing multi-page architecture apps? Seems like you could still develop simple applications a multiple of times faster with Ruby on Rails or Django and sprinkle in Angular and/or AJAX Requests as needed. Surely that is still a thing. I know that a lot of you are all engineering for Netflix scale but developing two independent applications that speak to each other over an API spec sure has it's costs and is a drag on a small scrappy team wanting to iterate quickly.

jaredklewis 10y ago
I spent a long time developing traditional rails apps. Today I spend most of my time on SPAs, and that I can tell, development time is similar. Of course the first few SPAs took much longer while I learned things and the ecosystem built up, by today, I feel equally comfortable.
- jetsnoc 10y ago
  If you can get the time to develop the software to be similar with all of the benefits of a SPA, that is hard to ignore. Any recommendations on how to make this a reality?
szastupov 10y ago
It totally depends on task at hand. If you have a db/forms heavy project than Rails/Django gives you advantage, if your project is more driven by interactions and subtle UX then SPA lets you focus on that. Like, imagine how hard it would be to make Shopify as SPA (https://engineering.shopify.com/17489056-rebuilding-the-shopify-admin-improving-developer-productivity-by-deleting-28-000-lines-of-javascript https://engineering.shopify.com/17489056-rebuilding-the-shop...). On the other hand, Trello would never feel so fluid if it was driven by server rendering (notice how weird Github projects comparing to Trello). Personally, I've been doing SPA for years and think it's the right way for reach UI. But recently I had to build a form-heavy app and decided to go with classical server-side setup + some jQuery on client. Old school but very productive. EDIT: added link to shopify blog.
- jetsnoc 10y ago
  Of course, right tool for the job. I'm biased since most of our projects are heavy on crud forms and database entry. Accounting and loyalty space.

by jetsnoc 10y ago

jaredklewis 10y ago

I spent a long time developing traditional rails apps. Today I spend most of my time on SPAs, and that I can tell, development time is similar. Of course the first few SPAs took much longer while I learned things and the ecosystem built up, by today, I feel equally comfortable.

jetsnoc 10y ago
If you can get the time to develop the software to be similar with all of the benefits of a SPA, that is hard to ignore. Any recommendations on how to make this a reality?

szastupov 10y ago

It totally depends on task at hand. If you have a db/forms heavy project than Rails/Django gives you advantage, if your project is more driven by interactions and subtle UX then SPA lets you focus on that. Like, imagine how hard it would be to make Shopify as SPA (https://engineering.shopify.com/17489056-rebuilding-the-shopify-admin-improving-developer-productivity-by-deleting-28-000-lines-of-javascript https://engineering.shopify.com/17489056-rebuilding-the-shop...). On the other hand, Trello would never feel so fluid if it was driven by server rendering (notice how weird Github projects comparing to Trello). Personally, I've been doing SPA for years and think it's the right way for reach UI. But recently I had to build a form-heavy app and decided to go with classical server-side setup + some jQuery on client. Old school but very productive. EDIT: added link to shopify blog.

jetsnoc 10y ago
Of course, right tool for the job. I'm biased since most of our projects are heavy on crud forms and database entry. Accounting and loyalty space.