-
Notifications
You must be signed in to change notification settings - Fork 157
Future of generator-backbone #385
Comments
👍 |
Yeah, awesome idea. I think this generator should show the best practices for modern web app development in Backbone.js and maybe provide a foundation for other generators. |
👍 |
great idea, happy to help! |
need to break the ideas in small issues |
@rodfersou good idea, once I start working on this I'll create one issue to track progress on for now I'll keep updating progress here to keep you guys posted 😊 |
👍 |
I've been creating some PRs for some of the latest bugs but I still struggle on composable generators a bit, for example when a command line option/prompt is set by a composed generator like "ui", the mocha ui style from generator-mocha, how can I re-use it in another generator when the storage of this value is namespaced by generator name in .yo-rc.json? I ended up loading it explicitly from that file but feels like an hack |
Opps. Just stumbled upon this in the context of yeoman/yeoman#1653 Now I would love to know if there is a chance to keep generator-backbone alive. |
@ruyadorno what are your thoughts on this? I guess the most important question here is if there is anybody with a room for contributions? I checked npm and there are 800 monthly installs of the generator. Do you think the number is low? And if so, is it low because of the current state of the generator? So, if we improve it would get higher traction? I know that days of Backbone might be a bit over, but I'm sure there are people willing use it if it fits their needs. Backbone has 700K monthly installs on npm. |
@marian-r totally agree, would be a shame to deprecate such a historically important generator, I jumped in to help at a time the generator was completely broken but unfortunately I don't have the time to move on with the outlined plans 😞 sorry by failing to update you guys on that, almost a year went by since my last update 🙀 @mischah essentially we just need someone to carry forward the original plan of rewriting a new I'm happy to keep helping with code reviews and small fixes |
I am fine to step in, I am using Backbone at work with Marionette but it would be nice to understand which of the current options are still relevant, my current stack is on ES6 with Babel, Handlebars Sass and webpack2 with some extra help from grunt |
@mteodori I think that's a pretty good setup. We definitively would want to move to webpack + es6. Simplify the whole build process and make the generator leaner. |
Great 💖 Just added generator-backbone to the to do list regarding issue and PR templates 😘 |
Tests are breaking with this generator. May be happening with other generators too! Is anyone working actively on this generator? |
@roopeshreddy no one is actively maintaining this generator. |
I'm still around if anyone is willing to submit a PR but def not actively working on it |
As one of the original Yeoman generators, generator-backbone has a lot of baggage and so many options/opinions that makes it a heavy burden to maintain - as a result the generator lost contributors and went through a poorly maintained phase. For such an iconic generator, it would be a shame to end up abandoned and filled with unresolved issues.
Here are some ideas for a better future:
v1.0.0
for this new clear slate - this way we can still havev0.4.x
around for anyone depending on itI'm writing this down with the goal of collecting feedback and overall opinion from interested people - personally, I think this can be a good opportunity to set a good example on how to create/maintain composable generators, similar to what the Yeoman team did with
generator-node
->generator-generator
.cc/ people that were involved with generator-backbone in the past: @SBoudrias @addyosmani @revathskumar
The text was updated successfully, but these errors were encountered: