(I am the author of GNU ease.js.) Wow, quite the negative response here. That said, this is something I was wholly expecting from the JavaScript community, so

(I am the author of GNU ease.js.) Wow, quite the negative response here. That said, this is something I was wholly expecting from the JavaScript community, so I am not swayed; I'm merely providing something that I found to be useful in the hope that it is useful to others. So thank you to those who recognized that. I feel that many of the negative statements here could have been addressed if the posters had taken the time to understand why the project exists: http://www.gnu.org/software/easejs/manual/About.html The framework exists for those who wish to have the benefits of Classical OOP using JavaScript without the need for a compiler; it provides a standalone library for something many frameworks currently do, but do so incompletely: their own class systems. If there is a feature of ease.js that you do not like, you are not forced to use it; it simply generates prototypes. Language and paradigm flamewars will always exist, but let's be respectful of those who want to "program into" their language (as Steve McConnell put it). Note that GNU ease.js was created when Harmony was just barely getting off the ground, and it is still not released. Even after it is released, there will still be users who do not have the newest features. Part of the reason for GNU ease.js is to address the issue of consistency across all browsers. It works in IE 5.5 (although that wasn't intentional)---you don't have to worry about whether or not ES6 is supported. ES6 also doesn't address some concepts ease.js does. http://www.gnu.org/software/easejs/manual/Implementation-Details.html Let me be clear---I have a strong understanding of the prototypal model, and it does have its uses and elegance. For those who want some of the features of GNU ease.js without the framework itself, I provided both the above link and this paper which demonstrates how OOP is generally done in ECMAScript (and its problems): http://mikegerwitz.com/docs/coope.html GNU ease.js encapsulates those hacks. There's value in that alone. To answer some of the Harmony-related questions: here is a reply to a question I received from another GNU hacker: http://www.gnu.org/software/easejs/misc/easejs-harmony-reply.txt With regards to the licensing: RMS asked if I'd be willing relicense under the GPLv3+, because of their campaign against proprietary JavaScript. Let me be clear on this matter as well: I am an avid free software activist. I hope that people will find GNU ease.js to be useful, but only if they are writing free software. http://www.gnu.org/software/easejs/whyfreejs.html Thank you, conductor, for posting the project---I appreciate input from the community regardless of its tone.