it’s a crime that most universities don’t teach concurrency models with DSA. it permeates not only every facet of modern engineering but also shows up everywhere in everyday life.
scrolling before bed? serial
singing in the shower? parallel
talking with support? usually async
learning via hierarchical memory seems quite appealing and likely necessary in the continuous regime
i’m uncertain as to whether transformers will be the best continual learners — especially wrt to KV cache compression as latent space memory
1 Year of Research coming to an end. 8 Months seeing no results, Almost quitting twice. November/December of last year finally seeing a very narrow path to a universal 2x perf improvement on every modern JS parser which would take me another 4 months to build.
This will land in oxc_parser fairly soon speeding up OXLint, OXFmt, Vite, Rolldown, Deno (oxc consumer) almost immediately.
In the long term it's likely that it will land in V8/SpiderMonkey/Bun/JavascriptCore/Typescript/+ Every other JS parser implementation
The wins come from a few key elements, obviously 1 novel "SIMD For Context Sensitive Languages" the other key elements take it from a 20% win e2e to a 80-200% win (99% of files will see a 80-100% perf improvement).
These key elements translate to any AST design and thus will speed up not only all JS tooling but every major browser when complete.
@threepointone@gr2m fixing this.activeResponse should also address the race conditions in this longstanding issue we’ve been working around: https://t.co/stPLLcWHxI
GitHub Actions steps can now run in parallel using new keywords for background execution and control.
• Run steps concurrently with separate logs using background, wait, wait-all, cancel, and parallel commands
https://t.co/qDtbazv5VG
just migrated the monorepo from eslint to oxlint (w react compiler support!)
went from 2-3min, fan turning on, 24GB+ RAM usage to sub 1 sec passes looking effortless
📣 TypeScript 7's Release Candidate is now out! 📣
The new native port is almost here. Try it out on your codebases, and make sure your team is ready for the upcoming 7.0 release!
https://t.co/WBCvxYHoJX
The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.
The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.
Access to all other Claude models is not affected.
We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.
Read our full statement: https://t.co/bwn0sximKZ
VoidZero is joining Cloudflare.
Our mission stays the same: to make JavaScript developers more productive than ever before. Vite, Vitest, Rolldown, Oxc, and Vite+ remain MIT-licensed. Evan and the VoidZero team will continue leading them.
Cloudflare shares our commitment to open source. Together, we can keep investing in the tooling developers rely on every day, while bringing the Vite ecosystem and Cloudflare’s platform even closer together.
Drizzle v1.0.0-rc.1 is out 🚀
▪︎ Effect v4 native support
▪︎ JIT row mappers to reduce ORM overhead to ~0
▪︎ Reworked casing API (breaking change)
▪︎ Drizzle for LLM agents (preview)
Drizzle is now as fast as using raw driver and mapping(or not mapping) results by hand 🙃
TypeScript 7.0 Beta is here!
Built on a new native and parallelized foundation, it's already being used on multi-million line codebases.
Read up more here and try it on your projects today!
https://t.co/mYN3MPp1ab
every junior SWE/current cs major needs to read this.
this perspective should not feel contrarian — what happened to holding oneself and one’s work to a standard?
As of today, Drizzle has become the most sustainablest ORM on Earth 🚀
PlanetScale hired entire Drizzle core team to work on Drizzle ORM full-time, which is just… WOW!
I mean, I can’t believe this is happening and how amazing this is going to be...
Let’s address the most important things:
▪︎ The governance of Drizzle does not and will not change
▪︎ Drizzle remains independent and open-source
▪︎ We will now work more full-timer on Drizzle ORM, Kit and Studio
▪︎ Our social media manager(me) will finally have a salary
▪︎ Drizzle v1 is going to be amazing
Thank you all for using Drizzle, without you there won’t be 1.2k GitHub issues and 355 PRs, we’d live a happy life, touching grass ❤️