2 ms·

Hey, thanks for the framework. I liked Roots.cx, and I found that a lot of the functionality that I really liked therein. Kudos! My comment probably needed t

by jbm 13y ago

Hey, thanks for the framework. I liked Roots.cx, and I found that a lot of the functionality that I really liked therein. Kudos! My comment probably needed to be more thoroughly thought out before being posted. My main issue with roots (and the reason I probably will not be using it in the future) is that I need to assume whoever takes over for me in 2 years will understand how to use Roots (and to make sure it is still updated). I can be pretty sure that Bootstrap will still be updated and maintained, but I can't be sure of the same with Roots. It makes it hard to use in a work context for anything major. I will take a closer look at Roots and your pre-compiled templates for my personal projects, thanks for letting me know about it.

jenius 13y ago
If it helps, I can assure you personally that it will. Roots is being aggressively developed right now and is already in use for several high-visibility projects at the company I work at full time. If anything, in a couple years roots will have expanded quite a good amount and, based on my current plans for the future, it will ship with a compiler that several orders of magnitude faster, be quite a bit more flexible with more languages and templates, be coupled with an optional cheap and efficient static hosting service with post-deploy compile hooks, and have a well-developed dynamic CMS that it can be paired with.