These are chat archives for Betterment/backbone.blazer

24th
Feb 2015
Sam Moore
@samandmoore
Feb 24 2015 15:07
just spinning up a gitter room to chat about this project
would love to chat more about what we want to do with this router vs what it is doing already
we basically modeled it off of the concepts in ember's routes/controllers/views for promise-based setup
Sam Saccone
@samccone
Feb 24 2015 15:11
boom
Sam Moore
@samandmoore
Feb 24 2015 15:23
i'm removing the marionette dependency altogether. we don't need it and don't really have any plans on doing something that would require us to have any more of marionette than what is in Object
James
@jamesplease
Feb 24 2015 15:35
looks cool @samandmoore. @thejameskyle and I have very similar routers
Sam Moore
@samandmoore
Feb 24 2015 15:37
ya. i was hoping to talk to you about the one you have inside of gistbook yesterday, but no luck haha
James
@jamesplease
Feb 24 2015 15:37
i don’t know how much advice I should give, though. if i gave all of my advice, i would just be telling you to recreate James / my router :P
Sam Moore
@samandmoore
Feb 24 2015 15:37
are you talking about the gistbook state-router thing?
haha
we want this to be a simpler version of what ember provides
James
@jamesplease
Feb 24 2015 15:38
gistbook’s router is a prototype version of it, yeah.
Sam Moore
@samandmoore
Feb 24 2015 15:38
gotcha
are you guys actively working on something that you're going to open-source?
James
@jamesplease
Feb 24 2015 15:40
i’ve abandoned this approach to routing, so I probably will never open source a router built on top of StateRouter
i am lazily re-implementing a microscopic version of ember’s router
Sam Moore
@samandmoore
Feb 24 2015 15:41
hah gotcha
it sounds like you see a large difference between "this approach" and what ember provides?
James
@jamesplease
Feb 24 2015 15:42
a huge difference
Sam Moore
@samandmoore
Feb 24 2015 15:42
the two biggest differences that i noticed were:
  1. ember clearly has a lot more state involved in their flow, e.g. Transition objects
  1. ember routes are applied hierarchically
the second bit is pretty interesting to me
/foos/:id/bars
eval FooRoute() then eval BarRoute()
that's pretty neat
James
@jamesplease
Feb 24 2015 15:45
yeah. and super powerful.
Sam Moore
@samandmoore
Feb 24 2015 15:45
definitely.
James
@jamesplease
Feb 24 2015 15:45
the router i am slowly working on will be built on top of: https://github.com/jmeas/hsm.js
Sam Moore
@samandmoore
Feb 24 2015 15:46
awesomeeee. yea. that's what is missing from what we wanted to build
we didn't want to build a FSM
James
@jamesplease
Feb 24 2015 15:47
ember’s implementation is very verbose, very slow, and used to be very broken (tildeio/route-recognizer#46)
Sam Moore
@samandmoore
Feb 24 2015 15:47
also, i like that in hsm.js you have the state mappings constructed as "state": StateCtorFunction
James
@jamesplease
Feb 24 2015 15:47
but you can recreate their router in like 5-10% of the code
and it would be better (i think)
Sam Moore
@samandmoore
Feb 24 2015 15:48
yea, it definitely can be done
James
@jamesplease
Feb 24 2015 15:48
but — anyway. i think there is a lot of value in the approach you are taking
i use a similar router in all of my apps
and it is so much better than the router that comes out of the box
Sam Moore
@samandmoore
Feb 24 2015 15:49
cool. thanks. we're going to try to build this out a bit more. make it work like ember's router minus the two huge features mentioned above, and try to push it as a reasonable alternative to what you might end up building :)
James
@jamesplease
Feb 24 2015 15:50
cool
Sam Moore
@samandmoore
Feb 24 2015 15:52
in the meantime i will keep bugging you guys with questions and probing for your opinions on decisions we're making. i'd love for this to become a useful tool