News for hackers. Stuff that matters.

A comment on Overview Of Upcoming Rails 7.1 Features Part 1. Parent comment

Re:Overview Of Upcoming Rails 7.1 Features Part 1 by kshahkshah on Tuesday December 20, 2022 @10:38AM (#34067368)
I love TypeScript, but Rails has a wonderful ecosystem of libraries that just feels unbeatable for the backend. For some reason (hot take incoming) the JS community seems to hate working with each other and improving existing libraries. The Ruby community seems to rally around improving our libraries (gems) rather than reinventing them every year.
[ Parent | on HN ]
Re:Overview Of Upcoming Rails 7.1 Features Part 1 by stevebmark on Tuesday December 20, 2022 @11:20AM (#34068033)
I take it you’ve never tried to install nokogiri?
[ Parent | on HN ]
Re:Overview Of Upcoming Rails 7.1 Features Part 1 by Mikeb85 on Tuesday December 20, 2022 @11:29AM (#34068177)
It's been fine for years now.
[ Parent | on HN ]
Re:Overview Of Upcoming Rails 7.1 Features Part 1 by fknorangesite on Tuesday December 20, 2022 @11:28AM (#34068165)
I think this joke is five or six years out of date. Nokogiri has been a breeze to install for a long time now.
[ Parent | on HN ]
Re:Overview Of Upcoming Rails 7.1 Features Part 1 by dwheeler on Tuesday December 20, 2022 @12:01PM (#34068695)
I used nokogiri in Ruby on Rails in 2015 and since, and have never had a problem installing nokogiri.
[ Parent | on HN ]
Re:Overview Of Upcoming Rails 7.1 Features Part 1 by fknorangesite on Tuesday December 20, 2022 @01:12PM (#34069813)
Exactly. It did used to be pretty finicky, but yeah I think it was 2015ish that those issues were fixed.
[ Parent | on HN ]
Re:Overview Of Upcoming Rails 7.1 Features Part 1 by faizshah on Tuesday December 20, 2022 @11:22AM (#34068071)
I feel like this is not a hot take, the big problem with JS ecosystem is the lack of stability. Every JS developer seems ok with picking their 100 favorite packages for each project instead of rallying around some core packages that everyone works on. Personally I don’t like the TS approach for large monoliths because I don’t like having to pick each library a la carte. I do prefer Typescript’s gradual typing system, but Rails wins in being easy and quick for development.

The big difference between the Rails and Ember approach vs most framework communities is the shared community around a shared tech stack.

[ Parent | on HN ]