Hacker News new | past | comments | ask | show | jobs | submit login

I like the concept of the separating concerns and no direct coupling between modules. I think they could have taken it one step further by using messaging but I'm biased there :)

I'm curious why they decided to roll their own modules when the web component standard has been around for a few years. Granted the polyfills may not have been available years ago when they started this but I feel like contributing to those, especially since the coding styles are so similar, would have been very fruitful. Looking at it today I'm not sure why I would use their modules versus web components unless I needed IE8 support.

The jQuery dependency is a little odd; is it going to keep up with the latest version of jQuery or eventually drop it? At a job I had a few years back I had to create a new web application where I was forced to use a platform that required a very old version of jQuery (otherwise it would break horribly) which made using a newer version a little annoying (though obviously doable thanks to noConflict()). It's rare to see frontend JavaScript frameworks with dependencies.

Overall this is pretty neat though I'm not sure I would necessarily use it.




You can do inter-module communication via messages. Notice the onmessage() inside the todo example here https://github.com/box/t3js/blob/master/examples/todo/js/mod...

As for $ dependency, a small discussion https://github.com/box/t3js/issues/12


Ah thanks for the info; didn't notice the onmessage. Still I'm biased towards my own messaging library but that's neat :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: