web-platform-tests in Blink and beyond bit.ly/blinkon7-wpt Or: Improving interoperability Philip Jägenstedt, BlinkOn 7, February 1, 2017 Primary focus: working effectively with WPT in Blink. Also: WPT as used by other vendors, and in standards.
A decade ago, nearly everyone was rendering their web applications on the server using technologies like ASP.NET, Ruby on Rails, Java, and PHP. Then handy libraries like jQuery showed up, and suddenly server-side rendering everything didn’t necessarily make sense anymore. jQuery was followed by a long list of client-side libraries like Backbone, Knockout, Angular, Ember, and React. With each itera
Nowadays, we’re forced to use many accessory tools to facilitate, speed up and optimize our web development workflow. Often, though, such tools add an extra layer of complexity into the stack. As a result, we need to utilize additional time and effort to learn, understand and use these tools correctly. The same is true for webpack. When using webpack for the first time, it can be difficult to unde
Many of our clients and peers love Webpack but hate the long build times that result as projects start leveraging more of Webpack’s features. The hardsource plugin, created by Bocouper and Webpack expert @mzgoddard utilizes intelligent caching and has been shown to reduce subsequent build times by up to 97%.
Problem: How can we preprocess JavaScript (at build-time or on the server-side) so engines like V8 don't have to spend as much time in Parse? This is a topic that involves generating either bytecode or a bytecode-like-abstraction that an engine would need to accept. For folks that don't know, modern web apps typically spend a lot longer in Parsing & Compiling JS than you may think. Yoav: This can
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く