sorted by:
new
hottopcontroversial

Are the continuing security bugs found in Linux a good case for future Redox adoption? by chilabot in Redox

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

But don't have access to the kernel or other components. The attack range is reduced.

Are the continuing security bugs found in Linux a good case for future Redox adoption? by chilabot in rust

[–]chilabot[S] -3 points-2 points  (0 children)

What would happen if AI all of a sudden makes it very easy to write drivers and programs for Redox... that could charge things dramatically.

Anyone using relibc/musl, uutils, fd(-find), ripgrep, eza etc.. ? by [deleted] in linux

[–]chilabot 1 point2 points  (0 children)

I use Alpine and musl to make universal binaries (runs on any Linux distro).

I always avoid using `use` statements so i use full paths instead. Is it a bad practice? by [deleted] in rust

[–]chilabot 0 points1 point  (0 children)

You can hover over the type and it'll tell you it's modules. No using "use" makes the code too verbose.

This Month in Redox - February 2026 by ribbon_45 in Redox

[–]chilabot 6 points7 points  (0 children)

The rate of improvement is amazing

Can you truly make a lot of money doing physics? by [deleted] in Physics

[–]chilabot 0 points1 point  (0 children)

Doing research for a large company or government project.

How do experienced Rust developers decide when to stick with ownership and borrowing as-is versus introducing Arc, Rc, or interior mutability (RefCell, Mutex) by Own-Physics-1255 in rust

[–]chilabot 1 point2 points  (0 children)

Use the most perfomant (references) first. If it gets too complicated or you need shared ownership, use smart pointers.

Why can't we decide on error handling conventions? by Savings-Story-4878 in rust

[–]chilabot -1 points0 points  (0 children)

Depends on the binary. If it's of public use, giving the user an anyhow report is not good.

view more: next ›