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

Why we no Yoman? #66

Open
kaievns opened this issue Apr 27, 2016 · 2 comments
Open

Why we no Yoman? #66

kaievns opened this issue Apr 27, 2016 · 2 comments

Comments

@kaievns
Copy link
Contributor

kaievns commented Apr 27, 2016

This was a bit of an elephant in the room for me on this project and I feel like I'm missing something.

So, why exactly we're building our own templating and CLI thing when there is yoman?

yoman was a go to tool for this sort of things for a few years now. here is for example a MEAN stack generator

I feel like we are reinventing a wheel here and at the same time blocking ourselves off all the awesome things that community already built

@davidbanham
Copy link
Contributor

Because I spent like 30 minutes reading Yeoman docs and then bailed. It's really focused on allowing multiple generators to edit the same file and engages a lot of extra complexity in order to enable that. That's just not a thing we need. What benefit would we accrue from using Yeoman over simple mustache templates?

@kaievns
Copy link
Contributor Author

kaievns commented May 2, 2016

well, my thinking is that if you want to use code generators broadly, piggybacking on Yeoman would make sense, as you could use both your own and community created templates.

and the second thing is that generating code is like authenticating users, it seems simple but there so many corner cases. and i'd much prefer someone else make all the mistakes :)

@davidbanham davidbanham mentioned this issue May 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants