Summing up: We have some momentum going here, let’s use it and roll!
I suggest whoever ends up writing the CSS gets to choose whether they like plain CSS or a preprocessor. Same for all other build-utilities. If one of them ends up being an issue, we can rip them out later. I prefer to have a Futon.Next that we need to rip something out of for the long term than not having a Futon.Next for the long term. I’m so looking forward to see some results here soon! :) If whoever ends up working on this needs anything, please let me/us know. Very happy to help with any roadblocks. Cheers Jan -- On Oct 25, 2012, at 22:03 , Ryan Ramage <[email protected]> wrote: >> You misunderstood that requirement. If we're not using a feature (e.g. >> config) it won't get deployed anywhere, it'll be removed at build time. It's >> not a user facing optional thing, the code just won't be on our CDN. >> > > Ok, interesting. Good to know. > > >> Right, and there are ~10 that exist and approximately interoperate today. > > Haha. With the new ability of attachment first design of erica your > normal web style folders are couchapps. One can push futon in its > current form, with no modifications*. We could be done with the new > futon as well. > > * ok, one modification. Couch does not like attachments with _ > starting, which current futon has. We can make a conscious decision to > not do that.
