4 ms·

I'd like a simpler explanation of how it all works. With colorful flow charts and graphs. I'm really interested in how it compares to what express does. How

by AlexC04 15y ago

I'd like a simpler explanation of how it all works. With colorful flow charts and graphs. I'm really interested in how it compares to what express does. How is it the same, how different? However since I'm reading this from the office between doing actual work I've not got time to read this version. I may or may not remember to come back and check it out after work. Anyways, all of that is intended as a round of constructive criticism. At the end of the day, it is what it is.

akavlie 15y ago
If you want colorful flow charts, there are plenty at the "Isomorphic" link: http://blog.nodejitsu.com/scaling-isomorphic-javascript-code http://blog.nodejitsu.com/scaling-isomorphic-javascript-code The proposed Resource-View-Presenter model is a bit of a brain bender. Anyway, that aside, I agree -- this is described as a framework "initiative", and that page has no links to actual code, making it sound like a mere proposal. However, looking back at Nodejitsu's blog, it looks like they have a post with a more cogent explanation... and github links: http://blog.nodejitsu.com/introducing-flatiron http://blog.nodejitsu.com/introducing-flatiron
- AlexC04 15y ago
  Thanks so much for this! The graphs are exactly the kind of "conceptual flow" I like to have to give me a 1000 meter view of what's going on.
mcantelon 15y ago
Express is quite low level, with many frameworks built on top of it. This appears to be higher level.
- justatdotin 15y ago
  yeah, 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 ago
    sammyjs 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 ago
      hey, 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.

by AlexC04 15y ago

akavlie 15y ago

If you want colorful flow charts, there are plenty at the "Isomorphic" link: http://blog.nodejitsu.com/scaling-isomorphic-javascript-code http://blog.nodejitsu.com/scaling-isomorphic-javascript-code The proposed Resource-View-Presenter model is a bit of a brain bender. Anyway, that aside, I agree -- this is described as a framework "initiative", and that page has no links to actual code, making it sound like a mere proposal. However, looking back at Nodejitsu's blog, it looks like they have a post with a more cogent explanation... and github links: http://blog.nodejitsu.com/introducing-flatiron http://blog.nodejitsu.com/introducing-flatiron

AlexC04 15y ago
Thanks so much for this! The graphs are exactly the kind of "conceptual flow" I like to have to give me a 1000 meter view of what's going on.

mcantelon 15y ago

Express is quite low level, with many frameworks built on top of it. This appears to be higher level.

justatdotin 15y ago
yeah, 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 ago
  sammyjs 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 ago
    hey, 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.