Viewing profile — thomasnowhere
thomasnowhere
HN member- Joined
- Sun, Mar 22, 2026, 9:48 PM UTC
- HN karma
- 7
- Public activity
- 15 items
- HN profile
- View on Hacker News ↗
About thomasnowhere
https://domternal.dev https://github.com/domternal/domternal
Recent public activity
-
comment
Comment #49184937
This, pretty much exactly what I've been noticing too. Feel for the juniors though, its rough trying to learn when the tool in front of you can just spit the whole answer out. I st…
-
comment
Comment #49184280
[dead]
-
comment
Comment #48759778
[flagged]
- story
-
comment
Comment #48753993
[dead]
- story
-
comment
Comment #48292319
The cost of writing code dropped but the cost of maintaining it didn't. If anything that makes saying no more important, not less.
-
comment
Comment #48285924
One area where AI is reliably faster with no quality tradeoff is writing E2E tests. You can cover a ton of edge cases in an afternoon that you would normally skip, and if something…
-
comment
Comment #47689220
[dead]
- story
-
comment
Comment #47677549
The never-resolving promise trick is clever but what caught me off guard is how clean the GC behavior is. Always assumed hanging promises would leak in long-lived apps but apparent…
-
comment
Comment #47535507
This looks nice. I work on a rich text editor and have a large Playwright test suite. The hardest bugs to catch are always the ones where a speciffic sequence of user actions leave…
-
comment
Comment #47507750
That makes sense, the hidden input approach is clever. Google Docs definitely proved it's viable at scale. The RTL support is a nice touch, that's notoriously tricky to get right. …
-
comment
Comment #47503185
Impressive that you built the rendering layer from scratch on Canvas. Curious about one thing though, how do you handle accessibility? With contenteditable you get a lot of browser…
- comment