@torbiak.bsky.social
Reposted
580 - Min-Max Baby
September 15, 2023 at 12:44 AM
580 - Min-Max Baby
Reposted
Reposted
ECMAScript excitement 😉
Congrats to @manishearth.bsky.social on unflagging TC39 Stage 3 Temporal in V8 today. Heading for Chrome 144 🎉
By many metrics this new date-time API is the single biggest change to JS ever 🔥
V8 uses Boa's temporal_rs by @jason-williams.co.uk Kevin Ness & Manish 👍
Congrats to @manishearth.bsky.social on unflagging TC39 Stage 3 Temporal in V8 today. Heading for Chrome 144 🎉
By many metrics this new date-time API is the single biggest change to JS ever 🔥
V8 uses Boa's temporal_rs by @jason-williams.co.uk Kevin Ness & Manish 👍
November 4, 2025 at 7:49 PM
ECMAScript excitement 😉
Congrats to @manishearth.bsky.social on unflagging TC39 Stage 3 Temporal in V8 today. Heading for Chrome 144 🎉
By many metrics this new date-time API is the single biggest change to JS ever 🔥
V8 uses Boa's temporal_rs by @jason-williams.co.uk Kevin Ness & Manish 👍
Congrats to @manishearth.bsky.social on unflagging TC39 Stage 3 Temporal in V8 today. Heading for Chrome 144 🎉
By many metrics this new date-time API is the single biggest change to JS ever 🔥
V8 uses Boa's temporal_rs by @jason-williams.co.uk Kevin Ness & Manish 👍
Reposted
ok this breakdown of AI writing indicators is incredible. Huge shout-out to the Wikipedia community for this
Wikipedia:Signs of AI writing - Wikipedia
en.wikipedia.org
September 28, 2025 at 2:41 PM
ok this breakdown of AI writing indicators is incredible. Huge shout-out to the Wikipedia community for this
Reposted
added a cheat sheet to the official Git website
(with a lot of help from other folks who work on the website)
git-scm.com/cheat-sheet
(with a lot of help from other folks who work on the website)
git-scm.com/cheat-sheet
Git Cheat Sheet
git-scm.com
September 16, 2025 at 6:28 PM
added a cheat sheet to the official Git website
(with a lot of help from other folks who work on the website)
git-scm.com/cheat-sheet
(with a lot of help from other folks who work on the website)
git-scm.com/cheat-sheet
Reposted
I've done innovative work before. For me to continue innovating would be a creative slump, a disappointing lack of originality.
August 3, 2025 at 1:47 PM
I've done innovative work before. For me to continue innovating would be a creative slump, a disappointing lack of originality.
Reposted
Reposted
Almost 4 months later, here it finally is:
uv: Making Python Local Workflows Fast and Boring in 2025
youtube.com/watch?v=TiBI... 1/3
uv: Making Python Local Workflows Fast and Boring in 2025
youtube.com/watch?v=TiBI... 1/3
https://youtube.com/watch?v=TiBIjouDGuI…
July 6, 2025 at 6:44 PM
Almost 4 months later, here it finally is:
uv: Making Python Local Workflows Fast and Boring in 2025
youtube.com/watch?v=TiBI... 1/3
uv: Making Python Local Workflows Fast and Boring in 2025
youtube.com/watch?v=TiBI... 1/3
Reposted
A brief history and (ab)use of __VA_OPT__: tavianator.com/2025/cpp_chu...
Taking the C preprocessor to Church - tavianator.com
tavianator.com
June 26, 2025 at 6:38 PM
A brief history and (ab)use of __VA_OPT__: tavianator.com/2025/cpp_chu...
Reposted
This article links tech layoffs that started in 2022 to a Section 174 change in the Tax Cuts and Jobs Act, which ended immediate R&D write-offs.
The assumption was companies using savings from the tax cuts to cover the increased tax bill on R&D spending. Instead they’ve cut headcount.
The assumption was companies using savings from the tax cuts to cover the increased tax bill on R&D spending. Instead they’ve cut headcount.
The hidden time bomb in the tax code that's fueling mass tech layoffs
A decades-old tax rule helped build America's tech economy. A quiet change under Trump helped dismantle it
qz.com
June 7, 2025 at 11:19 AM
This article links tech layoffs that started in 2022 to a Section 174 change in the Tax Cuts and Jobs Act, which ended immediate R&D write-offs.
The assumption was companies using savings from the tax cuts to cover the increased tax bill on R&D spending. Instead they’ve cut headcount.
The assumption was companies using savings from the tax cuts to cover the increased tax bill on R&D spending. Instead they’ve cut headcount.
Reposted
typst: A new markup-based typesetting system that is powerful and easy to learn. ★37477 https://github.com/typst/typst
typst / typst
A new markup-based typesetting system that is powerful and easy to learn.
github.com
February 16, 2025 at 12:20 AM
typst: A new markup-based typesetting system that is powerful and easy to learn. ★37477 https://github.com/typst/typst
Reposted
[SIGMOD '25] Low-Latency Transaction Scheduling via Userspace Interrupts
www.cs.sfu.ca/~tzwan...
Since Sapphire Rapids, Intel has added support for user interrupts, which can be used to implement a preemption-based scheduler for user-level threads. lwn.net/Articles/869...
www.cs.sfu.ca/~tzwan...
Since Sapphire Rapids, Intel has added support for user interrupts, which can be used to implement a preemption-based scheduler for user-level threads. lwn.net/Articles/869...
February 16, 2025 at 4:48 AM
[SIGMOD '25] Low-Latency Transaction Scheduling via Userspace Interrupts
www.cs.sfu.ca/~tzwan...
Since Sapphire Rapids, Intel has added support for user interrupts, which can be used to implement a preemption-based scheduler for user-level threads. lwn.net/Articles/869...
www.cs.sfu.ca/~tzwan...
Since Sapphire Rapids, Intel has added support for user interrupts, which can be used to implement a preemption-based scheduler for user-level threads. lwn.net/Articles/869...
Reposted
We’re building a new static type checker for Python, from scratch, in Rust.
From a technical perspective, it’s probably our most ambitious project yet. We’re about 800 PRs deep!
From a technical perspective, it’s probably our most ambitious project yet. We’re about 800 PRs deep!
January 29, 2025 at 5:18 PM
We’re building a new static type checker for Python, from scratch, in Rust.
From a technical perspective, it’s probably our most ambitious project yet. We’re about 800 PRs deep!
From a technical perspective, it’s probably our most ambitious project yet. We’re about 800 PRs deep!
Reposted
got to write this extremely fun answer on langdev stack exchange this evening and man I love Daan Leijen so much langdev.stackexchange.com/a/4242/861
![[excerpt from the linked answer that starts partway through]
When this function is called, result_location will record the address of wherever result happens to be stored on the stack. Control then yields to the enclosing continuation prompt, and some time later, the continuation is restored. Unless the stack frame for foo happens to be restored to precisely the same location, the write to *result_location will fail to update the new location of result and will instead clobber whatever now happens to be at that address.
Given this fundamental issue, most programming language implementors consider implementing delimited continuations that capture the C stack to be a complete non-starter.
Doing it anyway
Fortunately, Daan Leijen is not most programming language implementors. His audaciously-named 2017 publication Implementing Algebraic Effects in C describes an implementation strategy for delimited continuations that really do capture and restore C stack frames.
How does he do it? By simply always restoring the continuation to exactly the place it was captured from, of course! In § 4.3 Resuming, Leijen describes his implementation strategy:](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:fp4zjiflmhhaocasp4yblehe/bafkreidgzguyemf525vhz7efgbozyfegnyveufdqjanwuadms35ywhilei@jpeg)
January 5, 2025 at 2:39 AM
got to write this extremely fun answer on langdev stack exchange this evening and man I love Daan Leijen so much langdev.stackexchange.com/a/4242/861