hryx's comments

hryx | 2 years ago | on: So Long, Twitter and Reddit

As Andrew mentions in the post, even having a Twitter account was a source of stress. It's about more than just promoting his content.

It's a feeling I can sympathize with. In 2009 I deleted my Facebook account (or "deactivated" it, the only option at the time), and even though I wasn't using it much by then, it felt like a needless weight was suddenly lifted.

hryx | 2 years ago | on: File for divorce from LLVM

It might be rash if work had already started on it, but as with the other proposals on the issue tracker not labeled with "accepted", this is just a call for discussion and counter-proposals. At this point it's just the team collecting feedback, learning about affected use cases, and gauging feasibility -- opposite of rash, I'd say.

hryx | 3 years ago | on: Zig's multi-sequence for loops

In general Zig foregoes syntactic sugar and requires implementing higher-level APIs by composing primitives. But a new language feature is a candidate when it solves a use case that can't otherwise be solved, or opens up a path to more efficient code.

Loris' blog post points out that the new for loops address the latter:

> In the multi-sequence for loop version it’s only necessary to test once at the beginning of the loop that the two arrays have equal size, instead of having 2 assertions run every loop iteration. The multi-sequence for loop syntax helps convey intention more clearly to the compiler, which in turn lets it generate more efficient code.

It also builds on existing properties of slices/arrays, rather than adding a new "enumerate primitive".

hryx | 3 years ago | on: Bun v0.5.7

I don't speak for Jarred or Andrew, but here is a recent exchange between them about this matter: https://github.com/ziglang/zig/issues/14542#issuecomment-141...

The tension is understandable: Zig is explicitly not production-ready, yet it has such attractive performance and productivity properties, and has even proven useful in production scenarios (Bun, Uber, Tigerbeetle). But Andrew's suggestion is correctly aligned with Zig's mission and current level of maturity. If you have a complex project with lots of users like Jarred does, stick with a tagged release for now.

The highest priority of Zig pre-1.0 is to make the language the best it can be — which it will be in due time. The target audience of the master branch is those who can withstand churn and are focused on getting it there.

hryx | 3 years ago | on: Overview of the 555-XXXX phone number

Same. My favorite geezer hacker/heist movie, Sneakers, drops a realistic San Francisco phone number (415 area code) near the end. I always wondered who would pick up if dialed...

hryx | 6 years ago | on: Zig cc: A drop-in replacement for GCC/Clang

Compiling to C source isn't planned for the reference Zig compiler, as far as I know. It's more interested in helping people moving people off of C (see `zig translate-c`).

But for supporting more esoteric targets you might be interested in the goals of this ultra-early-stage assembler. ("Planned targets: All of them.")

https://github.com/andrewrk/zasm

page 1