@tomdale services … state … O_O services are by definition stateless.
-
-
Replying to @thomasABoyt
@thomasABoyt@tomdale This duplication of the module system into an entirely new module system is one of the things I hate about Angular :(2 replies 1 retweet 1 like -
Replying to @domenic
@thomasABoyt@tomdale You don’t need two service locators in a system. The language’s built-in one is fine.1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@thomasABoyt@tomdale I've also never understood the need to put a pillow between modules and an application.1 reply 0 retweets 1 like -
Replying to @thomasABoyt
@thomasABoyt@ryanflorence@domenic The module system is used for locating classes. What am I missing?1 reply 0 retweets 0 likes -
Replying to @tomdale
@tomdale@thomasABoyt@ryanflorence@domenic Indeed. The module system locates classes, the container instantiates them & manages instances2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats yes, that all makes sense to me, modules -> container -> instance, where does a service fit?@tomdale@thomasABoyt@domenic1 reply 0 retweets 1 like
@ryanflorence @tomdale @thomasABoyt @domenic A service is just a kind of module, like a controller, route, component, etc.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.