-
Notifications
You must be signed in to change notification settings - Fork 16
Description
The destructive communication is sad. There is a bigger focus on making an anti ActiveSupport campaign than adding ruby gem alternatives.
Although I agree with parts of the initial concept of this project, I can't git commit on a project named stop_active_support_anywhere. Sounds irresponsible.
Also, seeing you're an @hanami core member (Rails alternative), so you have a bigger responsability on this project. /cc @jodosha
I know @hanami since Lotus, and use hanami-utils daily, so I do appreciate and recommend it.
I'll leave 2 written contributions below.
- Text like this on your README should be reviewed:
ActiveSupport is Evil
There may be better alternatives to AS depending on situations/contexts
"You are definitely allowed to shoot yourself in the foot, if you really want to."
I couldn't walk today considering the amount of times in the last 10+ years of my Ruby consultancy experience I've successfully used ActiveSupport to help designing REST API Clients, Data Parsers / Importers, Form Objects, Service Objects, etc, ...
"if you are developing an application, and you are the only one who decides forever"
What's a "only one who decides forever" role?
- More alternatives to the list
- ActiveSupport::Validations
- dry-validations
- ActiveSupport::Attributes // ActiveSupport::Types (related to the Rails 5 Attributes API)
- dry-types
- virtus