-
Notifications
You must be signed in to change notification settings - Fork 0
motivations
searls edited this page Dec 11, 2014
·
2 revisions
Lineman did three main things:
- Add conventional sanity to simple front-end web projects
- Paper over grunt's weaknesses in a few places
- Send all of us down a bunch of pointless rabbit holes of various types and sizes
Upon reflection, it now seems:
- There's no point in trying to reinvent a better Broccoli than Broccoli. It's well thought out and great
- It would take us months to upgrade Lineman from Grunt to Broccoli in a piecemeal way
- Open Source projects doesn't get killed often enough, they just slowly lurch to death
So what if we could get a fresh start, kill Lineman, and build a new tool that's compatible with existing Lineman projects. Take the best part of Lineman—a conventional project structure, configuration, and build commands—and port that as opposed to any of the existing implementation.
A few benefits of starting fresh:
- No baggage for us
- Broccoli struggles with its on-boarding story right now (see the specificity and complexity of the sample app). If you're not using ember-cli, then you'll be writing a lot of custom Brocfile code. Reminds me of where Grunt was at two years ago
- It's an opportunity to build a broader base of community ownership than just a few people at @testdouble early while we still can
- If Broccoli is all it's cracked up to be as an API, the amount of custom code we need will be miniscule by comparison