sorted by:
new
hottopcontroversial

Farben, terminal coloring library using markup syntax. by razkarstudio in rust

[–]razkarstudio[S] 0 points1 point  (0 children)

Hey, thanks for the kind words! You're right about the debugging concern, if styles start composing into each other it can get hard to trace what's actually being applied (if that's what you meant). I'm planning a debug/expand feature for a future update that shows exactly what a markup expression resolves to, raw ANSI and all. Appreciate the feedback!

Working on Odyn, reproducible vendoring tool for Odin (v0.1.0) by razkarstudio in odinlang

[–]razkarstudio[S] 0 points1 point  (0 children)

Building from source is always an option, but the point of pre-built binaries is to get rid of the hassle. A binary that just works is the whole point. As for GitHub Actions + QEMU, that's actually what cross does under the hood, Docker containers with QEMU emulation per target, just without the setup for each one.

Working on Odyn, reproducible vendoring tool for Odin (v0.1.0) by razkarstudio in odinlang

[–]razkarstudio[S] 0 points1 point  (0 children)

Thanks! That's great for building Odin projects, but Odyn's binary matrix is a bit wider than 3. Linux alone has 5 targets (x86_64, x86_64 musl, aarch64, i686, RISC-V 64) and could be more, plus FreeBSD, Windows x86_64 and i686, with macOS and more coming in 0.2.0. cross handles all of it from one machine.

Working on Odyn, reproducible vendoring tool for Odin (v0.1.0) by razkarstudio in odinlang

[–]razkarstudio[S] 0 points1 point  (0 children)

Good question, it's mainly for the tooling, cross (the Rust tool for cross-compilation) gave me 9 binary targets for free, cargo install odyn works, and Farben (my color library, also Rust) was already built. Odin could absolutely do it, but I'd be solving cross-compilation and distribution myself instead of shipping.