Connor Shea

@connorshea.bsky.social

150 Followers 253 Following

Software Engineer. Denver. I like Ruby, Rails, TypeScript, Rust. Building http://vglist.co, Oxlint core team. Not good at computers, just bad at giving up. I like housing. he/him

Benchmark table: import/no-cycle on the vscode corpus drops from 3520.0 ms (1.76.0) to 1143.9 ms (1.77.0), a 3.08× wall-clock speedup, faster in all 15 paired rounds.
Benchmark table of three builds: main (3341.9 ms, 330.98 M allocations, 1360.8 MB peak RSS) through the drop-two-Vecs-per-edge commit (1082.0 ms, 38.61 M, 1063.9 MB) — cumulatively 3.1× faster, 8.6× fewer allocations, 21.8% lower peak RSS.
Wall clock table showing import/no-cycle runtime dropping from 3330.5 ms to 966.3 ms on vscode src — 3.9× faster on the rule-attributable portion.
Benchmark table comparing allocation counts for corpus ~/code/vscode/src (7,368 files), counting global allocator, 2 reps each, run-to-run spread under 400 allocations (~0.0007%). Columns: metric, v1.75.0, main, delta, delta percent. Whole-process allocations 57,248,774 → 52,996,284 (−4,252,490, −7.43%). Allocations minus parse-only baseline 55,589,803 → 51,337,178 (−4,252,626, −7.65%). Bytes requested 7.77 GB → 7.44 GB (−328.3 MB, −4.23%). Allocations per file 7,770 → 7,193 (−577).
Table comparing allocation counts and memory usage before and after an optimization, across two corpora. For n8n TS: allocations dropped from 1,949,840 to 14,252 (-99.3%), and bytes from 110.4 MB to 4.1 MB (-96.3%). For vscode src/: allocations dropped from 2,310,741 to 6,524 (-99.7%), and bytes from 129.9 MB to 1.9 MB (-98.6%).
Table titled "Results: main vs 3.0.0" comparing benchmark timings between version 3.0.0 and main across three fixtures (Radix at 2.5 KB, kitchen-sink at 716 KB, and cal.com at 1.4 MB). Columns are Benchmark, Fixture, 3.0.0, main, Change, and Speedup. read_span: Radix 1.62 µs → 173 ns (-89.5%, 9.4×); kitchen-sink 457 µs → 10.5 µs (-97.7%, 43.8×); cal.com 900 µs → 21.0 µs (-97.6%, 42.8×). render (color): Radix 11.3 µs → 1.35 µs (-88.1%, 8.4×); kitchen-sink 1.40 ms → 11.6 µs (-99.2%, 120×); cal.com 2.79 ms → 22.5 µs (-99.2%, 124×). render (mono): Radix 10.1 µs → 819 ns (-91.9%, 12.4×); kitchen-sink 1.37 ms → 11.0 µs (-99.2%, 124×); cal.com 2.90 ms → 21.9 µs (-99.2%, 132×). render_multi_label: Radix 22.9 µs → 4.06 µs (-82.0%, 5.6×); kitchen-sink 3.60 ms → 13.2 µs (-99.6%, 273×); cal.com 7.09 ms → 24.3 µs (-99.7%, 292×). Caption below the table: for read_span, throughput went from ~1.5 GiB/s to ~63 GiB/s on the large files.
Built oxlint (release) against main of oxc-miette vs. this branch of oxc-miette — identical except for the version of the miette dependency — and measured full-directory lint runs with hyperfine (default rules, output to /dev/null). Since parse + analysis is byte-identical between the two binaries, the entire delta is read_span: Then a table with the benchmarking results, with the following contents: On canvas-lms we lint ~10k files, get 3,149 diagnostics, and on main that runs in 370 ms, and on this PR it runs in 224 ms. So a 1.65x speedup. On the gitlab codebase we lint ~10.7k files, get 1824 diagnostics, and on main that runs in 579ms vs 438ms in this PR, so a 1.32x speedup. On a synthetic stress test file (2MB file w/ 4k diagnostics), we have 1 file, 4000 diagnostics, and on main it runs in 5.53s vs 1.01s on this PR, 5.47x speedup.
Batman holding his parents as they fade away, but Batman is the United States and his parents are Canada and Mexico. In the first panel, Batman says "No, No, stay with me!" and then "Don't leave me!!" while sobbing.
A GitHub pull request with the title 'docs: Update "Vite's future bundler" to "Vite 8's bundler"' Its description contains an image of Dewey, a child from Malcolm in the Middle, saying "The future is now, old man."
A red passport with "RUBY PASSPORT" on the front and a large gem icon with two fig leaves underneath sits on a desk. It also says `require "community"` at the top.
Claude: The script needs a fundamental redesign - it should work per-vec, not per-file, to avoid mixing types. Let me rewrite it with a Python script for the actual transformation logic. Me: you are NOT allowed to use python Claude: Got it, no Python. Let me rewrite the script using only shell and perl. First let me revert everything and start fresh. Me: NO PERL EITHER
A post by the OpenAI Developers twitter account from 1 hour ago, it says "Codex Security is now also available on ChatGPT Pro accounts."
A dropdown that says "Rules" with a search box where "arrow" has been input. The dropdown has two results: "eslint/arrow-body-style" and "vue/no-arrow-functions-in-watch".
Screenshot from the website, which features a basic UI for selecting linter plugins, filtering and selecting linter rules, and viewing and copying the generated JSON config file.
A screenshot of a terminal window with an error message from Oxlint. The error message says: Failed to parse oxlint configuration file. × Invalid configuration for rule `import/no-absolute-path`: unknown field `foobar`, expected one of `esmodule`, `commonjs`, `amd`, received `{ "foobar": true }` │ Invalid configuration for rule `import/no-duplicates`: invalid type: string "maybe", expected a boolean, received `{ "preferInline": "maybe" }` │ Invalid configuration for rule `no-cond-assign`: invalid type: integer `123`, expected string or map, received `123` │ Invalid configuration for rule `vue/define-emits-declaration`: unknown variant `declaration`, expected one of `type-based`, `type-literal`, `runtime`, received `{ "declaration": 0 }`
A prompt in the Graphite code review tool that says "Translate your existing git workflow to the equivalent Graphite commands."
Ryan Gosling (hot actor man) leaning against a wall with text overlayed that says "I already fucked up, 2027 will be my year"
Two blocks of Rust code with comments, each have Markdown syntax in the comments, with JSON code blocks in Markdown format. The first comment is a JSON blob that says `{ "this works fine and"; "does not crash the website generation" }`. The second comment is a JSON blob that says `{ "this comment will cause the website": "generation to crash :D" }`. The second comment is not indented, while the first comment *is* indented.
Screenshot from Spotify Wrapped, shows a photo of Carly Rae Jepsen and the text "You're a top 0.005% fan and you spent 4,215 minutes together"