s3th

6 ms·

1.
Infinite Image Grids Are Flat Toruses(seththompson.com)
4 points by s3th 5mo ago|1 comments
2.
New Redesign of ARIA Authoring Practices Guide (Accessible UI Design Patterns)(w3.org)
9 points by s3th 4y ago|2 comments
3.
by s3th 6y ago
The police officers responsible for the murders of countless innocent Black people.
4.
Black Lives Matter: React Router Docs Are Offline(reacttraining.com)
64 points by s3th 6y ago|27 comments
5.
by s3th 9y ago
If early error is deferred then it's no longer early... that's all I meant by skipped. It still is a semantic change that's unrelated to a binary AST.
6.
by s3th 9y ago
i'm very skeptical about the benefits of a binary JavaScript AST. The claim is that a binary AST would save on JS parsing costs. however, JS parse time is not just tokenization. For many large apps, the bottleneck in parsing is instead
7.
Energizing Atom with V8's custom startup snapshot(v8project.blogspot.com)
34 points by s3th 9y ago|17 comments
8.
by s3th 10y ago
This architecture switch will have no impact on the V8 API. We're working closely with the Node.js team to make sure that this is a smooth transition and early results look as though there are significant performance benefits [0]. Disc
9.
by s3th 10y ago
Would appreciate a bug report if you have a repo: https://bugs.chromium.org/p/v8/issues/entry?template=WASM%20...
10.
by s3th 10y ago
Here's how to interact with browser APIs and import/export functions via the WebAssembly JS API: http://webassembly.org/getting-started/js-api/
11.
by s3th 10y ago
We're very interested in exploring this space. It's possible that this capability is exposed through an extension of sourcemaps [0]. Definitely curious to hear more ideas and feedback in this space. [0]: http://webassem
12.
by s3th 10y ago
The main benefit would be shipping a single WebAssembly module to target client and server (e.g. the same benefit of sharing JS between the browser and Node).
13.
by s3th 10y ago
The more detailed post is here: https://news.ycombinator.com/item?id=11598245
14.
by s3th 10y ago
As pointed out below, technically "ECMAScript® 2015" is "ECMA-262 6th Edition", so the numbers still exist in some form. It's a really difficult balance between readability, matching most-common usage in the communi
15.
by s3th 10y ago
The gutters are a little small on my iPhone, but I can see all the text. Want to send a screenshot to seththompson [at] google [dot] com? I'll see how much I can fix.
16.
by s3th 10y ago
See my comment below: https://news.ycombinator.com/item?id=11564354 It's not so simple as (paraphrasing) 'ES6 is sugar and makes ES5 regress in speed.' Generally, "make it work right, then make it work f
17.
by s3th 10y ago
This is a case of "make it work right; then make it work fast". ES2015 performance will improve with time (we've already made 8-10x improvements on certain features) [0]. Strong mode work was stopped for a variety of nuanced
18.
by s3th 10y ago
You can see comparisons between ES5 and ES2015 feature equivalents, as well as comparisons with older versions at https://kpdecker.github.io/six-speed/ . It's important to remember that implementation of ES2015 is
19.
by s3th 10y ago
WebAssembly is a low-level runtime currently targeting the existing web platform. There are no plans to add wasm-specific web platform APIs [0]. You will not gain existing capabilities other than those already exposed to mobile websites. No
20.
by s3th 11y ago
We just sent out an intent to ship this week! [0] They're trickier to implement than other ES6 features since they require coordination with the Blink side of Chromium. [0]: https://groups.google.com/a/chromium.org
21.
by s3th 11y ago
WebAssembly is an open source runtime developed under the governance of a W3C Community Group [0]. The binaries that get sent over the wire are simply more efficient ways to pack existing types of code. We will soon have a textual encoding
22.
by s3th 11y ago
WebAssembly doesn't intend to replace jQuery, D8, or CSS. However, we definitely plan to enable efficient DOM access. Doing so requires supporting some sort of native Garbage Collection, as well as the concept of opaque reference types
23.
by s3th 11y ago
Something related to debugging? Perhaps you came across this thread? https://github.com/nodejs/node/issues/2546#issuecomment-1893...
24.
by s3th 11y ago
The Emscripten toolchain can be used to produce both WebAssembly and asm.js from the same codebase [0]. There are also the nascent beginnings of a translation tool from WebAssembly to asm.js here [1] (look for wasm2asm). Ultimately, it shou
25.
by s3th 11y ago
Yes! It's the compatibility of more than one implementation, each running the same WebAssembly binary that makes me so excited about this milestone.
26.
by s3th 11y ago
It's not too late! The wasm binary encoding is open to change up until the browsers ship a stable MVP implementation (then the plan is to freeze the encoding indefinitely at version 1). The primary advantage of LEB128 is (as you mentio
27.
by s3th 11y ago
The web is an amazing content delivery vehicle, I totally agree! There's a whole class of content I want to be able to just `wget` and be done with it. The goal of WebAssembly is to open up the reach and easy user experience of the web
28.
by s3th 11y ago
As we get closer to having a WebAssembly demo ready in multiple browsers, the group has added a small little website on GitHub [0] that should provide a better overview of the project than browsing the disparate repos (design, spec, etc.).
29.
by s3th 11y ago
A big difference between ES5 and ES6/7 is that the former passes through our old, highly-tuned optimizing engine Crankshaft [0] and the latter passes through our new optimizing engine TurboFan [1]. The team's expertise optimizing
30.
by s3th 11y ago
There's definitely a lot of room for improvement. The V8 team has been working on finishing baseline implementations for all of ES6 before spending significant time optimizing particular features. But improvements are coming quickly! I

More ›