Readit News logoReadit News
HippoBaro commented on Rust is just a tool   lewiscampbell.tech/blog/2... · Posted by u/JuniperMesos
anon-3988 · 13 days ago
Rust is just a tool. A decent tool that I think can be made better (by removing stuff and stop adding more stuff to the surface syntax). So I am down to criticize Rust.

However, I also don't understand how people don't see the usefulness of what Rust put to the mainstream: algebraic data types, sum types, traits, etc.

I also get super annoyed when people think Rust is only chosen for "safety". 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.

Honestly, in general, I am just annoyed when people don't use the right tool for the right job. And attempts to fix the tool with more bespoke stuff on top it.

HippoBaro · 13 days ago
> 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 frankly toxic) that’s become associated with parts of the Rust community, and has fairly or not, driven away many talented people over time.

HippoBaro commented on Swift is a more convenient Rust (2023)   nmn.sh/blog/2023-10-02-sw... · Posted by u/behnamoh
HippoBaro · a month ago
> 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 wrong, and it undermines the credibility of the author and the rest of the piece. Rust did not invent ownership in the abstract; it relies on plain RAII, a model that predates Rust by decades and was popularized by C++. What Rust adds is a compile-time borrow checker that enforces ownership and lifetime rules statically, not a fundamentally new memory-management paradigm.

HippoBaro commented on Interview with RollerCoaster Tycoon's Creator, Chris Sawyer (2024)   medium.com/atari-club/int... · Posted by u/areoform
HippoBaro · 3 months ago
> 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 feel like productivity has gone down significantly in recent years, despite tooling and computers being more numerous/sophisticated/fast.

HippoBaro commented on Systems Programming with Zig   manning.com/books/systems... · Posted by u/signa11
HippoBaro · 5 months ago
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 rely on.

We’ll know in many years if it was something worth relying on.

HippoBaro commented on Microsoft has urged its employees on H-1B and H-4 visas to return immediately   timesofindia.indiatimes.c... · Posted by u/irthomasthomas
HippoBaro · 6 months ago
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.

We are on our way there.

HippoBaro commented on Hitting Peak File IO Performance with Zig   steelcake.com/blog/nvme-z... · Posted by u/ozgrakkurt
database64128 · 6 months ago
I see you use a hard-coded constant ALIGN = 512. Many NVMe drives actually allow you to raise the logical block size to 4096 by re-formatting (nvme-format(1)) the drive.
HippoBaro · 6 months ago
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 size can differ. For example, buffered writes use the page cache, which operates in PAGE_SIZE blocks (usually 4K). Or your RAID stripe size might be misconfigured, stuff like that. Otherwise they should be equal for best outcomes.

In general, we want it to be as small as possible!

HippoBaro commented on (On | No) Syntactic Support for Error Handling   go.dev/blog/error-syntax... · Posted by u/henrikhorluck
HippoBaro · 9 months ago
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 often push back on this aspect of the language (among other things), but in my experience, that usually fades as they get more familiar with Go’s philosophy and design choices.

As for the Go team’s decision process, I think it’s a good thing that the lack of consensus over a long period and many attempts can prompt them to formally define a position.

HippoBaro commented on Precision Clock Mk IV   mitxela.com/projects/prec... · Posted by u/ahlCVA
HippoBaro · 9 months ago
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.

HippoBaro commented on Cutting down Rust compile times from 30 to 2 minutes with one thousand crates   feldera.com/blog/cutting-... · Posted by u/Qadriq
HippoBaro · a year ago
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 the work to LLVM, which is largely single-threaded.

It’s not surprising they didn’t see a linear speedup from splitting into so many crates. The compiler now produces a large number of intermediate object files that must be read back and linked into the final binary. On top of that, rustc caches a significant amount of semantic information — lifetimes, trait resolutions, type inference — much of which now has to be recomputed for each crate, including dependencies. That introduces a lot of redundant work.

I also would expect this to hurt runtime performance as it likely reduces inlining opportunities (unless LTO is really good now?)

HippoBaro commented on Nyxpsi – A Next-Gen Network Protocol for Extreme Packet Loss   github.com/nyxpsi/nyxpsi... · Posted by u/nyxpsi
HippoBaro · a year ago
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.

u/HippoBaro

KarmaCake day417October 3, 2016View Original