igrunert

5 ms·

1.
Oxide raises $200M Series C(oxide.computer)
614 points by igrunert 7mo ago|335 comments
2.
by igrunert 8mo ago
If you're in Denver, Colorado you can see one in-person at The Forney Museum of Transportation.
3.
by igrunert 10mo ago
WebKit on Windows has progressed since ~5 years ago. The gap between the Windows port and the Linux WPE/GTK ports is shrinking over time. Every JIT tier has been enabled for JSC on Windows[1], and libpas (the custom memory allocator) h
4.
by igrunert 11mo ago
The layout tests on Windows are failing at the moment due to a regression introduced a few days ago (likely https://commits.webkit.org/301043@main ). The easiest way to run WebKit on Windows is via Playwright.
5.
by igrunert 1y ago
A CMPXCHG16B instruction is going to be faster than a function call; and if the function is inlined there's still binary size cost. The last processor without the CMPXCHG16B instruction was released in 2006 so far as I can tell. Window
6.
by igrunert 1y ago
The "Chrome Commit Tracker" linked is a pretty interesting set of visualizations that I hadn't come across before. Makes it a lot easier to get a feel for the sizes of the various teams, and how they change over time. https:
7.
by igrunert 1y ago
WebKit runs on Windows, the Windows port just needs work to bring it up to the level of the Linux port. I got every JIT tier enabled in JavaScriptCore [1] and enabled libpas (the memory allocator). The Windows port is moving to Skia in line
8.
by igrunert 1y ago
Ah yeah, I see Firefox ran into that and added retries: https://hacks.mozilla.org/2022/11/improving-firefox-stabilit... Seems like a worthwhile change, though I'm not sure when I'll get around to it.
9.
by igrunert 1y ago
I recently ported WebKit's libpas memory allocator[1] to Windows, which used pthreads on the Linux and Darwin ports. Depending on what pthreads features you're using it's not that much code to shim to Windows APIs. It's
10.
by igrunert 1y ago
I think the author was happy to be employed by a megacorp, along with a team to push jemalloc forward. He and the other previous contributors are free to find new employers to continue such an arrangement, if any are willing to make that in
11.
by igrunert 2y ago
The gap between the Windows and GTK ports is shrinking. Every JIT tier has been enabled for JSC on Windows[1], and libpas (the custom memory allocator) should get enabled soon. The Windows port is moving from Cairo to Skia soon as well, mat
12.
by igrunert 2y ago
While the modern web is complicated, there's a few things working in Ladybird's favor. Web Platform Tests (1) make it significantly easier to test your compliance with W3C standards. You don't have to reverse engineer what ot
13.
by igrunert 2y ago
Ladybird does have another slight advantage in that it only has an interpreter for JS and wasm, instead of maintaining multiple tiers of JIT compilation for both. That choice materially reduces the surface area for exploits.
14.
by igrunert 2y ago
For Ladybird - Andreas Kling called out that the vast majority of "easy tests" are passing and each additional test is going to be more difficult to come by going forward. https://www.youtube.com/watch?v=-l8epGysff
15.
by igrunert 2y ago
There are a handful of git features which work significantly better with a clean history on main. If `git blame` points at a well crafted commit, it can help bring additional context to the line in question. In addition `git log -S<strin
16.
by igrunert 2y ago
When discussing security it's important to keep in mind the threat model. We're mostly concerned with being able to visit a malicious site, and execute wasm from that site without that wasm being able to execute arbitrary code on
17.
Every JIT tier enabled for JavaScriptCore on Windows(iangrunert.com)
7 points by igrunert 2y ago|0 comments
18.
by igrunert 3y ago
> But (Safari is) the only option here that’s unsupported outside one manufacturer’s hardware. You can use WebKit on Linux via GNOME Web (WebKitGTK), it's maintained by Igalia. Though that won't get you cross-device syncing, wh
19.
WebAssembly on WebKit for Windows(iangrunert.com)
2 points by igrunert 3y ago|0 comments
20.
by igrunert 3y ago
I think a big reason developers don't choose WebKit is due to the Windows port requiring significant work, and most new browsers want to support Windows. On this thread there was a rough estimate of $1M - $2M USD to do that work. It&#x
21.
by igrunert 3y ago
Building an browser engine from scratch is a great exercise for validating both the specifications and the web platform tests. For example, here's some bugs raised by Andreas Kling in the HTML spec that were found while building Ladybi
22.
by igrunert 3y ago
Yep, embedding the Servo engine into the final binary. This work is sponsored by another (separate) NLnet grant: https://nlnet.nl/project/Tauri-Servo/
23.
by igrunert 3y ago
Legacy Layout refers to the original system, Layout 2013. There was a second system started, Layout 2020, to address challenges with implementing parts of the CSS spec which didn't cleanly map to Layout 2013's architecture. There&
24.
Estimating Web Browser Investment(iangrunert.com)
2 points by igrunert 3y ago|0 comments
25.
by igrunert 3y ago
> JavaScriptCore doesn't have WebAssembly enabled on Windows yet. I got JavaScriptCore compiling with WebAssembly enabled yesterday, but I don't know how long it'll take to get it to actually work. The bigger problem for B