Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
gavinhoward
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
61.
▲
by
gavinhoward
2y ago
Oh my goodness, thank you! I've been looking for that for AGES!
62.
▲
by
gavinhoward
2y ago
I don't want AI at all, but please read the article to understand what I mean by "friction."
63.
▲
by
gavinhoward
2y ago
Yes and no. Yes, flat design is too flat, and AI chat is too devoid of friction. But mobile and tablets are better at certain things [1], and we shouldn't get rid of that either. I saw somewhere (Bret Victor?) that tools have two parts
64.
▲
by
gavinhoward
2y ago
The author of the paper knows about bitslicing [1], so not mentioning it seems deliberate. My guess is that bitslicing only gets you so far. [1]: https://bearssl.org/constanttime.html#bitslicing
65.
▲
by
gavinhoward
2y ago
You could do that, except that you would register the handler before the network code executes. Then, on failure, the network code would run the handler that waits until activity resumes, then restarts.
66.
▲
by
gavinhoward
2y ago
I have rarely been so happy to see a post. I am working on designing a bug tracker, and this post completely clarified that I am going down the wrong road. Back to the drawing board.
67.
▲
by
gavinhoward
2y ago
Hey! Good to talk to you. Sorry, I was AFK for several hours. Thank you for the offer, but I don't think Yao should be featured yet. Edit: I guess I'll answer your questions anyway. > So Yao has a delineation between safe and u
68.
▲
by
gavinhoward
2y ago
Restarts don't always need a debugger or intervention. A classic case would be restarting memory allocation after failure and after the error handler freed cache memory. Another case would be retrying to open a file when the process ha
69.
▲
by
gavinhoward
2y ago
The errors that a procedure can run into are part of its interface. Languages like Zig and Swift make that explicit. The difference is that callers (even indirect callers) can register handlers to handle those errors without unwinding the s
70.
▲
by
gavinhoward
2y ago
No, it is much more powerful. ON ERROR RESUME NEXT is equivalent to a catch all in a try catch. Conditions and restarts let calling code set up error handlers, and if one of them handles the error, it would be like starting over from the to
71.
▲
by
gavinhoward
2y ago
I did, but my Gitea instance stopped working. I am trying to replace it.
72.
▲
by
gavinhoward
2y ago
I searched for conditions and restarts. I did not find them. That makes me sad because that is what my systems programming language uses. For context, conditions and restarts come from the Lisp world. They do not unwind the stack. Instead,
73.
▲
by
gavinhoward
2y ago
The cause of the GCC one has been found. It was me. Of course.
74.
▲
by
gavinhoward
2y ago
I solved it in mine. I should write a blog post.
75.
▲
by
gavinhoward
2y ago
The article is right: it is almost never a compiler bug. I have had that experience of reporting and being wrong. It sucks. On the other hand, I have a confirmed bug in Clang [1] and a non-rejected bug in GCC [2], so it does happen. [1]: h
76.
▲
by
gavinhoward
2y ago
> Do you mean that your system will have some built-in collaboration features? Yes. [1] But that is only chat/discussions. In the future, Yore might get real-time collaboration like Google Docs, but that depends on it taking off. &g
77.
▲
by
gavinhoward
2y ago
No, this is an executable without `-fPIC`. I am grateful that I only use one multi-call executable (built from a monorepo made partially because of your post, btw) because I think shared libraries in C might have the same sort of problems,
78.
▲
by
gavinhoward
2y ago
I can confirm that C (GCC and Clang) will generate this: 7e2f0: f3 0f 1e fa endbr64 7e2f4: 64 48 8b 04 25 f8 ff mov %fs:0xfffffffffffffff8,%rax 7e2fb: ff ff 7e2fd: c3
79.
▲
by
gavinhoward
2y ago
Makes sense. I want to build a "standard library" for my build system that would stoop to that. I can do that because my build system is not just a task graph executor; it is backed by a full programming language and can add its
80.
▲
by
gavinhoward
2y ago
Big fan. I wish you could write more. I am gonna go check the assembly of my own code for this. And I am going to integrate funtrace into my workflow. Question about your build system comment: my build system doesn't stoop to figuring
81.
▲
by
gavinhoward
2y ago
Gavin Howard here. Yes, GP is entirely correct. I want to do something like the article, but the bc standard (POSIX) requires a decimal BigInteger representation. I am glad you like my bc!
82.
▲
by
gavinhoward
2y ago
They could arbitrarily decide that I am a persona non grata and lock me out. They claim rights above what FOSS licenses allow, and I do not want that. I do not want my code to end up in their LLMs. Yes, I have blocked them from my self-ho
83.
▲
by
gavinhoward
2y ago
Yeah, I don't know why you were downvoted. I upvoted you because I was sure you were replying to me sincerely.
84.
▲
by
gavinhoward
2y ago
Mine will allow cloning all data, including issues, PRs, and real-time chats (Zulip-style). I think that might cover your bases.
85.
▲
by
gavinhoward
2y ago
You are absolutely right. To be honest, though, I don't want to even mirror that repo on GitHub. Not doing so means I don't have to agree on their onerous T&C for that code. I was planning on streaming my work on Twitch once I
86.
▲
by
gavinhoward
2y ago
It is not ready yet, sorry!
87.
▲
by
gavinhoward
2y ago
I can see your point. This is a good reminder to me that I need to control my tongue as well; I have said things like the Pijul author did in that thread, and I need to do better.
88.
▲
by
gavinhoward
2y ago
If you loved darcs, check out Pijul. They solved the exponential problem with first-class conflicts. Disclaimer: I am making a competitor to Pijul, but Pijul really is the spiritual successor to darcs.
89.
▲
by
gavinhoward
2y ago
Ah, cool!
90.
▲
by
gavinhoward
2y ago
Um, yeah. How do you know the name? I have never mentioned it by name, I think. Only linked to it occasionally. Edit: Another reason I am surprised is that Yore became its name only a few months ago.
More ›