thomasnowhere

5 ms·

1.
CRDT: Tree-Based Indexing (2022)(madebyevan.com)
1 points by thomasnowhere 23d ago|0 comments
2.
by thomasnowhere 1mo ago
same here, it reads exactly the same whether the number is real or completely made up, so the confidence stops meaning anything.
3.
by thomasnowhere 1mo ago
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 still think they're worth it, but tbh I just don&#x
4.
Show HN: Domternal – headless rich-text editor for Angular/React/Vue/Vanilla(domternal.dev)
1 points by thomasnowhere 3mo ago|0 comments
5.
by thomasnowhere 4mo ago
The cost of writing code dropped but the cost of maintaining it didn't. If anything that makes saying no more important, not less.
6.
by thomasnowhere 4mo ago
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 breaks you see it immediately.
7.
Show HN: Domternal – Rich text editor toolkit on ProseMirror with Angular UI(github.com)
2 points by thomasnowhere 5mo ago|0 comments
8.
by thomasnowhere 5mo ago
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 apparently not as long as you drop the references.
9.
by thomasnowhere 6mo ago
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 leaves the editor in a broken state, things like formatting insid
10.
by thomasnowhere 6mo ago
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. Great work pulling this off in 10 months. Good luc
11.
by thomasnowhere 6mo ago
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 accessibility features for free (screen readers, selection,