I'm finally starting to pick up Go and try to formally learn it. It's got a lot of wild features! First language I've used in quite a while that natively supports complex numbers, seems like an interesting choice. The swapped type declaration order is gonna take a while to get used to.

First of these optimizations rolled out in v1.15.0 with a reduced scope. Next version of oxlint will be even faster: github.com/oxc-project/... On my laptop: ~15% faster on `oven-sh/bun`, ~9% faster on `microsoft/vscode`, ~11% faster on `posthog/posthog`, and ~8% faster on `elastic/kibana`

VoidZero x SquiggleConf: Win a ticket! VoidZero is a proud sponsor of this year's @squiggleconf.com on September 18th and 19th in Boston. We've got an extra ticket for the event and want to give it away to one of you so you can join us there! Learn in this thread how you can enter the raffle 👇

Trying some new oxlint optimizations. This PR has gone over several iterations in the last few months and the core idea is simple: don't run rules for files if they don't apply (using an AST node bitset lookup). The result: linting is around 15% faster in practice.

Announcing Oxlint Type-Aware Preview oxc.rs/blog/2025-08...

Cool to see more tsgo-based linters! I think best practices here are not known yet, so it is great to see more teams innovating on this.

Great news for anyone linting large repositories! Hopefully this will be an easy performance win for teams using ESLint.

Just had a listen to this, it's well worth listening to catch up on the current state of JS linting, as Josh has lots of experience from working on ts-eslint. Lots of innovation happening in linting currently Overall, I think right now is a great time to learn more about linting, parsing, and ASTs.

First version is out! It's still pretty experimental, but we will keep improving performance and fixing bugs with each version. Most importantly though: you can use it now!

`oxlint --type-aware`. Mic drop. It's incomplete and have numerous problems, including a noticeable performance issue. BUT, you can finally see your floating promises quickly! Example PR: github.com/rolldown/rol... Problems: t.co/K7ZVnPjOPL

It's been great to work on prototyping this! I'm really excited by typescript-go and looking forward to getting this released as soon as we can. The future is fast ⚡️

I am permitted to host tsgolint in Oxc and explore type aware linting! I am super excited! We reduced the original scope of tsgolint to be a backend for oxlint, taking the best out of both worlds! github.com/oxc-project/...

Introducing tsl, an extension of tsc for type-aware linting! Want to speed up your ESLint time without losing the great type-aware rules from @typescript-eslint.io? Run `bunx tsl --migrate` to try it out! github.com/ArnaudBarre/...

This is the best explanation of ARIA that I've seen. There is so much practical advice in here as well!

We're thrilled to announce the first stable release of Oxlint - version 1.0! Our Rust-powered JavaScript/TypeScript linter delivers 50~100x faster performance than ESLint with 500+ rules and zero configuration required. Time to give it a try! voidzero.dev/posts/announ...

Today we are excited to announce Rolldown-Vite: a technical preview of the version of @vite.dev entirely powered by the Rust stack we built over the past year (Oxc + @rolldown.rs) voidzero.dev/posts/announ...

For the Oxlint 1.0 announcement, I'd like to show more real world performance numbers on large repos. If Oxlint has been satisfactory, would you be keen to send me the numbers Oxlint reports at the end? If you have never tried Oxlint but has a large repo: `npx oxlint@latest`.

I got involved with oxc because I just showed up, looked at the issues available and suggested solutions, and started making contributions. It was also nice to not have the pressure of being publicly assigned to it so I could take my time and learn as I went.

If you find an OSS issue that calls your attention, go for it. You don't need to ask permission to start working or have it assigned to you. If someone else sends a PR before you, that's great. You can use your knowledge of the issue to help review the PR, add tests, and validate the approach.

Happy to see Mercedes Benz adopting modern tooling such as @rolldown.rs and Oxc in their workflow, as well as going the extra mile and sharing their results! Up to 64% CI pipeline time reduction is impressive 👀 And more per improvements are yet to come 🤯 www.mercedes-benz.io/blog/2025-05...

Σ Experimental bundle analyzer in the last version of obuild.unjs.io @rolldown.rs is fast enough that we can build a package, generate types, then bundle it again, minify it with OXC, and then bundle again!! (for side-effect check) and still takes <50ms for a small lib!

A proof of concept to run ast-grep via OXC parser

On Oxlint JS plugins: we've created a survey to gather requirements and would love to hear your thoughts. The linked discussion includes background information and potential approaches we could take. github.com/oxc-project/...

I'm starting "This week in Oxc" to improve roadmap visibility. Feel free to subscribe to this thread. github.com/oxc-project/...

In the latest version of the `oxc` VS Code extension (0.16.5), lint fixes now use the provided fix message whenever possible, making it much more clear what the fix will do. Previously, this just appeared as "Fix XYZ problem".

There have been a number of bug fixes and improvements to the editor experience for oxlint recently. If you have run into any bugs or issues with the `oxc` extension in VS Code, we would be interested to hear about it: github.com/oxc-project/...

Want to follow all updates + people involved in and around @voidzero.dev projects here on Bluesky? Then make sure to check out our starter pack! go.bsky.app/Sbpuppb

Oxlint has now reached a beta version! It's faster than ever, has over 500 rules built-in and we are working on adding lots more features. We are also working towards supporting custom plugins as well 🙏

500 Oxlint rules. What a remarkable achievement by everyone who has contributed to OXC. It was only 11 rules when I completed the prototype back in June 2022.

Oxc v0.53.0 now returns an estree for direct consumption in JavaScript through napi and wasm APIs, no more ugly work arounds. github.com/oxc-project/...

2025 resolution: don't buy any new domain names (challenge level: impossible)

Optimist: The cup is half full Pessimist: The cup is half empty Programmer: The cup should never have anything in it, TODO: figure out why this happens sometimes

My latest blog post covers how a simple observation at airport security highlights the concept of Betterment and how it applies to engineering teams. Which group are you in? angiejones.tech/the-betterme...

in an upcoming oxlint release, overrides will now be resolved relative to the config file location: github.com/oxc-project/... so this now works correctly: ``` { "rules": { "no-debugger": "off" }, "overrides": [{ "files": ["src/*"], "rules": { "no-debugger": "error" } }], } ```

💯 Principles we should all be living by. @ericwbailey.website at #perfnow

Guys literally want only one thing and it's widely accessible and affordable public transit involving trains and buses

Society if engineers were banned from playing Factorio:

I am now a core member of the oxc team! github.com/oxc-project Thanks to @boshenc.bsky.social for being welcoming to new contributors like myself and creating a great tool.

This is your weekly reminder to run `git gc` and `cargo clean`

this 100% matches my time at github (3 years now!!)

TIL about surrogate pairs: en.wikipedia.org/wiki/UTF-16#... All things related to text encoding just confuse me, I think 😅

pov: you are a dog treat being eaten #corgisky

Welcome @boshenc.bsky.social!

and in this new country, we shall have 13 different types for text and text shall be known as strings and we shall call lists of things "vectors." what's the difference? nobody knows.

Bluesky’s captured tech twitter because it appeals to our innate desire to buy a new domain name.

Playwright accessibility tip: Prefer using native locators over `.locator()` directly For example: prefer `.getByLabel(...)` instead of `.locator('[aria-label="..."]')`. This focuses the test on accessibility semantics instead of implementation details. This makes it more robust when refactoring.

I created a Bluesky Starter Pack! 🎉 It includes ~75 wonderful people in the web dev community who are doing inspiring work. I know I’ve missed some folks; I plan on adding to it over time. Starter packs are such a great idea. Immediately makes Bluesky feel less lonely for newcomers. 😄

I recently did some performance optimization work on oxlint and made it up to 33% faster at linting the VS Code repository. It can lint over 5000 files with 100 rules in just about half a second. github.com/oxc-project/...

I don't think I realized how bad the X/Twitter website had gotten until I moved here. Bsky website is so much faster and less buggy.

obligatory puppy coworker pics: