kbolino

6 ms·

1.
by kbolino 5d ago
I've never downloaded a C# mod from a Discord server. They are typically available via first-party sources (e.g. CoI Hub for Captain of Industry ), reputable* third-party sources (e.g., Nexus Mods, Thunderstore for Valheim ), or even
2.
by kbolino 5d ago
The CLR is the reason most C# games are moddable.
3.
by kbolino 27d ago
> I miss strict, deterministic unsigned addition overflow. In many modern languages, all kinds of verbose hoops are required to get this behavior and there's a chance it will generate terrible machine code. Most modern (post-2000) l
4.
by kbolino 28d ago
Repeating the package name is fine if it's exactly the same name (modulo capitalization) and there's nothing better to name the type anyway. The style issue would arise with e.g. uuid.UUIDVersion, which should just be named uuid.V
5.
by kbolino 1mo ago
Sure, you can just ignore errors entirely, and this is what Rust actually does today, at least for std::fs::File. The only other option within RAII that I can think of is that you can mutate some external, longer-lived state. The primary
6.
by kbolino 1mo ago
RAII has the advantage that you can't forget to do it, but defer has the advantage that you can handle failure in ways other than panicking. Of course, in many cases (e.g. closing a file), there's generally not much you can do any
7.
by kbolino 1mo ago
You can exploit the mechanism described in the article yourself, but it's already changed once in the past and is not part of any compatibility guarantee. As with structs.HostLayout, a blessed structs.NoCopy in the standard library cou
8.
by kbolino 1mo ago
Interfaces in Go (the closest equivalent to traits in Rust) don't have to have methods either, but they are structurally typed. This is like "static duck typing" if you will. So an interface with no methods is implemented by
9.
by kbolino 1mo ago
This feels like a style complaint and not one about substance. An inaccessible (because it's named _) zero-length struct field is just another kind of metadata. It also doesn't require you to pollute the method set, which would be
10.
by kbolino 1mo ago
Whether your recommendation is valid seems to be quite CPU-dependent. Cf: cpu: AMD Ryzen 5 5600X 6-Core Processor BenchmarkAES_CBC-12 100000000 10.96 ns/op BenchmarkAES_CTR-12
11.
by kbolino 1mo ago
Go doesn't have auto-vectorization in the first place, so its portable simd library is at least partly there to fill the gap.
12.
by kbolino 1mo ago
I did a cursory look through a number of major languages and libraries*, and as far as I can tell, they all retain and provide access to the fragment by default. Maybe some of them didn't in the past, or the APIs that I found supersede
13.
by kbolino 1mo ago
Yes, this is just how fragments work; they're supposed to be stripped before sending the request to the server. This is exactly why, in the context of the thread , the fragment is the correct place to put the TSON hash parameter.
14.
by kbolino 1mo ago
Using the query string to carry the sha256 hash but then saying the "hash parameter is verification metadata, not identity" doesn't make much sense. The ?query part of a URL is supposed to be sent to the server. If you want
15.
by kbolino 2mo ago
Rust's solution (the ? operator) is actually applied to the Result type (and, IIRC, Option and ControlFlow). Go does not have a Result type. This makes a 1:1 port of Rust's solution impossible. Moreover, the "obvious" so
16.
by kbolino 2mo ago
You need this in Java because interfaces are explicitly implemented. You don't need this in Go because interfaces are structurally implemented. The way you spell "anything that has a method named Size which returns int" is in
17.
by kbolino 2mo ago
Technically, Java has the same rule, it's just that all user-defined types are reference types, and so the zero value for them is always spelled "null". I'm not sure how Scala pretends otherwise, but I have worked with K
18.
by kbolino 2mo ago
Ignoring the stack trace matter, which is explored in the sibling thread, it seems to me you're really taking issue with two of Go's language design choices that aren't specifically about errors: structural typing and the lac
19.
by kbolino 2mo ago
Yes, I don't think stack traces are a silver bullet. They tell you the path taken through the code, but rarely do they tell you why that path was taken. I don't know what Scala stack traces look like specifically, but I've
20.
by kbolino 2mo ago
> In the overwhelming majority of cases, you want to trivially send the error up the stack to be handled Maybe so, but for JVM languages, this "trivially" includes a stack trace. Go doesn't offer that for normal errors and
21.
by kbolino 2mo ago
SPF failures overriding DKIM successes is a direct violation of RFC 7489 section 4.2 [1]. I have never observed such behavior in the wild, though my experience may be more limited than yours. There are two possible explanations anyway, one
22.
by kbolino 2mo ago
Using both has to be done very carefully, because a positive result from the weaker one (SPF) will override a negative result from the stronger one (DKIM). You should maximally use DKIM and minimally use SPF. Ideally, you should not use SPF
23.
by kbolino 2mo ago
The audience may be larger, but I don't feel like it's anywhere near "everyone". Personally, I don't know anyone who still uses a dedicated email client except in specific institutional settings. I haven't touc
24.
by kbolino 2mo ago
SDL_RenderGeometry(Raw) are only capable of 2D rendering and the vertexes do not even have a z-coordinate. Genuine 3D support is available in SDL3 via the GPU types and functions: https://wiki.libsdl.org/SDL3/CategoryGP
25.
by kbolino 3mo ago
It's quite difficult to find fixed-point number systems that include trigonometry, never mind fancier tools like elliptic integrals. The problem is not just one of static number representations, but also geodetic/geometric computa
26.
by kbolino 3mo ago
> People are convinced you have to use doubles because of the inaccuracy of floats With single-precision floats, considering the worst case, i.e. longitudes close to the equator but far away from the prime meridian, one ulp can translate
27.
by kbolino 3mo ago
I had this problem on the first Apple Silicon Mac Mini in 2020 so it's at least a little older than 2023.
28.
by kbolino 3mo ago
It's also the corporate standard for generic cubicle workstation monitors, though it's unusual to find a Mac in such a place anyway.
29.
by kbolino 3mo ago
I wonder if they can solve the "ecosystem fracture" issue by borrowing the bubble concept from e.g. testing/synctest. The way the synctest API works is by creating a "bubble" around the test harness and the code und
30.
by kbolino 4mo ago
There's another big one, 4K page support. The MMU can be told to set up a virtual address space with smaller, x86-compatible 4096-byte memory pages instead of the default 16384-byte pages.

More ›