At last I can show concrete example proving that IoC may be useful, even in
dynamic languages.
I always liked the simplicity of IoC concept - You don't have to know
anything about environment, you'll be called by someone when needed
But all IoC implementations I saw did exactly the opposite -
On Sunday, July 29, 2012 1:22:49 PM UTC-4, Alan Gutierrez wrote:
The ability to get a patch into the source has given programmers more
confidence
in their dependenies. They are no longer deferring decisions by
programming to
interfaces, but instead making a commitment to a dependency. C#
Easier? https://github.com/scottcorgan/Injector
On Friday, July 27, 2012 7:45:48 AM UTC-7, Eldar wrote:
Do we need this in Node?
My answer is yes we need some (simple) way to specify the app level
dependencies at runtime. Here is my take on
thishttps://github.com/eldargab/node-runtime.
That was a crazy idea and my goal was to find simple and clear way to swap *
fs* for *mkdirp*
On Saturday, April 20, 2013 9:23:50 PM UTC+4, Scott Corgan wrote:
Easier? https://github.com/scottcorgan/Injector
On Friday, July 27, 2012 7:45:48 AM UTC-7, Eldar wrote:
Do we need this in Node?
I recently wrote Micon https://github.com/alexeypetrushin/miconjs simple
Dependency Injector, it's designed for server use, not browser.
On Friday, July 27, 2012 6:45:48 PM UTC+4, Eldar wrote:
Do we need this in Node?
My answer is yes we need some (simple) way to specify the app level
I thought about this the other day and it seems to me, if you were to use
something like AMD (require.js), your container would be a simple
configuration. This line is basically asking a container to provide a data
provider with an id.
define(['dataProvider'], function(provider) {
});
Yeah, the topic's name is completely wrong. I realized it just right after
posting but couldn't fix.
What I actually mean is:
Look, require('foo') is nothing but global var 'foo' except that it is
scoped on module's level. Typically it is set by Node depending on your
dirs layout. But why
On Fri, Jul 27, 2012 at 10:25:53PM -0700, mixu wrote:
I've never really needed to dependency inject into third party modules. If I
did, I'd rather fork the third party dependency than do some sort of dynamic
solution.
That's part of what has changed with development since the rise of `git`
No.
On Friday, July 27, 2012 9:45:48 AM UTC-5, Eldar wrote:
Do we need this in Node?
My answer is yes we need some (simple) way to specify the app level
dependencies at runtime. Here is my take on
thishttps://github.com/eldargab/node-runtime.
Please checkout and let me know how do you
