11 ms·
Express is quite low level, with many frameworks built on top of it. This appears to be higher level.
by mcantelon 15y ago
Express is quite low level, with many frameworks built on top of it. This appears to be higher level.
- justatdotin 15y agoyeah, but, it's not immediately clear to me why they built sugarskull instead of a client library to match connect's routing (I've used sammyjs for that purpose) and while I do appreciate the philosophy of plates (I've done something similar), I wonder why wasn't that implemented as an express 'template engine'. I'm sure there's good reasons: I'd like them spelled out ;{)} looking good.
- hij1nx 15y agosammyjs emulates Sinatra. Sinatra is ad-hoc routing, vs centrally-declarative (e.g. a routing table definition). And although sammy is great, it is also a jack-knife with many plugins, we wanted to move the plugin-like capacity to a higher position in the architecture, which keeps sugarskull simple and focused on routing. I dont think the router is the right place to hang all your functionality from. `plates` is essentially a loose html-parser. The only reason it exists is because `weld` is too slow right now for mass consumption. `plates` is intended to ensure that developers have a way to template without DSLs since a lot of people want to keep their markup clean.
- justatdotin 15y agohey, thx for the explanation. sounds like I should consider replacing sammy with sugarskull I totally endorse the anti-template philosophy. But I want a bit more, like targeting attributes (eg, the href of an anchor, the value of an <option>) and replicating a class-selected fragment for welding data from arrays.