3 ms·
I'm not sure what this really adds, and as it's GPLv3 why anyone serious would use it for anything. Ok, looking through...holy hell it's ugly. I've never reall
by antihero 13y ago
I'm not sure what this really adds, and as it's GPLv3 why anyone serious would use it for anything.
Ok, looking through...holy hell it's ugly. I've never really felt the need to use public/protected in JS, and it looks inspired by PHP.
Bolting this stuff on on top of JS, in such a broken feeling way...I just can't see why anyone would use this at all.
- deleted 13y ago[deleted]
- vertex-four 13y agoYou definitely do distribute the HTML, CSS, Javascript, and content, by sending it to the browser, for any reasonable definition of distribute. What you don't distribute is any server-side code.
- dllthomas 13y ago"as it's GPLv3 why anyone serious would use it for anything" Serious people never set out to produce GPLv3 works? I totally grant the "this doesn't look like it's actually useful", though, although I've not been neck deep in JS for ages.
- mantrax3 13y ago> "and it looks inspired by PHP." You're getting the order wrong here. - It was inspired by Java. - PHP OOP was also inspired by Java. It's hard to argue that Java's OOP model is bad. It encourages clear code structure and works especially well for large project (for tiny projects you don't need OOP at all, anyway). This is why C#, PHP, this library and many more are based on Java. Oh, BTW, let's keep digging: - Java's OOP was inspired by Objective C. - Objective C was inspired by SmallTalk. It's always Lisp or SmallTalk, isn't that fun?