Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
steveruizok
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
1.
▲
I'm pretty sure isRecord is tldraw's fault
(tldraw.dev)
3 points
by
steveruizok
2mo ago
|
0 comments
2.
▲
Code sandbox with hot reload for ESP32 devices
(resident.inanimate.tech)
4 points
by
steveruizok
4mo ago
|
0 comments
3.
▲
An exhaustive review of design tool hover areas
(tldraw.dev)
2 points
by
steveruizok
5mo ago
|
0 comments
4.
▲
by
steveruizok
7mo ago
This is an incredible price. Lucky students.
5.
▲
by
steveruizok
7mo ago
Sorry Simon, I honestly didn't expect this to be posted anywhere https://x.com/just_be_dev/status/2026419663505072195
6.
▲
by
steveruizok
7mo ago
We're in chats with the GitHub team, they're taking it really seriously. I consider our pause on contributions similar to pi's open source vacation, we'll figure it out. https://github.com/badlogic/p
7.
▲
Show HN: Together, multiplayer drawing chat room
(together.tldraw.com)
2 points
by
steveruizok
7mo ago
|
1 comments
8.
▲
by
steveruizok
7mo ago
Author here. tldraw is not an open source project. It used to be but we switched to a commercial license for our v2 in 2023. The old v1 is still available under MIT; and I try to put as much as we can under MIT license where it makes sense,
9.
▲
by
steveruizok
7mo ago
(author here) Code quality matters a lot—we make an SDK, we sell our code. I'm writing my own code with the assistance of AI tools. When I'm asking an agent to step in, I can recognize when the tools are producing poor results, I
10.
▲
by
steveruizok
7mo ago
(author here) To be fair, we also were getting plenty of poor PRs that implemented well-described issues. Or hey, maybe they were poor and maybe they weren't, but they were someone else's "claude please fix" and I don&#x
11.
▲
by
steveruizok
7mo ago
OP here: /s
12.
▲
by
steveruizok
7mo ago
Hey, OP here. Shitty issue command is fine in a world where I have time to review it and expand it, just like I would have before; except now, there's a 80% chance that actually the AI got it right and I have a well-researched issue th
13.
▲
by
steveruizok
8mo ago
Reviewing code is much less of a burden if I can trust the author to also be invested in the output and have all the context they need to make it correct. That's true for my team / tldraw's core contributors but not for exter
14.
▲
by
steveruizok
8mo ago
I have a GitHub action that labels and tags issues automatically. It also standardizes the issue title. I love this script and would recommend it to anyone. https://github.com/tldraw/tldraw/blob/ce745d1ecc1236
15.
▲
by
steveruizok
8mo ago
Hey, Steve from tldraw here. We use AI tools to develop tldraw. The tools are not the problem, they're just changing the fundamentals (e.g. a well-formed PR is no longer a sign of thoughtful engagement, a large PR shows more effort tha
16.
▲
by
steveruizok
1y ago
Want to email me steve@tldraw.com? We're looking at an issue with new accounts today on tldraw.com but it sounds different from what you're describing.
17.
▲
by
steveruizok
1y ago
I'd like to do self-serve pricing like that, maybe we will in the future, but I don't think there are as many teams as you think where the difference would be a deciding factor. When I was doing pricing discovery and asking early
18.
▲
by
steveruizok
1y ago
I think we’ll do extended trials for small teams if they’re pre-revenue / pre-funding, and I can imagine setting up some relationships like that with incubators etc. A few other posters have asked the same question and it’s a good one,
19.
▲
by
steveruizok
1y ago
We support iPad about as good as we can, with stylus pressure and some tricks to avoid slowdowns due to the high input rate. I actually did the ink in Excalidraw too, so it at least worked last time I touched it! But the difference between
20.
▲
by
steveruizok
1y ago
You can stay on 3.x. The license on 3.x shows a watermark and a license key will hide it. New commercial licenses will still work for 3.x too, in case you’re unable to upgrade, though 4.x has only a few small breaking changes.
21.
▲
by
steveruizok
1y ago
Small teams are so hard to price for. When we first launched we had a non-commercial license and I was spending forever negotiating these tiny deals with teams where that was already a huge expense. The watermark solution we brought on last
22.
▲
by
steveruizok
1y ago
Thanks! Granular permissions are a common feature request, especially in education, so there’s a good chance we work on that this quarter.
23.
▲
by
steveruizok
1y ago
Sorry for the logins around collaboration. I really liked the open collaboration feature too but we were getting some sketchy user behavior around it and my nerve broke. You can still join someone else’s board anonymously though. When you s
24.
▲
by
steveruizok
1y ago
Yeah, this is the current gap in the offering. Pricing is such whackamole. I expect we’ll offer extended free trials to teams that need longer to get off the ground.
25.
▲
by
steveruizok
1y ago
Hey, thanks! React Flow is more narrowly focused on flow charts and workflows. It’s also MIT licensed and much more popular (looking at NPM installs) and sells premium access to docs and examples, while we license the library directly. Our
26.
▲
by
steveruizok
1y ago
Here’s a resource for more LCM models, which were built over Stable Diffusion. The inference provider is less a design piece than a detail. https://huggingface.co/latent-consistency
27.
▲
by
steveruizok
1y ago
We did a similar thing at tldraw with Draw Fast ( https://drawfast.tldraw.com/ ) and it was very fun. Inspired a few knock offs too. We had to shut it down because it was getting popular on Russian Reddit. A related project L
28.
▲
Patchfork: A tiny, fast, and clever immutable state utility for TypeScript
(github.com)
2 points
by
steveruizok
1y ago
|
0 comments
29.
▲
by
steveruizok
2y ago
That redirect is a bug for sure, thanks for pointing it out. We have all those examples on the index page for logged in users but I can see how it would seem like they’d disappeared.
30.
▲
by
steveruizok
2y ago
Thanks for the links! I should really share the design doc from when we started putting this together. The core idea here was a) making a little hobby machine on the canvas and b) using LLMs to “power” the widgets. Somehow that ended up loo
More ›