Rust to WebAssembly the hard way — surma.dev
What follows is a brain dump of everything I know about compiling Rust to WebAssembly. Enjoy. Some time ago, I wrote a blog post on how to compile C to WebAssembly without Emscripten, i.e. without the default tool that makes that process easy. In Rust, the tool that makes WebAssembly easy is called wasm-bindgen, and we are going to ditch it! At the same time, Rust is a bit different in that WebAss
WebGPU — All of the cores, none of the canvas — surma.dev
WebGPU is an upcoming Web API that gives you low-level, general-purpose access GPUs. I am not very experienced with graphics. I picked up bits and bobs of WebGL by reading through tutorials on how to build game engines with OpenGL and learned more about shaders by watching Inigo Quilez do amazing things on ShaderToy by just using shaders, without any 3D meshes or models. This got me far enough to
Is postMessage slow? — surma.dev
No, not really. (It depends.) What does “slow” mean? I said it before, and I will say it again: If you didn’t measure it, it is not slow, and even if you measure it, the numbers are meaningless without context. That being said, the fact that people will not even consider adopting Web Workers because of their concerns about the performance of postMessage(), means that this is worth investigating. M
Raw WebAssembly — surma.dev
Can you use the DOM in WebAssembly? Rust says yes, other people say no. Before we can resolve that dissonnance, I need to shine some light on what raw WebAssembly can do. When you go to WebAssembly.org, the very first thing you see is that it’s a “stack-based virtual machine”. It’s absolutely not necessary to understand what that means, or even look at the WebAssembly VM specification to make good
Layers and how to force them — surma.dev
The answer is will-change: transform. Or is it? TL;DR: Unless you will change transform, don’t use will-change: transform. Use will-change: opacity or backface-visibility: hidden, as their side-effects are less disturbing on average. A primer to layers A very simplified rendering engine of a browser works as follows: Download and parse HTML, generating a DOM tree. Process styling to lay out the do
Deep-copying in JavaScript — surma.dev
How do I copy an object in JavaScript? It’s a simple question, without a simple answer. Chinese translation: 中文版 Russian translation: русском Uzbek translation: O'zbek Call by reference JavaScript passes everything by reference. In case you don’t know what that means, here’s an example: function mutate(obj) { obj.a = true; } const obj = {a: false}; mutate(obj) console.log(obj.a); // prints true Th
How to read web specs Part IIa – Or: ECMAScript Symbols — surma.dev
Two browsers behave differently when given the same code. Which one is the buggy one? The spec is almost guaranteed to contain the answer, but it’s notoriously hard to read. Maybe this will help. Note: Before we start: The spec is not the only or maybe not even the best source to get this kind of information. Specs are hard to read, the ECMAScript spec especially so. While there is ongoing work on
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
