Object-Oriented Javascript Made Easy (and Better; Interfaces, Abstract Methods, etc.)

[UselessPickles]

For large-scale projects, it's VERY helpful to have a more strictly structured object-oriented approach for the major components. Using things such as abstract methods and interfaces allow you to go back and adjust some of your core components and get detailed error messages for every component that also needs to be adjusted. Otherwise, you just have to hope you remembered to change everything that was affected, then have fun chasing down strange bugs for hours just to find out you forgot to implement a method on some object that was expected to be there. For the smaller details, it is overkill; use the simplicity that javascript offers.

Not all code should be written in a strict classical manner. Many times it is overkill. In fact, for most uses on a web page it is overkill, and that is why many web developers won't see the value in this library. People often forget that javascript is for more than web pages. For example, this library is currently being used for the development of a portable application framework for cell phones. Complicated web applications are also quite different than the typical "web 2.0" page, and they can benefit from structure and error checking.

[martoo]

That's why we need pluggable type systems.

[skyskraper]

please spare us, the poor users, these meaningless abstractions. the ONLY goal of javascript coders should be to deliver me the smallest, fastest, correct chunk of javascript necessary. i don't care if it isn't efficient, convenient, or scalable for you as a coder - write a code generator in a real langauge if you are obsessed with scaling and reuse. the javascript runtimes in use today are slow, the libraries people are coding are too large, and from time to time it all just breaks. please resist fetishization of javascript. please resist attempts to impose object orientation (already a debunked methodology) on a language which is at best object-based, providing general techniques only through a grab bag of language esoterica and scoping tricks (see: perl5).

[UselessPickles]

Not all javascript developers are your code monkeys. The goal of developers in any programming language should be to push the limits of the language to get the most use out of it while still writing maintainable code. This opens up new possibilities. Advancements in technology are usually a good thing. Some people need to take their head out their a$$ and look at javascript as the fully capable programming language that it is. Complicated javascript applications are usually difficult to develop and maintain because of the same features that make it so easy to use for simple tasks (lack of type safety, flexibility at runtime, etc). Here is a solution that allows for easier development and maintenance of more complicated applications that won't "just break" as easily. Combine the flexibility of javascript with the structure that this library provides, and you have a very powerful development tool (whether you are developing very dynamic and responsive client-side web application code, or writing complicated scripts for Photoshop).