beautron

10 ms·

1.
by beautron 5mo ago
That's the idea! "Allow" the user to install any apps they choose. (I put "allow" in quotes, to emphasize how bizarre it is that a few platform vendors get to decide what all of humanity is "allowed" to do
2.
by beautron 5mo ago
This is sort of the defining mechanic of these games in my memory. The first thing that pops into my head when I think of Last Ninja is aligning and realigning myself, and squatting, awkwardly and repeatedly (just like a real ninja, lol), u
3.
by beautron 6mo ago
One problem with the /italics/ form is that it's not convenient when writing about filesystem paths (though I do like its visual indication of slanting).
4.
by beautron 6mo ago
Perhaps more proof of work is necessary, but it makes me sad. I still remember creating my HN account. It stands out in my memory, because it was the smoothest, simplest, easiest, and quickest account creation of my life. I had lurked here
5.
by beautron 7mo ago
I prefer the perspective that a computer program is akin to a mathematical constant. This was true in the old days. A program I wrote in C64 BASIC, way back in 1980s, should still work precisely the same today (even on one of the freshly-ma
6.
by beautron 8mo ago
> Not a lot of companies allow disabling their garbage, but FF does. > > Can't we be happy with this nice switch? I want my tools to keep working the way they have been working. I don't want to be paranoid that "garb
7.
by beautron 9mo ago
> The typical Go story is to use a bunch of auto generation, so a small change quickly blows up as all of the auto generate code is checked into git. Like easily a 20x blowup. Why do you think the typical Go story is to use a bunch of au
8.
by beautron 10mo ago
But sometimes it is useful to return both a value and a non-nil error. There might be partial results that you can still do things with despite hitting an error. Or the result value might be information that is useful with or without an err
9.
by beautron 11mo ago
I share your unpopular opinion. While I understand that having identical UI elements across apps aids in discoverability, I just love it so much when an app has its own bespoke interface that was clearly made with love. Like you, it might b
10.
by beautron 1y ago
My perception is that there's always been some dissonance between loving tech intrinsically for itself vs. the Silicon Valley venture capitalist business model. Conflating tech with its dominant business model enables the paradox where
11.
by beautron 1y ago
> Going from a project with 1,000 to 1,000,000 lines of code is a tiny leap compared to going from 0 to 1000. Are you sure the leap is tiny? It's a much easier problem to get only 1,000 lines of code to be correct, because the lines
12.
by beautron 1y ago
> When there are many and diverse data formats that meet that standard, it seems perverse to use the word "easy" to talk about empirically discovering the quirks in various undocumented dialects and writing custom logic to acco
13.
by beautron 1y ago
> If somebody give you a JSON file that isn't valid JSON, you tell them it isn't valid, and they say "oh, sorry" and give you a new one. That's the standard for "easy." But it isn't that reliably
14.
by beautron 1y ago
I also love CSV for its simplicity. A key part of that love is that it comes from the perspective of me as a programmer . Many of the criticisms of CSV I'm reading here boil down to something like: CSV has no authoritative standard, a
15.
by beautron 2y ago
I love that the Go project takes compatibility so seriously. And I think taking Hyrum's Law into account is necessary, if what you're serious about is compatibility itself. Being serious about compatibility allows the concept of a
16.
by beautron 2y ago
This matches my experience. I think I have a 25 hour circadian rhythm, which has me always wanting to stay up one hour later than the night before.
17.
by beautron 2y ago
I think the experience of building something atop a framework should absolutely have bearing on how to build the underlying framework.
18.
by beautron 2y ago
> And it doesn't really color the function because you can trivially make it sync again. Yes, but this goes both ways: You can trivially make the sync function async (assuming it's documented as safe for concurrent use). So I w
19.
by beautron 2y ago
Wow, this is wild! Maintaining perfect justification solely through word choice is... quite a writing constraint, lol. I don't think I've seen this done before.
20.
by beautron 2y ago
Didn't Unity and Epic have people working directly on the Vulkan specification? I remember reading a comment (maybe here!), way back during Vulkan's original release, where someone was screaming about how Vulkan was a conspiracy t
21.
by beautron 2y ago
> Common Lisp's string support certainly feels like it comes from a world where allocating memory is expensive, and something the programmer should be aware of, and have the option to reuse buffers instead of allocating additional m
22.
by beautron 2y ago
This rings true to me, perhaps because I struggle with this one. I used to think I was destined for success, because I'm good and creative at many things, and am curious and can teach myself things. But: I expected the system to inte
23.
by beautron 2y ago
> In general, when doing low level optimization of Go code, avoiding allocations is the biggest bang for your buck. I have found this to be the truth. I'm making a game in Go, and have learned that a smooth framerate depends on prog
24.
by beautron 2y ago
I'm sure Magit is lovely. But I can't resist sharing the story of my bad experience with it over a decade ago (which has left me scared away). It was maybe early 2012, and I was excited to try Magit. I got it set up, and called &#
25.
by beautron 2y ago
This is a great analysis that gave me a lot to think about. I've always loved the way Go's packages work. With care, I can organize large codebases that end up feeling so clean and nice to deal with. I usually get to pick all my o
26.
by beautron 2y ago
I feel this strongly. Physical books make a deeper impression in my memory. There are all sorts of particularities of how the book was bound: it's size, it's smell, the texture of the paper, etc. It's like the book exists in
27.
by beautron 3y ago
Yes, but even with that interpretation, they claimed something much stronger: > The encoded value can change any time you re-compile your program Any value (not just enums) can change any time you re-compile your program, if some progr
28.
by beautron 3y ago
I love Go's lightweight, somewhat implicit style of doing enums. You just declare an int type, and then a list of constants of that type. People are complaining about 'iota' here, but I think it's slick and great. It com
29.
by beautron 3y ago
But Twitter doesn't address many of the downsides of social media that were listed, or many of the upsides of RSS that were listed.
30.
by beautron 3y ago
I agree that weighted keys are preferable, but it's not about "building finger strength," but rather about building finger coordination . Your fingers are already plenty strong enough for weighted keys (especially once you l

More ›