Went Off The Rails: Why I'm Rebuilding Archaeopteryx In CoffeeScript

Post by rohitarondekar » Sun, Feb 26, 2012, 6:10 AM UTC

sha90 wrote: post #125

rohitarondekar wrote: post #70

Earlier quoted context omitted.

Write your own? I'm sorry but if Bundler doesn't solve your problem (or introduces other problems) either try and fix those issues OR write your own dependency management lib.

The unfortunate reality about writing your own new Bundler is that you'll inevitably end up rewriting Bundler. Isolate is basically just a mini-Bundler with a different (arguably simpler) storage location, but the storage location is really not where the complaints about Bundler are coming from. Rewriting things just to shed complexity or "bloat" will often just put you in a position where your library just can't do…

Post by bphogan » Tue, Feb 28, 2012, 3:02 PM UTC

MatthewPhillips wrote: post #124

bphogan wrote: post #123

Earlier quoted context omitted.

Wrapping things in objects doesn't seem to help me. I'd still end up with this, thanks to callbacks. app.get('/documents', function(req, res) { Document.find().all(function(documents) { // 'documents' will contain all of the documents returned by the query res.send(documents.map(function(d) { // Return a useful representation of the object that res.send() can send as JSON return d.__doc; })); }); }); Seems to me that…

I would create a DocumentRequest object that takes your req and res, then break apart your callbacks to separate functions on the DocumentRequest prototype. Then you would simply consume it with: app.get('/documents', new DocumentRequest);