Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
markusw
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
markusw
1y ago
I had no idea that was possible. I'll keep that in mind if I need a similar workflow. DuckDB is awesome. :D
32.
▲
by
markusw
1y ago
Oh, interesting! But that's more of a desktop application now, right? I was thinking of web servers when writing the article, but I can see how that's not totally clear. :-)
33.
▲
by
markusw
1y ago
Yeah, totally agreed. I'll have to look into that. I've really enjoyed the stability of SQLite, down to the file format.
34.
▲
by
markusw
1y ago
The biggest one is latency. Network latency will almost always be orders of magnitude bigger than I/O latency. There's a whole class of problems that goes away when latency becomes very small.
35.
▲
by
markusw
1y ago
Interesting! I'm going to look into that. :-) Thank you for sharing.
36.
▲
by
markusw
1y ago
While I really like DuckDB, I wouldn't use it for OLTP workloads. I'm curious, when do you want to treat your Postgres like SQLite? :-) That's basically the opposite of what I was thinking of in the article.
37.
▲
by
markusw
1y ago
On the other hand, and especially if migrating from SQLite, there's typically not _that_ much data. Even hundreds of GBs would probably be okay? Drives are so fast these days. Would be interesting to benchmark.
38.
▲
by
markusw
1y ago
Yeah, that really is a great thing about SQLite. I wonder whether packaging everything in Docker (including a specific Postgres container identified by hash or whatever) and deploying on the same architecture would solve this?
39.
▲
by
markusw
1y ago
Hehe. Yes and no. In the cloud, as you probably know, the usual way now is to spin up Postgres separately (RDS, Supabase, Planetscale, Crunchy Bridge, you name it). We've gotten so used to it that a different way of doing it is often n
40.
▲
by
markusw
1y ago
Indeed pondering! The dude here. I think writing a little piece like that often sparks some interesting discussions here and elsewhere. :-)
41.
▲
by
markusw
1y ago
It's also used plenty in the cloud, for a variety of reasons. Check out the first linked article for something I wrote on that: https://www.maragu.dev/blog/go-and-sqlite-in-the-cloud
42.
▲
What if we treated Postgres like SQLite?
(maragu.dev)
75 points
by
markusw
1y ago
|
81 comments
43.
▲
by
markusw
1y ago
You can easily do consistent backup on live databases. There’s a backup command and API.
44.
▲
by
markusw
1y ago
Thank you for answering. That's fair re. App Store rules. Feature flags FTW? :D I was happy to see that FTS5 was always enabled as a compile-time option.
45.
▲
by
markusw
1y ago
I've just tried it out, looks nice! I've been using TablePlus a lot, but there are some SQLite-specific features I'd really like to have in an app: - Foreign keys enabled by default, so I don't have to remember to enable
46.
▲
by
markusw
1y ago
Beautifully done, thank you for sharing. :-)
47.
▲
Show HN: GAI, a Go-idiomatic, lightweight abstraction on top of LLMs
(gai.maragu.dev)
2 points
by
markusw
1y ago
|
0 comments
48.
▲
by
markusw
1y ago
I wrote about this back in 2022, still applicable today: https://www.golang.dk/articles/benchmarking-sqlite-performan...
49.
▲
Running LLM evals right next to your code
(maragu.dev)
1 points
by
markusw
2y ago
|
0 comments
50.
▲
by
markusw
2y ago
My pulse is still higher than usual. We just spent an hour on this. This is an art game. :D Thank you!
51.
▲
by
markusw
2y ago
You’re missing MIDI controllers, of which there are plenty. :) Synth versions without the keys are often called “desktop versions”.
52.
▲
by
markusw
2y ago
I build my frontends with HTML using gomponents. The jury’s still out about how far I can get with just Go while incorporating LLMs into my apps, but I’m optimistic!
53.
▲
by
markusw
2y ago
Yep! "Boring tech" has basically become an established term at this point, I'm not going to change that.
54.
▲
by
markusw
2y ago
It's okay, sometimes the discussions turn interesting and I learn something. And a lot of people get to read my article, and I hope their lives are enriched in a small but meaningful way. I'm glad the approach works for you as wel
55.
▲
by
markusw
2y ago
I do! In the article, I mostly mean working with LLMs inside the applications I'm building, as opposed to as a tool as part of development. But I do both. Right now, I'm trying out Zed, which supports multiple LLMs natively. Just
56.
▲
by
markusw
2y ago
Because I don't know PHP, so that would be a terrible choice for me. But if that's what you're productive in, I'd say, absolutely!
57.
▲
by
markusw
2y ago
I think it's a great example of a modern, elegant, boring & productive language. But Go wasn't really the point of the article, so maybe we shouldn't be here doing language flamewars? :D
58.
▲
by
markusw
2y ago
The Javascript tooling ecosystem seems especially broken. XKCD 927 [0] applies there, to build systems, frameworks, and more. I would suggest trying a different ecosystem entirely. I chose Go's, but there are many alternatives not near
59.
▲
by
markusw
2y ago
I think they feel like pure science fiction magic. I have multiple alien brains installed locally on my laptop.
60.
▲
by
markusw
2y ago
My point isn’t about these particular technologies. Pick any you like. But maybe not the flashy new ones, but the ones that make you the most productive and don’t change a lot. And then add the fancy new LLMs.
More ›