There is a module development process where we try to make an effort to not use all the deprecated methods that were deprecated.
This is important too because this is the first time we’re using non-js module files, and because we’re not using all of the deprecated methods, we’re going to be running into compatibility issues with some of the modules we use.
This is a major change, and will lead to a lot of compatibility issues. The fact that we’re not using all of the deprecated methods will cause other people to make incompatible changes. We’re going to miss the opportunity to make some cool new features.
This looks like a major change also. We’re going to make some major changes when we make the next release. This is a really good change. We are going to be able to use all of the module methods that are no longer in use. We can make some of the module methods that we used to use no longer available in future releases. This is going to be a big change.
We all agree that if we want to keep our code as small and lean as possible we should only use the deprecated methods. This new change makes it much easier to do that.
We should not be able to do that. We should have a way to make the module methods like the ones that we use to do some of our things for us. We could also have a way to call them out and have them available to us.
We’re going to have to make a decision on this one soon. It’s going to be a pain to rewrite all of the module methods. We have a pretty strong opinion on that so we want to make it painless.
I think it makes it more difficult because we are calling out to the module methods to do things that we could do with jQuery or Prototype. We do want those methods to be available but we don’t want to use them.I think we want to make it so that you are able to just do the code you want to do. You can’t call out to jQuery or Prototype to do something else. It makes it a little more difficult to write the code.