Viewing profile — HippoBaro

> Says frustrating things like "so I can just use unsafe", because no you don't and if you do I would reject your changes immediately. This is the kind of hostility (which is frank…

> Rust invented the concept of ownership as a solution memory management issues without resorting to something slower like Garbage Collection or Reference Counting. This is plain w…

> It actually took a lot longer to re-write the game in C++ than it took me to write the original machine code version 20 years earlier. Is the most interesting quote IMO. I often …

I’m very excited for Zig personally, but calling it “ultra reliable” feels very premature. The language isn’t even stable, which is pretty much the opposite of something you can re…

It was nighttime in Singapore when the ruling was announced. My husband and I scrambled to find a flight back. The best we could find, at any price, lands 25mins after the deadline…

It’s really the hardware block size that matters in this case (direct I/O). That value is a property of the hardware and can’t be changed. In some situations, the “logical” block s…

Just to add my two cents—I’ve been writing Go professionally for about 10 years, and neither I nor any of my colleagues have had real issues with how Go handles errors. Newcomers o…

I’m amazed by the ambition, technical brilliance, and relentless dedication behind some personal projects on display here. All of this for a clock! I don’t get it, but I’m in awe.

Eminently pragmatic solution — I like it. In Rust, a crate is a compilation unit, and the compiler has limited parallelism opportunities, especially since rustc offloads much of th…

It would be great to know a bit more about the protocol itself in the readme. I’m left wondering if it’s reliable connection-oriented, stream or message based, etc.

I am not sure I buy the underlying idea behind this piece, that somehow a lot of money/time has been invested into asynchronous IO at the expense of thread performance (creation ti…

> Under the asynchronous model, both timeouts and cancellation simply compose. You take a future representing the work you're doing, and spawn a new future that completes after sle…

I think the author knows very well what UB is and means. But he’s thinking critically about the whole system. UB is meant to add value. It’s possible to write a language without it…

Go has an amazing runtime and tool ecosystem, but I’ve always missed a little bit more type safety (especially rust enums). Neat!

For the kind of software I write there are two cases: (1) the hot path for which I will always have custom allocators and avoid allocations and (2) everything else. For (1) GC or n…

A few years ago my company moved to using Bazel as our build system. JetBrain IDEs have a plug-in for Bazel that’s incredibly slow and buggy. It’s a shame because I used to really …

As a database engineer who worked extensively with both i3 and i4 instances, I want to add that although i4 has lower IOPS, the latencies distribution of IO ops is an order of magn…

Abstracting code is always a dangerous gamble because they rely on invariants. In this case “the shape all resize the same way”. When the invariants breaks, the abstraction collaps…

There's absolutely nothing in Rust that mandate error handling. You can always ignore them, just like in any other language.

This! These fancy operators add a lot of complexity in practice. Trivial things in Go like error wrapping (to add local context), become much more complicated with `?` operators. G…

I think there are a few misunderstandings there (the video is funny, btw). The kind of async IO I'm referring to exists one layer below whatever Apache and node are using. Both are…

I can't entirely agree with this, but I like how the authors think about the issue (S3 being a de-facto standard without anything formal to back it up). POSIX is outdated and probl…

I think the information there is valuable because questions about memory usage in Linux keep coming up. The answer: "don't worry about it," is probably a good starting point. The p…

> I've used stackful coroutines many times in many codebases. It never required or used a runtime or preemption. Can you tell us which? Go, Haskell and the other usual suspect all …

As someone else said, it is not, strictly speaking, a bug. If your server receives a request that requires very computationally expensive work, is it okay to delay every other requ…