ghoward

25 ms·

181.
by ghoward 4y ago
I have a relative that works for FreeTaxUSA. Thank you for using it! I'll let her know the ads work, thank you. I'll be happy to give her your comments.
182.
by ghoward 4y ago
No, I don't really agree. I don't like async because of something you accused conditions and restarts of: hidden control flow. In your example, I don't see any, which is great. But async can have hidden control flow. (I won
183.
by ghoward 4y ago
> This is exception semantics which is hidden control flow present in every language with exceptions. This is not exception semantics. A language can make the keyword "raise" do whatever it wants. Should I have used some othe
184.
by ghoward 4y ago
I am not working in industry; I'm such a loner programmer that I struggle in industry. But since my wife likes her work, I have space to write the software I want to write. My first goal is to make that software good enough and useful
185.
by ghoward 4y ago
Adding async to your error handling would just mean that you now have two problems.
186.
by ghoward 4y ago
> Every explanation of conditions and restarts I can find explicitly mentions searching the call stack for a handler and jumping into it, then reserving the capability to return to the function the error originated in. > This is expli
187.
by ghoward 4y ago
My ideal process ([1]) is...tedious. I never actually do it to that level, but my level of released bugs is low enough that what I actually do is good enough. But what it does give me is a template to follow and adjust as the circumst
188.
by ghoward 4y ago
Sure, but to add binary data to any executable on any platform is more involved. As an example, see [1]. That will turn any file into a C file with a C array, and I use it to embed a math library ([2]) into the executable so that the exec
189.
by ghoward 4y ago
And this is one of the many reasons I use ZFS personally.
190.
by ghoward 4y ago
Yeah, I agree, and I like C! I think the lack of bounds checks where they are not a problem is a massive design flaw nowadays. Zig should have made bounds checks universal and spent effort on compiler passes to elide them. Allowing people
191.
by ghoward 4y ago
Because code formatters cannot work on whitespace languages like Python. They can't adjust the indentation for you because they have to assume that the given indentation is intended. It also makes a lot of other automatic tools for d
192.
by ghoward 4y ago
Not GP. > I'm very skeptical that the lack of memory safety is not going to be an issue "in practice". For what it's worth, I agree with you. And I'm a C programmer that managed to put out a non-trivial piece of
193.
by ghoward 4y ago
> Zig did this with Rust's async/await, by making it colorblind. Zig's async/await is not colorblind. [1] It just appears that way at first because the compiler infers as much as it can at compile time. [1]: https:&#
194.
by ghoward 4y ago
This is a great answer, thank you. I think what hindered my understanding was the claim that Nix was purely functional, so it never made sense why flakes were needed. Knowing that Nix is not purely functional, i.e., that channels were sti
195.
by ghoward 4y ago
This is a great piece of advice. I hope it helps me someday.
196.
by ghoward 4y ago
> I am glad that you acknowledge that it is only how it makes you feel as the original comment that are the cause of such obviously weren't intended for you interpret them that way. Yes, but the unfortunate thing about Nix is that s
197.
by ghoward 4y ago
Thank you for the explanation. I'm going to go back through everything I've read and see where it helps me. However, I just want to address one thing. > To be honest, nix is a system you have to actually use to begin to underst
198.
by ghoward 4y ago
Can someone please ELI5 flakes to me? Specifically: * What they add from vanilla Nix. * What they take away. * How they work. * Why channels are unnecessary with flakes (once they're complete) as TFA implies. * How much they replace ho
199.
by ghoward 4y ago
You are absolutely right, especially about understanding the semantics of importing code in each language. Fortunately, with few restrictions, it is possible to use hacks to simulate the effect, mostly.
200.
by ghoward 4y ago
The common interface is dependencies and dependents, but the problem with existing build systems is that they make assumptions about those two things. They also place other restrictions. For example, the Go build system assumes you set up t
201.
by ghoward 4y ago
Funny thing: I just wrote about this in my blog. [1] Well, sort of. Many thanks to dang for this ever wonderful forum, the best on the Internet! [1]: https://gavinhoward.com/2022/07/lobste.rs-will-become-an-ech...
202.
by ghoward 4y ago
(This is the second part of my comments.) > This does not scale beyond a very small number of users... We are not talking about the Linux kernel. We are talking about an init/supervision system. Why are you moving the goalposts? I w
203.
by ghoward 4y ago
(Split my comment in two because HN complained it was too long.) > It is unclear what this "putting its fingers" actually means... Why does systemd need timers when cron exists? Why does systemd need to manage home directories?
204.
by ghoward 4y ago
> You will not have this without changing the kernel itself, /sbin/init needs to run as the root process of all other processes on the machine. By design, any implementation has to "take over the machine" in some sens
205.
by ghoward 4y ago
> Git repos are as atomic as you make them. Not with submodules, apparently. [1] > Package managers already use checksums. This entire point is just wrong and ignorant. Reproducible builds would be nice here, sure, but outside of a fe
206.
by ghoward 4y ago
Funnily enough, I'm working on the next Git. (I'm not the author of Pijul; it is another one.) So here's what I think of these points, as well as how my VCS will address them. 1. Atomicity across projects: this is a good poin
207.
by ghoward 4y ago
My post has three quotes where people claim Zig is completely colorblind, not just at compile-time. My point stands, especially because of the hoops that gist had to jump through to get it to work.
208.
by ghoward 4y ago
Yes, why does that matter? It still shows that Zig's async/await is not colorblind.
209.
by ghoward 4y ago
Zig's async/await isn't actually colorblind. [1] It just seems that way at first. [1]: https://gavinhoward.com/2022/04/i-believe-zig-has-function-c...
210.
by ghoward 4y ago
What is your narrow area of expertise? Passwords and memory-hard functions? I figure scrypt is, but I'm not using that. I'm implementing OPAQUE with Argon2.

More ›