+1 for Nokogiri, it's comical at this point how long it takes to install.
I first starting coding with Rails in 2017, and now it's a major part of my job for the past year and a half. My most recent frustrations with Rails has been Webpacker and the asset pipeline.
We are refactoring our specialized documentation platform built as a Rails app into a whitelisted gem executable that will take the path for documentation and boot up a fully featured and branded docs platform. Our biggest hurdles initially were namespacing, folder configuration and changing the default behavior that zeitwerk, the asset pipeline etc. expected. Once we figured that out though, the rest has been pretty straightforward.
Webpacker is my second largest compliant because I can no longer easily create a web-app.
Rails is supposed to be convention over configuration and I felt it broke the spirit of the framework when I could no longer easily just 'get going' and its the main reason I didn't upgrade my apps to Rails 6.
I think the issue is a conceptual one. How do you integrate a second language's ecosystem of libraries, dependencies, etc. into a framework built primarily for the first language?
It used to be that you could accomplish everything for a full stack web app in Rails alone. You still can, truthfully, but a lot of clients, companies and consumers are expecting certain behavior that gets very challenging to duplicate without client-side JavaScript, and JavaScript has gone from a couple script tags to an entire universe of complexity, in and of itself.
+1 for Nokogiri, it's comical at this point how long it takes to install.
I first starting coding with Rails in 2017, and now it's a major part of my job for the past year and a half. My most recent frustrations with Rails has been Webpacker and the asset pipeline.
We are refactoring our specialized documentation platform built as a Rails app into a whitelisted gem executable that will take the path for documentation and boot up a fully featured and branded docs platform. Our biggest hurdles initially were namespacing, folder configuration and changing the default behavior that zeitwerk, the asset pipeline etc. expected. Once we figured that out though, the rest has been pretty straightforward.
Webpacker is my second largest compliant because I can no longer easily create a web-app.
Rails is supposed to be convention over configuration and I felt it broke the spirit of the framework when I could no longer easily just 'get going' and its the main reason I didn't upgrade my apps to Rails 6.
I completely relate to that.
I think the issue is a conceptual one. How do you integrate a second language's ecosystem of libraries, dependencies, etc. into a framework built primarily for the first language?
It used to be that you could accomplish everything for a full stack web app in Rails alone. You still can, truthfully, but a lot of clients, companies and consumers are expecting certain behavior that gets very challenging to duplicate without client-side JavaScript, and JavaScript has gone from a couple script tags to an entire universe of complexity, in and of itself.
Complicated stuff!
Nokogiri was most frequently named a "most frustrating" gem in the 2018 version of this survey! rails-hosting.com/2018/