Re:Designing very large JavaScript applications
by iovrthoughtthis on Friday April 20, 2018 @06:47PM
(#16888937)
This article isn't about the framework though. It's incidental.
This seems a very out of place comment.
Re:Designing very large JavaScript applications
by ngxoogler on Friday April 20, 2018 @06:56PM
(#16888983)
I 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.
Re:Designing very large JavaScript applications
by alexanderhouse on Friday April 20, 2018 @07:12PM
(#16889060)
The 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.
Re:Designing very large JavaScript applications
by pier25 on Friday April 20, 2018 @06:55PM
(#16888980)
So what framework is it?
Re:Designing very large JavaScript applications
by applecrazy on Saturday April 21, 2018 @03:41AM
(#16890410)
The article mentions that it's an in-house proprietary framework used in some live Google products, such as Drive, Photos, Search, and Play.
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.