Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this merely focused on bashing ActiveSupport? #9

Open
ivobenedito opened this issue Mar 18, 2018 · 2 comments
Open

Is this merely focused on bashing ActiveSupport? #9

ivobenedito opened this issue Mar 18, 2018 · 2 comments
Labels

Comments

@ivobenedito
Copy link

ivobenedito commented Mar 18, 2018

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.


  1. 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?


  1. More alternatives to the list
  • ActiveSupport::Validations
    • dry-validations
  • ActiveSupport::Attributes // ActiveSupport::Types (related to the Rails 5 Attributes API)
    • dry-types
    • virtus
@davydovanton
Copy link
Owner

hey, thanks for the issue. My general point - create a repo which will help developers too see ruby ecosystem and will contain some libs or ideas which can replace existed AS code and make ruby libraries less rails specific.

Also, I have no idea for a better name for this project, because again, general point for all of this - make ruby ecosystem less rails specific. Because I think it's important for other frameworks and ecosystem growing. If you have a better name for this - let's create a new issue and discuss it?

I agree, sometimes README can contain angry words (I'm not a native speaker), that's why I'll be happy to see any help with it 👍

@jodosha
Copy link

jodosha commented Feb 4, 2025

@davydovanton can we close and archive this repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants