4 ms·
You didn't even mention the Closure library which was released and then practically abandoned. We invested so much into Closure where I worked, with the promise
by mevile 7y ago
You didn't even mention the Closure library which was released and then practically abandoned. We invested so much into Closure where I worked, with the promise that this is what Google used internally, when suddenly Angular dropped out of Google and that sucked up all the oxygen in the room.
- rpeden 7y agoLooking at the changes and fixes in recent releases of the Closure library, it sure doesn't look abandoned or even practically abandoned. I think I understand what you mean though. The Closure library looks good at what it does, but doesn't have a big ecosystem around it like React or Angular. I remember looking at the Closure library back in 2010 and decided against using it, but from what I can see it still looks pretty decent. It doesn't look as nice to use as Angular or React, but it's been around a lot longer than either of them and probably has to remain backward-compatible with some pretty old code.
- pcj-github 7y agoClosure user here! 2019 and I still love it! Yes, it's verbose but easy to understand what's it's doing... My project compiles ~1000 js files down to ~300kb. Works great with bazel. No better type system for javascript IMHO. :)
- mkozlows 7y agoI mean, okay, but which other things that you would have selected would still be a good choice today? Would you be happy if you'd gone with Ember or Backbone?
- mevile 7y agoYes we looked at all of those as well as Sproutcore. There weren't a lot of good options. Lots of people were using ext.js and yahoo ui library and dojo. Closure was among the better options at that time.