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

Better name? #10

Open
francesco-strazzullo opened this issue May 18, 2018 · 3 comments
Open

Better name? #10

francesco-strazzullo opened this issue May 18, 2018 · 3 comments

Comments

@francesco-strazzullo
Copy link
Member

Hi @jevakallio. This issue is related to your issue #8. But I would like to concentrate on the first part of your statement on this specific issue. When you talk about the name of the movement and how is difficult to create a constructive position when it's formulated in the negative.

You made our team think about it. The point is, you're absolutely right.

The purpose of this movement is not just to make people write code without frameworks. But it's also, and perhaps more importantly, on how we as developers make context-aware techinical decisions about frameworks. And to make people understand why it's important to consider a frameworkless approach as a solution.

So a better name could be "Good Context-aware Techincal Decisions about Frameworks" Movement. 😄

But as you can understand "Frameworkless Movement" has more impact, even if it's not exactly what we mean. Now the I hope that I explained better our purpose, I hope that someone can come up with a better name.

In the meantime, we will change our README in order to make this message clear enough.

Thank you very much to help us making our point as clearest as possible.

@MattiaFattorello
Copy link

Hi, I like "Frameworkless" Movement as it inspire boldness. Yet, a more concise version of "Good Context-aware Techincal Decisions about Frameworks" could be "Frameworkwise" Movement". :)

@francesco-strazzullo
Copy link
Member Author

Thanks @MattiaFattorello for the proposal, we really appreciate it! We decided to keep this discussion open for now, to let people suggest new names to us.

@giacomocerquone
Copy link

Absolutely, I followed a live about this topic and at first glance I am firmly convinced that the naming is not correct, I initially thought something completely different and a better name could let you reach even more people.

Frameworkwise is more appropriate

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

No branches or pull requests

3 participants