Happy to announce Octane – the successor to Inferno.
React’s programming model, compiled.
Hooks, Suspense and Actions, compiled ahead of time. No virtual DOM. No Rules of Hooks. No manually maintained dependency arrays. The compiler understands what your code captures and generates the reactivity for you.
Octane supports TSX and JSX, along with TSRX for even better DX and performance.
It includes integrations for libraries such as TanStack, React Three Fiber, Lynx and StyleX, plus a compatibility layer for using Octane components inside existing React apps.
Octane is available in alpha today, with beta coming soon.
Wrote up a practical introduction to SIMD using a real example from Ghostty. SIMD has a reputation for being complex, but the common case follows a simple, repeatable shape and shouldn’t be scary! Everyone should know at least this much. https://t.co/yVcAycaq8P
Allbirds, the once-buzzy maker of wool sneakers, announced a new business plan just days before it planned to close down for good: AI computing infrastructure. @EdLudlow explains the move https://t.co/vQ4526Lhrz
I've open sourced Ripple!
https://t.co/sVDs3rtH9b
It's super early days, not much works and there's little to no documentation or guidance. Plus the codebase is raw, but I at least wanted to share my ideas with the community. :)
@jayforeman > Without the Silvertown Tunnel, congestion and air quality around the Blackwall Tunnel were predicted to get worse as London's population grows.
https://t.co/UTfo6y0fTG
@david_govea@LynxJS_org There spec defines QuickJS for their main thread but any engine for the background thread (V8, JSC etc.). I'm curious if they're explicitly using JS engines for their strengths? For example, QuickJS for its low latency one-pass compiler would make sense for start up.
@AdamRackis If anything, it would in Google's interest to make the language more complex to protect new browsers from eating into Chromium's emerging monopoly.
Building a new rendering engine that is W3C and ECMA compliant is already a very high barrier-to-entry.
@daniguardio_la@munificentbob After that, I started just diving into the code of other JS parsers.
It’s a little outdated, but the parser for ESPrima is very readable: https://t.co/jpag0yNoET
After that, I look a look at Hermes, V8 and Quick.js, which are a lot heavier, but cover more of the edge cases.
I want to share a JavaScript parser that I've been working on.
It's still a work-in-progress, but it's fully compliant with the ECMAScript 2024 spec, passes the Test262 parser test suite, and outputs ESTree:
https://t.co/6MmDkYyAuO
@daniguardio_la This is the exactly the reason I built it as well! To learn a little bit more about the low-level.
In terms of my own learning, I started with the excellent "Crafting Interpreters" book by @munificentbob to understand some of the theory.