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.

Sign up for GitHub

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

Jump to bottom

General Question #144

Open
rwatts3 opened this issue Apr 7, 2017 · 1 comment
Open

General Question #144

rwatts3 opened this issue Apr 7, 2017 · 1 comment
Labels
question

Comments

@rwatts3
Copy link

rwatts3 commented Apr 7, 2017

Any chance this library and blaze once they are released to NPM, can potentially line up against react, angular, and vue ?

Mainly do you believe the life of blaze is truly over ?

I ask this question because from my experience with BlazeComponents, it's the one piece to the puzzle that makes blaze fall in the shadows compared to react , angular, and vue.
@mitar
Copy link
Member

mitar commented Apr 7, 2017

I think this is a question without an answer, because I do not believe in libraries winning against other libraries, but in them addressing needs of their users. Both Blaze and Blaze Components address needs of some users and this is it.

I ask this question because from my experience with BlazeComponents, it's the one piece to the puzzle that makes blaze fall in the shadows compared to react , angular, and vue.

I to not understand this statement. How would you describe your experience with Blaze Components?

@mitar mitar added the question label Apr 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mitar @rwatts3