Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I Miss Rails

chanind.github.io

Post reply on HN
Print view View original

291–300 of 522 posts

Re: I Miss Rails

#291

Post by clairity »

inapis wrote: post #151
strken wrote: post #136

Earlier quoted context omitted.

Blaming complexity on React is a bit like blaming complexity on ERB. The problem isn't React, the problem is the massive hole where React doesn't have an opinion. React improves the area around the hole so much that the technologies we use to fill the void look obviously deficient in comparison.

This is actually the bane of JS community's existence. JS developed so fast and so wildly that there was never a breather to form and write down best practices or opinions. This is jarring to someone coming from the Rails world where a lot of magic is happening, there are strict opinions (heck, it's in the subtitle of the copy) and strict conventions to adhere too. JS is wild west compared to that. This is not to say…

> “...JS developed so fast and so wildly that there was never a breather to form and write down best practices or opinions.”

js and ruby were released in 1995, with rails coming 10 years later. so js development wasn’t fast in the least. after the little ajax blip resulting from outlook web access’s release in 98, js stagnated until node came along and made it interesting again.

prototype/jquery a little before it and later front-end frameworks like backbone, ember and then angular helped cement js as a thing. it only seems fast and wild because the ecosystem really only woke up again in the 2010s.

(i tooled around with js on netscape right after it came out but then lost interest)

Re: I Miss Rails

#293

Post by piyushpr134 »

I think one big mistake rails did was to tightly couple view side with server side. This made sure tight coupling. If rails had a layer in between controller and html (with a dumber html templating), with this middle layer either spitting html or json apis, we would not need to get rid of rails

I too find react etc too complicated for a simple crud kind of app. Rails was much faster to achieve the same.

Re: I Miss Rails

#294

Post by Spiritus »

0xADEADBEE wrote: post #109
dbrgn wrote: post #46

Earlier quoted context omitted.

Django has multiple good asset handling libraries. I like https://django-pipeline.readthedocs.io/ . And with django-channels ( https://channels.readthedocs.io/ ) Django goes way beyond just WebSockets. You can now do fully asynchronous data processing pipelines. I'm still happy working with Django (which is not something I can say about the JS ecosystem). Especially when doing APIs with Django REST Framework.

Fully agree with you - been in the JS world a lot lately and it's not as polished as the more 'traditional' web frameworks. Channels was supposed to make core but never did - what happened there? That's what I was driving at really - if I were stewarding a modern web framework, I would be integrating websocket support. It never sat right with me that something as common as APIs is farmed out to a library in Django (t…

>Channels was supposed to make core but never did - what happened there?

https://www.djangoproject.com/weblog/2016/sep/09/channels-ad...

Re: I Miss Rails

#295

Post by Spiritus »

0xADEADBEE wrote: post #105
debuggerpk wrote: post #35

Earlier quoted context omitted.

for websockets, django has django-channels https://channels.readthedocs.io/en/latest/ . But I do agree, django has been a little late to this party.

What happened to bringing this into core? Last I was using Django that was the next big integration and it just sort of faded away.

https://www.djangoproject.com/weblog/2016/sep/09/channels-ad...

Re: I Miss Rails

#296

Post by tomschlick »

0xADEADBEE wrote: post #28
BillFranklin wrote: post #6

> if the modern equivalent of Rails already exists, please let me know! You're in luck. Rails 5.2.3 was released 20 hours ago. More seriously, I feel rails is still excellent and I'm happy to work with it every day. I'd be interested to hear more about what makes rails not modern? I find it a very productive framework. EDIT: If you're talking about missing a JS equivalent of rails, do you know about Loopback? https:/…

I know this is the opposite of what you asked but I find Rails to be keeping pace with modernity much better than its conemporaries! Django seem to have given up on integrating websockets (ActionCable has been in Rails for literally years now), nor is there trivial integration for JS assets/asset pipeline functionality. I don't write much of either anymore, but I'd still reach for Rails the instant I need to get some…

On the php side of things, Laravel is doing very well and is very "rails-esque".

Re: I Miss Rails

#298

Post by ileri62 »

0xADEADBEE wrote: post #28
BillFranklin wrote: post #6

> if the modern equivalent of Rails already exists, please let me know! You're in luck. Rails 5.2.3 was released 20 hours ago. More seriously, I feel rails is still excellent and I'm happy to work with it every day. I'd be interested to hear more about what makes rails not modern? I find it a very productive framework. EDIT: If you're talking about missing a JS equivalent of rails, do you know about Loopback? https:/…

I know this is the opposite of what you asked but I find Rails to be keeping pace with modernity much better than its conemporaries! Django seem to have given up on integrating websockets (ActionCable has been in Rails for literally years now), nor is there trivial integration for JS assets/asset pipeline functionality. I don't write much of either anymore, but I'd still reach for Rails the instant I need to get some…

Serious question: Django doesn't even have lazy loading. Why do people use it? Am I missing something? No way I'd wait a few seconds to get something big from the db

Re: I Miss Rails

#299

Post by [deleted] »

Spiritus wrote: post #294
0xADEADBEE wrote: post #109

Earlier quoted context omitted.

Fully agree with you - been in the JS world a lot lately and it's not as polished as the more 'traditional' web frameworks. Channels was supposed to make core but never did - what happened there? That's what I was driving at really - if I were stewarding a modern web framework, I would be integrating websocket support. It never sat right with me that something as common as APIs is farmed out to a library in Django (t…

>Channels was supposed to make core but never did - what happened there? https://www.djangoproject.com/weblog/2016/sep/09/channels-ad...

[deleted]

Re: I Miss Rails

#300

Post by nnain »

Spiritus wrote: post #294
0xADEADBEE wrote: post #109

Earlier quoted context omitted.

Fully agree with you - been in the JS world a lot lately and it's not as polished as the more 'traditional' web frameworks. Channels was supposed to make core but never did - what happened there? That's what I was driving at really - if I were stewarding a modern web framework, I would be integrating websocket support. It never sat right with me that something as common as APIs is farmed out to a library in Django (t…

>Channels was supposed to make core but never did - what happened there? https://www.djangoproject.com/weblog/2016/sep/09/channels-ad...

Andrew Godwin (creator of django-channels) has recently handed over the repo to other maintainers and moved on to some role on adding `async` support to Django Core. (Channels was officially adopted by the Django project, but isn't part of the Django-core — you still have to add the package separately.)

This async support is hopefully coming within 2019. I'm super-excited about using it in future django projects.

Post reply on HN