aidenyb
Re:Ghostty compiled to WASM with xterm.js API compatibility
on Monday December 01, 2025 @08:20PM (#46116096)
This is great. I've been using code-server to embed VSCode into the browser and been missing the terminal functionality. Excited to try this out.
Show HN: Grab elements from your page and give it to AI
Hey HN! I made a tool to grab elements from your page and give it to Cursor, Claude Code, and others as context.I spend a ton of time vibe coding and one of my gripes is coding agents have a hard time finding the element I'm talking about. I wished I could say "fix this" and the agent would know.React Grab basically fixes this by copying the selected element's information (like React component...
Show HN: Tool to visualize any React app
Show HN: Reverse Engineering React.js Internals
I’ve been exploring React.js internals and found them hard to access, so I reverse-engineered how React DevTools hooks into React and built a package: https://github.com/aidenybai/bippyFor a bit of context: React represents UI as a tree of "fibers," which hold data like props, state, and context. React updates UI in two phases: render (building the fiber tree) and reconciliation (scheduling...
Show HN: Scan for React Renders
Show HN: Million Lint – ESLint for Performance
Hey HN! Founder of Million – We’re building a tool to that helps fix slow React code. Here is a quick demo: https://youtu.be/k-5jWgpRqlQFixing web performance issues is hard. Every developer knows this experience: we insert console.log everywhere, catch some promising leads, but nothing happens before "time runs out." Eventually, the slow/buggy code never gets fixed, problems pile up on a...
Re:Show HN: Million 3 – Optimizing compiler for React
on Friday February 09, 2024 @01:33AM (#39312062)
Holy crap you're right, that was a VERY large image, fixed: 18.5MB -> 21KB
Re:Show HN: Million 3 – Optimizing compiler for React
on Friday February 02, 2024 @07:42PM (#39236484)
hi, this is aiden
around 2 yrs ago, i messed up benchmarks in the past with million v1. i'm sorry about putting out false information. once the reddit post came out i stopped working/advertising million entirely. i then spent 3 months redesigning the entire library. i tried my best to make it as fast as possible and accurate. benchmarks are real now, see here: https://krausest.github.io/js-framework-benchmark/current.ht...
Show HN: Million 3 – Optimizing compiler for React
Show HN: I made a tool that makes React faster automatically
In brief: I'm Aiden, 18, and have spent the past 2 years of high school working on Million.js, an open source React alternative with 11K stars on GitHub and hundreds of thousands of npm downloads.Recently, I released automatic mode, which detects slow React components and automatically optimizes the reconciliation phase. It's still in beta but chugging along. It's around 70% faster than React...
Million.dev
Virtual DOM: Back in Block
Re:Million: less than 1kb virtual DOM that is fast
on Saturday July 30, 2022 @11:43PM (#32292963)
Million was originally created as a Virtual DOM -- and still ships as a Virtual DOM. More recently, Million added an optional react compat library in order to make it easier for users to learn about Million.
I'm open to different ways to market Million if there is a specific tagline you have in mind
Re:Million: less than 1kb virtual DOM that is fast
on Saturday July 30, 2022 @11:14PM (#32292816)
Thanks! We're planning on adding a benchmark soon: https://github.com/aidenybai/million/issues/37
Re:Million: less than 1kb virtual DOM that is fast
on Saturday July 30, 2022 @11:12PM (#32292809)
Thanks for the feedback, Million has a React compat layer https://millionjs.org/docs/start-here too
Re:Million: less than 1kb virtual DOM that is fast
on Saturday July 30, 2022 @11:11PM (#32292802)
That's a fair point, seems like the current issue owner is inactive on the task, I'll go in myself and start work on a benchmark. Million started out as only a virtual dom (and therefore was never added to the js-framework-benchmark). Only recent was the React compat added, which is when we were comfortable to start working on benches.
My intention wasn't to dismiss your point at all btw. My intention was if there wasn't any 3rd party benchmark for a library (like js-framework-benchmark), you shouldn't take claims at face value unless you've done due diligence. It's great to hear that you're keeping yourself accountable, hopefully Million will also sometime soon :)
Re:Million: less than 1kb virtual DOM that is fast
on Saturday July 30, 2022 @10:52PM (#32292717)
Author of Million here -- Don't trust my benchmarks at face value! Always run your own benchmarks
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @02:21PM (#31585949)
This sounds like a websocket version of Astro (https://astro.build)! Very cool stuff.
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @02:19PM (#31585930)
I have yet to explore this area, I'll check out S.js!
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @02:18PM (#31585918)
Check the value prop: https://github.com/aidenybai/million#what-is-million
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @01:06PM (#31584860)
I'm aware! AFAIK it's just a auto memoizer for React currently
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @12:11PM (#31584049)
Hey, author here of this Show HN post. I appreciate all the comments on the post, but I would appreciate if content you post is on topic. I love the discussion about HN culture but I don't think it's relevant to this post, and it's quite overwhelming to read so many comments. If you'd like, you can start your own discussion on HN about this rule (as long as it is along the HN guidelines).
Other than that, thank you so much for all the awesome feedback, it's really appreciated :)
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @12:07PM (#31583979)
Million's docs uses https://github.com/shuding/nextra, which uses React + Next.js for underlying code
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @12:06PM (#31583965)
Not sure why that's happening, looking into it
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @12:05PM (#31583957)
Not similar to SolidJS in internals (fine grained rendering), but same idea of compiling JSX and optimizing it beforehand
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @01:30AM (#31578470)
Just to add on here, the Preact author made a generalized utility for tagged template => vnode conversions: https://github.com/developit/htm
Re:Show HN: I made React with a faster Virtual DOM
on Wednesday June 01, 2022 @12:09AM (#31577966)
I made some adjustments to the README [1], thanks again for the helpful feedback.
Re:Show HN: I made React with a faster Virtual DOM
on Tuesday May 31, 2022 @11:44PM (#31577801)
Thanks!
Re:Show HN: I made React with a faster Virtual DOM
on Tuesday May 31, 2022 @10:58PM (#31577518)
I love the work done by the Lit team (I assume you're a contributor?). It's really fantastically designed, as you mentioned with bundle size/rendering speed/etc. I'm sure that Lit's implementation is very efficient and ranks high in benchmarks.
This isn't to say virtual DOM isn't fast Experimental libraries that use virtual DOM's like blockdom and ivi (see https://krausest.github.io/js-framework-benchmark/2022/table...) are very, very fast.
At the end of the day, the way libraries render UI is a set of tradeoffs. No one method is objectively better. While lit works great for a lot of web developers, so do virtual DOM based libraries
Totally agree on native DOM diffing, I'll check out Apple's proposal :)