4 ms·
The main difference to boilerplate generators like Yeoman is that Roc collects an entire set of dependencies into a single npm package, versions it and provides
by arsovik 11y ago
The main difference to boilerplate generators like Yeoman is that Roc collects an entire set of dependencies into a single npm package, versions it and provides a generic way to start using them within a project (CLI + configuration).
It does not introduce an extra api-layer, you use things like React like you normally would.
In short terms the boilerplate is shifted into a versioned module that has a CLI and simple configuration system. The main goal of this is to keep complexity of things like Webpack, universal rendering and the like outside your actual project.
When you generate an app with Yeoman you get all the code dumped into your project. With Roc you get a thin skeleton that depends on the larger module that can be updated through npm.
Think of it like npm module composition.
- mhd 11y agoSo, fat jars for JavaScript?
- arsovik 11y agoSort of. It's an npm package with a lot of extra responsibility. - May have some boilerplate/gluecode (that yeoman would typically put inside your own project) - Some settings exposed that can be used to easily affect the behaviour of the package. - Some commands that do a specific job. For example building the bundles or starting development mode with Redux devtools++. Roc itself is not coupled with any tech like React or Redux, it's just one of the potential use cases.
- jitl 11y agoPut that on the homepage. Compare A (your app on Yeoman) to B (your app on Roc). Show me why I should use this!
- arsovik 11y agoGood suggestion. We have written a bit more about it here. How a typical workflow would look as a developer/user. https://medium.com/@DZV/roc-one-solution-to-javascript-fatigue-b14ea07b9763#.3igzifp2h https://medium.com/@DZV/roc-one-solution-to-javascript-fatig...