3 ms·
Even the original, untyped, Dart was designed to be easier to optimize that JavaScript (e.g. it's class based, not prototype based, so the runtime doesn't have
by kjksf 10y ago
Even the original, untyped, Dart was designed to be easier to optimize that JavaScript (e.g. it's class based, not prototype based, so the runtime doesn't have t work as much to optimize object access).
Recently Dart has added a strong mode (https://github.com/dart-archive/dev_compiler/blob/master/STRONG_MODE.md https://github.com/dart-archive/dev_compiler/blob/master/STR..., http://news.dartlang.org/2017/01/sound-dart-and-strong-mode.html http://news.dartlang.org/2017/01/sound-dart-and-strong-mode....).
One of the reasons for strong mode is to enable better optimizations (https://www.dartlang.org/guides/language/sound-faq#why-strong-mode https://www.dartlang.org/guides/language/sound-faq#why-stron...).
- throwayedidqo 10y agoI'm going to save these links for the next time I get downvoted for saying that js object system and dynamic typing suck for performance :). When JS performance threads come up I always mention that JS will never be as fast as Go/Java. Some people have a tantrum when I explain these issues. The sources I usually cite are dense and people just continue to downvote without reading them.