benhoyt

11 ms·

91.
Show HN: I use the WordStar Diamond in 2023(benhoyt.com)
5 points by benhoyt 3y ago|0 comments
92.
Using the WordStar Diamond in 2023(benhoyt.com)
5 points by benhoyt 3y ago|0 comments
93.
by benhoyt 3y ago
In case it helps anyone, here's a recent blog article written by Daniele Procida (a director of engineering at Canonical, responsible for documentation) that helps explain the motivation for our written interview: https://ub
94.
by benhoyt 3y ago
There's a big area between "obsessed with" and "don't really care about"! I clearly care about it and think it's interesting and important, hence writing the article, but I have better things to be obsess
95.
by benhoyt 3y ago
Are people "obsessed" with this? As the OP, I'm not. I agree with you that static vs dynamic typing and the other issues you mentioned are more important than this, but that doesn't make smaller details not worth discu
96.
Name before type: why ‘age int’ is better than ‘int age’(benhoyt.com)
3 points by benhoyt 3y ago|10 comments
97.
Proposal to enhance Go's HTTP router with method and wildcard matching(benhoyt.com)
2 points by benhoyt 3y ago|0 comments
98.
The proposal to enhance Go’s HTTP router(benhoyt.com)
6 points by benhoyt 3y ago|0 comments
99.
by benhoyt 3y ago
I think that's a fair critique. You have to really put thought into good error messages and error handling. When you do, they're nicer and more informative than an ugly stack trace. But a poor error message chain like the one you&
100.
by benhoyt 3y ago
> Putting error nil checks into a function is an anti-pattern in Go. I assume you mean into a helper function like I've done with check()? If so, I agree with you for normal "production" Go code. But for simple throw-away
101.
by benhoyt 3y ago
I'm guessing you're being sarcastic. If so, it's not really a fair criticism. Go has properly-typed return values (not just parsing text from stdout) and any type can implement the error interface, allowing for error types wi
102.
Show HN: Gogit – Just enough Git (in Go) to push itself to GitHub(benhoyt.com)
176 points by benhoyt 3y ago|73 comments
103.
Scripting with Go: tiny Git client that can create a repo, push itself to GitHub(benhoyt.com)
4 points by benhoyt 3y ago|0 comments
104.
by benhoyt 3y ago
This looks interesting. I created and maintain a library for INI parsing that got surprisingly popular -- it's tiny, so is good for embedded systems. This API has a very similar feel to mine, including the callback for every key/v
105.
Ten Years of “Go: The Good, the Bad, and the Meh”(blog.carlmjohnson.net)
8 points by benhoyt 3y ago|0 comments
106.
by benhoyt 3y ago
I'm pretty sure I wrote the first version of kernel.com in assembler. Update: actually, more likely it was built using the meta compiler running on top of one of my previous Forths (I wrote a few). It's been too long to remember e
107.
by benhoyt 3y ago
My first programming languages were x86 assembly and Forth. My Dad was into Forth, and I learned programming from him. I wrote several x86 Forth systems for DOS as a teenager, culminating in a somewhat-polished ANS compatible one I called &
108.
Making Lua-yottadb 4x as fast looping through database records(yottadb.com)
3 points by benhoyt 3y ago|0 comments
109.
by benhoyt 3y ago
This is a fascinating concept that I've written about before: "C#’s async/await compared to protothreads in C++". [1] Both async/await in C# and protothreads [2] in C unroll control flow to a state machine. In C, th
110.
by benhoyt 3y ago
https://benhoyt.com/writings/ The programming-related articles I've written, focussing primarily on Go and Python, as well as articles about my projects like GoAWK.
111.
by benhoyt 3y ago
I agree with your point. However, I think overuse of the word "toxic" is toxic. :-) It seems to be applied to everything from a jerk who sexually harasses women to overzealous blog posts about version control, so the word becomes
112.
by benhoyt 3y ago
> Unlike many other professions grounded in the limitations of physical reality: carpentry, civil engineering, hair cutting, etc, Software Engineering is a house of cards of artificial abstractions. The tools and architectural patterns a
113.
by benhoyt 3y ago
Not surprisingly (as the OP), I disagree. Good names help people understand concepts; bad names confuse. Choosing good names is not merely aesthetics, it's bringing clarity, meaning, and culture. That said, in this particular case, I
114.
Names should be as short as possible while still being clear(benhoyt.com)
85 points by benhoyt 3y ago|126 comments
115.
by benhoyt 3y ago
Yes, my thought is to read Bob Nystrom's "Crafting Interpreters". It's excellent, in-depth but not academic, and the writing style is great. https://craftinginterpreters.com/ " He also has a lot of g
116.
by benhoyt 3y ago
> modern Python supports the `datatype` decorator I presume you mean the @dataclass decorator?
117.
by benhoyt 3y ago
I just finished transcribing this from the scanned PDF, and thought it might be interesting to others. It certainly took me back! I was really into Forth as a teenager (thanks to my dad's interest), and wrote several of my own Forth co
118.
Lookup Tables: article I co-authored for “Forth Dimensions” as a teen(benhoyt.com)
21 points by benhoyt 3y ago|1 comments
119.
For Python packages, file structure != API(benhoyt.com)
32 points by benhoyt 3y ago|4 comments
120.
by benhoyt 3y ago
But length() is standard POSIX, no? Even length(array) has been approved by POSIX [1] but not yet included in the spec (they're very slow to update the spec for some reason). Both forms have been supported in onetrueawk, Gawk, mawk, an

More ›