3 ms·
The framework he is talking about is trash compared to modern JavaScript UI frameworks. There are very few established patterns and each team seems to make up
by ngxoogler 9y ago
The framework he is talking about is trash compared to modern JavaScript UI frameworks.
There are very few established patterns and each team seems to make up their own rules. Some of the worst code I've ever seen was a result of this framework.
The code-splitting is probably the best feature and worked great when this was released, but smart lazy-loading of bundles is much easier in 2018.
The most frustrating thing is that the framework developers consistently point to benchmarks created over 3 years ago to show how great it is.
- iovrthoughtthis 9y agoThis article isn't about the framework though. It's incidental. This seems a very out of place comment.
- ngxoogler 9y agoI get what you're saying and maybe I'm being harsh, but the whole backdrop of the article is this supposedly amazing framework that was built. It undermines a lot of his points that it is poorly used.
- alexanderhouse 9y agoThe apps listed in the talk (Photos, Sites, Plus, Drive, Play) all seem to have gotten much better lately? Are you actually sure you are talking about the same framework as the author? Google has so many it can be confusing. If you'd be talking about the closure library and dreaded goog.ui.Component, I'd agree but that isn't it.
- pier25 9y agoSo what framework is it?
- applecrazy 9y agoThe article mentions that it's an in-house proprietary framework used in some live Google products, such as Drive, Photos, Search, and Play.
- deleted 9y ago[deleted]