Hi Martin,
assetgraph-builder comes pretty close to ticking all your boxes:
https://github.com/One-com/assetgraph-builder, except that it requires a
separate build step.
Stylus and coffeescript are not yet compiled in production, but it would be
trivial to add as it's already supported by the
Thanks guys. AssetGraph looks great but contains too much magic for this
particular project, a straight rails 3.1 port. For now I am going with
connect-assets until I hit a major roadblock (haven't tried the CDN part
yet).
On Sun, Apr 15, 2012 at 4:43 AM, papandreou
On Saturday, April 14, 2012 8:35:09 PM UTC-4, r...@tinyclouds.org wrote:
This is a discussion to bring up with the EcmaScript committee.
Or Node could lead the way by example, just like browsers do before
creating a spec and advocating for it with the W3C.
Committees don't feel the pain
I think streamline is a brilliant piece of engineering and I'm sure there
are people who really benefit from such a tool. Just understand it's not
for everyone.
Has anyone ever stated that is is for everyone? If we just could agree
with the haters (you know whom I mean) that it a useful tool
PS: I just recently heard about node's past ability to froze stack with
promise.wait(). It's sad that this ability was removed just because some
guys used it wrong. It's useful and needed feature for right hands.
While I personally wasn't part of the community when that went down I did a
lot of
Hallo,
tests are now passing on node v0.4.x
a find2node or find2walk (shell command - idea from find2perl) where
you take find parameters and convert it into a js script.
I think the filewalker-module is a very good base for such a module.
Happy filewalking!
--
Job Board:
I'm working on a C++ NLP binding and wanted to implemented a streaming
interface so that text could be added to a stream in JS, my native binding
will receive it, extract the text process it and emit a dataevents with
the responses.
How would I go about reading a stream that was either passed
I'd recommend not doing the stream bit in C++, and instead have a
much simpler binding layer that does a single action, and then use
JavaScript to wrap up the queue of writes and emitted data blobs.
Check out the zlib binding in src/node_zlib.cc and lib/zlib.js in
node's source. It does
