-
Notifications
You must be signed in to change notification settings - Fork 43
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
Project name issues #129
Comments
Someone proposes name "alight" |
I also prefer the name "alight" to differ from angular.js. In a world dominated by jQuery MVVM is not really popular, so it should be explained. :-) |
First targets are people who have tried Angular.js and think it's too heavy (or too buggy). Look at fresh example in jQuery: https://jsfiddle.net/jane_mel/oshgnr30/6/ |
@dev-rke I'm talking about development of real application not a todo list or hello world. I added routing, i18n and custom directives which is required for real development. Still this time I've found a lot of things that differs from angular. That's why it took a week. And that's why I think that angular in the name can discourage newcomers. |
@rumkin: Ok, now i understand. I also had to do that in my current project and it took around 8 weeks. ;-) But i agree, a name without "angular" would improve seo visibility. ;-) |
It hard to search anything by name angular-light because of mess of angular / angular-light search output.
The second reason is difference between projects. Yes, it has same core basics but there is a tones of differences. I've spent a week to start using alight.
The third reason is that now angular has two absolutely different versions and it will be hard to explain which one is a base for alight.
For example
vue.js
use MVVM too and it's quite popular. So I think that MVVM doesn't need extra highlighting or explanation.I believe that
Angle.js
is a good name for Angular successor.The text was updated successfully, but these errors were encountered: