markusw

10 ms·

121.
Show HN: gomponents, HTML components in pure Go(gomponents.com)
15 points by markusw 3y ago|6 comments
122.
by markusw 3y ago
Ha, I’ve started the same thing in Go, but didn’t get that far. https://github.com/maragudk/sqlite
123.
by markusw 3y ago
Yeah, it's not exactly a new idea. I'm actually a bit surprised it's this popular. :D Thanks! Doing it in another language would be almost trivial, there's really not a lot of code involved. I've focused mostly on m
124.
by markusw 3y ago
Ooooooooh. TIL!
125.
by markusw 3y ago
See the other thread on naming. ;)
126.
by markusw 3y ago
Haha, you got me. :D
127.
by markusw 3y ago
There you go! :D https://github.com/maragudk/goqite/pull/31
128.
by markusw 3y ago
Yeah, that’s a good idea! I was today old when I learned that SQLite can have transactions across separate db files.
129.
by markusw 3y ago
Well peepz, it’s been fun, but I’m off to bed now because sometimes I get sleepy. Ta! :D (Thank you for all the comments!)
130.
by markusw 3y ago
I also don’t like those parts, but for an otherwise great project, I’d happily use the parts I do like. Strict tables go a long way for me, and you can make foreign key checks a compile-time enforcement.
131.
by markusw 3y ago
Thank you, I’m really glad you like it! :)
132.
by markusw 3y ago
See this other thread: https://news.ycombinator.com/item?id=39670199
133.
by markusw 3y ago
I don't understand your comment. Abstracting away the SQL is exactly what this library does (and pretty much the only thing): Send, Receive, Delete methods. Could you clarify?
134.
by markusw 3y ago
It really is! I've become a SQLite fanboy. :D Although I can definitely see the value in Postgres as well. But it's usually one of those two.
135.
by markusw 3y ago
It has a Go API. ;) Check the source, that's essentially what it is. But you get this particular design, the tests etc. for free, so if you value your time, maybe this is worth something to you. Maybe not though. Either way, it's
136.
by markusw 3y ago
Feedback and opinion are not the same thing. Also, yes, I will take on that risk. As anyone who has ever been at the receiving side of an issue tracker knows, not all feedback is equal. I appreciate taking the time to provide feedback, thou
137.
by markusw 3y ago
Oh! TIL! Thank you for that. :)
138.
by markusw 3y ago
That’s the “received” column. :) Messages after X attempts aren’t received by the normal receiver method anymore.
139.
by markusw 3y ago
If you want to be able to send to the queue in the same transaction as other state changes, it has to be the same file. That’s often a useful property.
140.
by markusw 3y ago
Which is very much your right. Agree to disagree? :D
141.
by markusw 3y ago
It’s bring-your-own-driver, so you can use a CGo-free one. :) The one in go.mod is only used in tests.
142.
by markusw 3y ago
I've updated the code example to reflect this.
143.
by markusw 3y ago
Didn’t take it that way, but thank you for the clarification. :) And thanks! Likewise. :D
144.
by markusw 3y ago
I actually quite like it. :D
145.
by markusw 3y ago
Interesting that it supports the Redis API as well! As noted elsewhere here, it was important to me to use SQLite, since that's what I use as the storage layer already. But I've added HTTP adapters for remote clients. I hadn'
146.
by markusw 3y ago
Yeah, there are a lot of queue libraries like ours. :) It was important to me it was SQLite, since that's what I use as the storage layer already.
147.
by markusw 3y ago
This exactly. If you're using SQLite in your Go project, you most probably already have your sql.DB and schema migrations sorted, so I don't want to get in the way of that. :) (But I can see how that could be clearer from the exam
148.
by markusw 3y ago
Hehe. Perhaps.
149.
by markusw 3y ago
Nah, I've already got the domain. :D
150.
by markusw 3y ago
Thanks! See the first sentence of the readme. ;) "goqite (pronounced Go-queue-ite) is…"

More ›