News for hackers. Stuff that matters.

A comment on Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?. Parent comment

Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by timdorr on Tuesday March 05, 2013 @01:35PM (#5326376)
What about pre-processors (SASS, Less) or templating engines (ERB, Haml, Slim)? That would seem to be a huge task to "un-pre-process" an asset. Going backwards is immensely difficult. These are not easily reversible processes.

Instead, why not make something like IntelliJ/RubyMine/WebStorm/etc.'s Live Edit plugin a native part of the browser. Allow the asset pipeline to tell the browser it has changes available, rather than try to have it regurgitate all the processed assets. That would be relatively easy to add and very straightforward to implement.

[ Parent | on HN ]
Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by pedalpete on Tuesday March 05, 2013 @10:55PM (#5329222)
Your Live Edit idea is a good one, but I think the assumption about "un-pre-processing" would be part of the pre-processing development tools understanding what was being pushed to them, therefore, the need for an open standard as has been alluded to above.
[ Parent | on HN ]