Plugins in Playground

[rezoner]

Hi everyone,

I got plugins working for Playground. Plugins are nothing more than bundles of event listeners that can replace properties of an application or a state (on instantiation time)

For example here is a plugin that deploys basic Three.js rendering for Playground.

From end user point of view usage looks like this:

playground({
  use: {
   three: { /* config properties goes here */ }
  }
});

Now.

While this is very modular and pretty useful if you know what's going on under the hood - I am afraid it encourages bad habits by letting developers skip many learning curves. All the problems that jQuery has to deal with. jQuery is great - but because of its accessibility it lures awful developers and has became a synonym of whatever is lame in web programming.

What's your opinion. Is it a risk worth taking? I don't want to scare off professionals, I really appreciate that my library is unpopular but used by people as dedicated as I am. People who care to spend their time learning the basics before asking.

[rezoner]

What I'm also afraid of is ending up with two movements.

Direct composition over inheritance approach:

create: function() {
  this.collisionManager = new ENGINE.CollisionManager()
},

step: function() {
  this.collisionManager.step(delta);
}

vs Plugins:

use: {
  "rezoner/CollisionManager"
}