Hey guys - project creator here. Would love to get any and all feedback - this project has been my passion for over a year and I'm super excited to finally release it!
This is really nice and a great way to rapidly build without resorting to templates or bootstrap. Highly polished, great work.
We released something built on the same stack (jade, stylus, coffeescript) that's a bit more lightweight, more geared towards building prototypes called [proto](https://github.com/droptype/proto). Because it's focused on building small prototypes, it saves everything to gists and provides a viewer at http://proto.es/{gist-id}.
Thanks so much! I really appreciate it. Proto looks like top quality stuff - excellent work. I'm going to check this out in depth - perhaps our tools can learn something from each other or combine in some way : )
That would be fantastic. As I said, root is very highly polished and you've done a great job. We have something in the pipeline that might make sense to collaborate on. Will shoot you an email to discuss.
On a related note, I'm currently using Grunt.JS with few plugins for Compass, CoffeeScript and Live Reload. Similar to Guards (ruby based), it's the plugin ecosystem that makes it valuable and able to suit multiple needs.
I will admit that this is a rather opinionated framework. I'm kind of shooting for the apple philosophy - reduce flexibility for a lighter and more beautiful product. I've worked with a lot of compiled languages and for me, these are the cleanest and easiest to work with. I did try to build in a bit of flex though with the plugin interface and the fact that it compiles html, css, js, and ejs in addition out of the box.
Meteor is not the same type of project as roots at all, so this comparison doesn't exactly make sense. Although meteor is an awesome project and in addition is backed by at least 3 people working on it full time : )
Mimosa author here! I'll work on the website. =) I do think the tool is better documented than some of the others, and I was really going for having the docs rather than making them super pretty.
Mimosa is very pluggable (http://mimosajs.com/modules.html), moreso than Brunch, but slightly less so than grunt, though, to be honest, my grunt experience is slim. That said, grunt obviously has quite the ecosystem of plugins that all the others lack.
HackerNews commenting n00b, but guessing it only lets replies go so deep? Hence my reply to the site suggestions goes here. =)
Crazy kinds of awesome to get that kind of feedback! I'll take a look at all that stuff. Big site update content-wise with my next release and I can make some changes then.
Hacker News has exponential delay time on comments based on depth. So the deeper a comment is, the longer you have to wait to reply to it. It's supposed to help cool off flamewars.
Your site definitely looks slick! I'd take any suggestions anyone has and as long as they make sense, implement them. I'd rather be writing node than thinking about design anyway. =)
Cool project. Also, you should checkout Punch (http://laktek.github.com/punch). I like it mainly for the JSON based content definitions, which is really helpful when it comes to prototyping web apps.
In that case please consider redoing your videos with more care. Both the audio and video are poor. Your microphone should be near your mouth so that you don't sound like you're far away and the video resolution is really low.
I know, I definitely need to do a better job with the videos. I just did them this morning (wasn't planning on having them but i thought it might be a good idea) and vimeo really murdered me on the resolution, not sure why. I'll have new ones up soon, promise : )
It looks like roots is using Bower to manage client-side packages. Bower is Twitter's "front-end JavaScript" package manager. Bower does indeed manage and track dependencies for you, see http://twitter.github.com/bower/
I made a plugin interface just for things like adding typescript support. I know pretty much nothing about typescript through, are there any good node compilers out there? It would be incredible if you made a plugin for it - if not I'd be happy to try to tinker one together myself.
p.s. I would add a tweet button on the site, I actively looked for it, although I'm lazy I tweeted anyway, but this might give you some extra shout-outs, especially for the shot grace period you are on HN front page
Sorry for being unclear. On the video you recommended using ftp to transfer the pub folder over to the web server for go live. It's best to recommend a tool that operates on an encrypted ssh transport like sftp/scp/etc.
I very much appreciated the run-this-remote-file | sh installer method before I learned what I was actually opening myself up to. As handy as it is, this practice really should be discouraged, imho.
I get that, but what if you recently ran sudo make-me-a-sandwich in that shell session? If someone maliciously slipped a sudo command in that script they'd have everything they needed, and you might not even realize it. Obviously, I'm not suggesting the authors of these tools, but these remote shell installers seem like they'd be obvious targets for Bad Hackers.
It seems like the whole point of these remote shell installers is to make it easier for some people, but some might not be aware of this risk.
Yes, and they should drop the pipe to bash/sh at the end of the curl command. Download it, read it, then manually run it, don't just pipe it all together.
Fair enough. This is why I have explicit instructions on how to install without the run-as-remote-file install method right above it. Do you think it would help to add a view source link next to it or something?
Personally since node is the only real dependency, I'd just use the npm installer. I didn't mean to discourage the work you put in, by the way. I might be using this tomorrow, but today is the christmas party.
If you check the source, really this is all the script does. It checks to see if you have node, and if you do it runs npm install roots -g. But this is good feedback and if other people feel the same I'll definitely swap out the one-command installer. Have fun at the christmas party!
As a developer, I don't quite get who this is for. I know these technologies and how to use them and install them. Installing node.js and stuff is also pretty much a couple of one liners.
I guess I don't see why others find much pain in installing node or rails... I already have Ruby/Node and other stuff installed and each new project I create differs in file structures and stuff like that based on the needs of the project. Different projects require different stacks.
Hi - I'm a developer too, full time, and I'm the one who made this so I guess I should be the one explaining it. Roots is for front-end devs or devs who do front-end work. It makes doing front-end work blazing fast and much less repetitive.
As for your comment on making it yourself, I would urge you to go check out the github repo (https://github.com/jenius/roots). I can assure you that replicating this environment is not something that can be done with a couple lines of npm install xxx - there is a lot of code under the hood. I've spent more than a year on and off working on this. The command line client is fast, simple, and intuitive. The css library is extensive and extremely powerful. I built this tool for developers to make life quicker and easier when it comes to front-end dev.
Give it a shot, and if you still think it would be more convenient to roll your own, email me and maybe I can take a few tips from you on how to continue improving roots to make it more useful for developers : )
Because it's simple. Getting over the 'installed' barrier is important. I include very clear instructions on how to install with npm above the "| sh script". If people thought this was really a disaster, that comment would have been upvoted more, and so would yours.
I've never heard anyone argue using number of upvotes as evidence before! And I'm not sure that the right thing to do is always the most popular option.
Simplicity is desirable, but not at the expense of security. I'm sure you wouldn't suggest that we omitted the password checking step in login forms because it gets over the "forgetfulness" barrier.
And it's also questionable what it actually brings in terms of simplicity, since it doesn't install node for you.
I only say this because I'm surprised you posted another comment just linking to a comment that's already been made. Usually the practice is to add your opinion under the existing comment or upvote it. It seemed to me that you posted it again just so that your comment would be at the top of the page for the limited period that new comments hang there, in order to get more attention. And the reason I mentioned the upvotes was exactly this reason - if people actually thought this was important, they would have upvoted the original one more - you posting the exact same thing again is unnecessary and frankly should be discouraged.
Like I mentioned as a response to both your and the other comments, I explain how to install it without that shortcut directly above, so it's not too difficult to do this if you are concerned about security. In addition, it is very simple to just check the source of the link if you are suspicious. I asked in the other comment thread if it would help if I put a "view source" link next to it to make it even more convenient and nobody responded, so I figured it wasn't something people were after.
I'm not sure how to respond to your questioning it's simplicity. It's not a complex script - it checks if you have node, and if you do it installs roots. If you don't, it tells you that you need node and opens up the node.js website. It's just a little helper, not a mind-blowing, life-saving tool. Is it saving you hours upon hours of time? No. But does it make the process simpler? Yes.
The point of linking to another comment (made by someone else who is more qualified to comment around 2 years ago) is to point out how people just aren't learning.
While it may seem like it's just a convenience, these things tend to take on a life of their own. For example, Chef's "pipe to bash" installer is used by Vagrant, thereby exposing anyone using Vagrant and Chef to make a dev VM on an untrusted network (any wifi!) to who knows what being installed. But unless you read the source, you don't know about this risk.
Cool project - one of the major pain points with Yeoman was trying to get templating working. Cool to see a project which takes this approach from the beginning.
This looks interesting, I've been doing a lot similar work as I'm currently building an open source CMS for nodejs. It's a lot more complex than Roots however the goal of the project is to make it easy for developers to build websites and applications. It'll come with a full featured and extendable admin control panel and built in support for all the common stuff like authentication, user Management, content management, blog posts, asset publishing, etc.
The nodejs side handles the API which automatically generates REST routes for your resources, and you have the ability to write custom API endpoints as well.
The website and admin panel are automatically built using Grunt and require.js and depend only on the API so you're free to host your website on S3 or another server entirely. The client-side website will call the API for content, authentication, etc. The admin panel is written in AngularJS (So far it's incredibly responsive and feels almost native!) and it's up to the user what to use for the main website.
One nice thing is during development it'll watch your files for changes, rebuild the site on the fly and update the client view using socket.io. No more constantly refreshing the page after every change! In production mode everything is bundled and minified using r.js.
If this sounds interesting to you guys then I should have something to show HN in the next few weeks :)
Sounds like a cool project - excited to see it for sure. The tough part with projects like this is making sure that it's simple but still flexible. For example, can you fully customize the rest routes, or are those just generated? If a developer knows enough to work with routing, models, and the back end, why wouldn't they just use rails and activeadmin for the admin panel? If your project is any less simple/flexible than rails, that will be a tough compromise.
Either way, this sounds like a pretty sweet project, I'd love to check it out when it's released. What are you thinking about calling it (just so i recognize)?
I completely agree with your points. I constantly encounter the same problems when I use other frameworks so I want everything to be fully flexible.
At the moment the REST routes are generated for resources and available through the api/resources endpoint. (For example, /api/resources/users/) you can however add whatever other routes you like to /api/ using your own controllers.
I'm thinking about adding a simple query language to the REST route syntax to take care of some common requests. That may work something like this: /api/resources/users/$near/lat,lon
It's still early stages though so I'll probably go through a lot of ideas before I'm happy with it!
It'll be called Nails (or Nails Framework, Nails CMS, whatever sounds closest to the finished idea) - I have the domain nails.io which I'll be using for this project.
Cheers. I've used RailwayJS in the past but I switched to LocomotiveJS[1] which I find much nicer to work with and it's incredibly flexible too.
I'm using locomotive in this project on top of express to help with controllers and routing, though I'm thinking about using flatiron[2] which is a pretty solid looking set of modules for routing, middleware, etc.
Make some simple HTML components, break out the compiled HTML and CSS for non-developers, and you've got yourself a bootstrap alternative. Please, make it happen.
I made it my specific goal not to have this as a bootstrap alternate - there's already boostrap and foundation - why do we need more? In addition, I'm very much against using classes to dry up your css. You should be using mixins or extends to build object-oriented css - that's the principle that roots css is built upon.
Rather than catering to non-developers, I like to encourage people to learn more about development so they can write clean code and make beautiful sites. If that means less adoption, so be it - at least I won't be polluting the web with poorly built sites : )
That being said, this is open source, so if that's something you want to work on, you are more than welcome!
Since I'm a dev I would never use a compiled version of such a framework, but having adoption by non-devs would benefit the community and create a market for devs to create things for.
I wouldn't think of it as catering to them but creating an easier on-boarding process.
Ok, i see what you're saying. That is the exact mission of this library (https://github.com/jenius/roots-css) which is behind roots. I would love any help or advice on making this go where you imagine it can. Hit me up via email or twitter and let's talk about it!
This seems comparable to Fire.app (http://fireapp.handlino.com/, F/LOSS, my favorite) or CodeKit. I noticed that you are specifically pimping out Stylus rather than Sass/Compass, but it doesn't seem to be a problem to get Compass working if you copy the library in yourself.
for sure, this was what i was aiming for. if i were better at cocoa dev i would have made a little mac app too.
I pimped out stylus and avoided sass/compass for very specific reasons. try using the roots-css library and let me know what you think. I'm hoping people find it to be a refreshing change of pace - the syntax is natural, extensive, and includes ui components.
Will do. I've heard people on Freenode IRC telling me that while Compass is a great library, Stylus is the superior language. I certainly was a fan of Sass over SCSS, and I like how Stylus reminds me of that.
I prefer using mixins over extend, as they are more flexible and intelligent. If you don't structure your classes correctly it can lead to some code duplication, but frankly this doesn't make any speed difference after gzip anyway.
To respond to your edit, stylus is as good at including mixins as sass. it's a lot less verbose in fact. you just run it as a function.
The placeholder selectors are the one thing stylus does not have. I'd like to see if I can build that in and send a pull request at some point. But for a library like this I need flex and intelligence which means i'll be using mixins over placeholders anyway.
For sure. I actually built roots on top of sass originally, and I became frustrated with it's limitations. I tried porting it to stylus because that was the only viable alternative that I knew of, and once I started working with it I couldn't go back.
The only drawback to stylus is that sometimes you can get caught with ambiguity. But I've tried to make roots so that if you are just starting, you deal with that as little as possible.
Haha was very prepared for this question. The main differences for me are that roots doesn't rely on ruby, it's built for advanced devs (starts with jade, stylus, and coffeescript), it uses roots-css rather than compass, and the project structure is a bit lighter and cleaner.
I tried yeoman and played with it for a while when it came out, but for me it feels vastly different to actually use. The concepts are definitely similar though. Great question!
Looks great! I've been using yeoman for a while now and this looks like a fantastic replacement / alternative. Are you looking for contributions or just releasing this for people to use?
Both! Any and all contributions are more than welcome. I don't know what the eff I'm doing. This works great for me, but if I can make it better for everyone else I'm all about that. I'll continue to work hard on this until it's the best it can be.
Are people using this/Brunch/Yeoman inside Rails apps? I can't work out the usecase - or do you use this in conjunction with a separate app generating your API?
Thanks so much! Really appreciate it. I am a backend dev and spend much of my time in rails (as you can probably tell from the way this project was written), so I very specifically built this to work with rails. I have a plugin here (https://github.com/jenius/roots-rails) that's working, but still tinkering with it. More than happy to accept contributions as well!
Your "curl roots.cx/get | sh" installation method is not as easy as it seems because it requires node.js but current text seems to imply that only a Linux or Mac system is requited :)
I think the reason is because this isn't a code-based library, it's a command line client. The portion that is more code-based (the css library) is chock full of code examples, and all the commands are listed out on the front page.
After looking it over, what kinds of other code examples would you want to see?
For sure. I do work mainly on backend dev, and the roots-rails and roots-express plugins help me out a decent amount. Roots specifically is targeted to front-end though. If you have any suggestions on how to tie this together nicely with backend stuff I'd be more than happy to hear it though!
My biggest thing right now is getting the livereload to work with rails, specifically through pow. I'm sure there's a way to do it, just have to figure it out...
Thank you! Yeah, you can absolutely use plain js. You can just drop a plain js file in there and delete the coffeescript - everything should still compile perfectly.
If you want to use basic html, css, and js, you can use the flag --basic to the end of a roots new command : )
But yeah I'm thinking some option for custom default templates might be nice to add, now that you bring this up. Also, try coffeescript! It's great, promise
You won't regret it. Just give yourself a week or so to get used to it - it seems frustrating at first when you make syntax errors, but it is a life saver in the long run
Thanks so much for leaving feedback - really appreciate it. It helps a lot, and thanks so much for your kind words as well. Just out of curiosity, why would you prefer sass and haml? Have you tried stylus and jade? If not, you should give them a shot!
You're definitely right that there are a lot of alternatives - I just think roots is the best. If there are any other features that you can see as helpful, by all means let me know and I'd love to try to integrate them!
Great job OP. Would love to see something that merges aspects from this and Yeoman. I feel like (haven't officially tried either TBH) they focus on slightly different aspects and would really cover full stack very very well.
Again, Great job!
I wasn't implying anything. Some people like having a unique name so I was just letting him know another Roots existed. Ultimately the author's choice if he cares enough to rename it or not.
Also, this website is open source in addition to the project. It's here on github: https://github.com/jenius/roots.cx