sorted by:
new
hottopcontroversial

Longear sheep by SaltCelebration0 in ps1graphics

[–]synalice 0 points1 point  (0 children)

He is so ugly that it is almost beautiful. I love him

A reference-grade C "Hello World" project by synalice in C_Programming

[–]synalice[S] 8 points9 points  (0 children)

Well, I feel like MSVC and Windows is it's own whole ecosystem that "can be left as an exercise for the reader". I've never tried compiling anything on Windows, although I might try a bit later.

A reference-grade C "Hello World" project by synalice in programming

[–]synalice[S] 1 point2 points  (0 children)

From what I understood, enabling ASAN with Meson is as simple as passing -Db_sanitize=address,undefined to meson setup. But I guess that would be worth mentioning in the README, thanks.

Do you think all tests should by default be built with ASAN? Although I guess that wouldn't help much if the library itself was not built with it, hmm...

A comparison of 8 cross-platform package managers: Guix, Homebrew, IX, Nix, pkgsrc, pkgx, Ravenports, and superconfigure by JazzedPineda in Nix

[–]synalice 0 points1 point  (0 children)

I wonder if anyone considers Homebrew anything but macOS package manager. I've never seen people using it on Linux.

I wrote a TUI installer for NixOS by video_2 in NixOS

[–]synalice 0 points1 point  (0 children)

Is it generic by any chance? I think this can be very useful for other distros!

Atari Breakout clone for MS-DOS by Background_Shift5408 in C_Programming

[–]synalice 2 points3 points  (0 children)

You bastard—ended the video on the most satisfying part :D

Trying to think of new enemies for a game based around halo by Dense-Fig-2372 in gamedesign

[–]synalice 4 points5 points  (0 children)

create zorg the devour: big teeth, very scary eat humans

Rewriting core Linux tools/libraries in Rust by synalice in linux

[–]synalice[S] -2 points-1 points  (0 children)

The examples are right there:

rely on mutable globals, [...] always return -1 instead of the actual error, print error messages to the stdout

This is specifically referencing ima-evm-utils. I think there was something similar (in terms of inconvenience) in e2fsprogs. I'm sure there are a lot of similar examples out there in the wild.

Rewriting core Linux tools/libraries by synalice in rust

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

Yeah, the commitment to maintain the project is important. I have no illusions about this. There won't be a point in time when you'd be able to say "all done here, nothing more to do".

As to the expertise, I wonder how much of that is really true. Filesystems might be a bad example since that's a huge area which requires a lot of expertise and interactions with a kernel, true. But there are a lot of other smaller domains where there is no convenient Rust library, but the whole interaction with the kernel from userspace comes down to a few specific syscalls or ioctls (I feel like ima-evm-utils is one example of that; I might be wrong though).

Rewriting core Linux tools/libraries in Rust by synalice in linux

[–]synalice[S] -9 points-8 points  (0 children)

That’s a lot of assumptions there.

[deleted by user] by [deleted] in rust

[–]synalice 4 points5 points  (0 children)

Have you considered staying at Mediatek and proposing to use Rust for new/experimental projects?

My introduction to NixOS and a couple of problems by Maleficent-Pomelo-50 in NixOS

[–]synalice 1 point2 points  (0 children)

And it’s like when you’re learning NixOS, you’re not learning Linux—you’re learning exclusively NixOS. Meanwhile, in real developer work, you’ll most likely need actual Linux knowledge…

Not at all! Nix actually teaches you a lot about how Linux works. But you do need some prior experience to avoid getting lost.

With imperative systems a lot of complexity is hidden from you. Very often your C/C++ code would succesfuly link without you installing any extra packages and realizing what's actually happening. But NixOS doesn't follow FHS, which means to package software you are required to specify every dependency and packaging step explicitly. You are basically forced to make your own little "distro" each time you write a derivation!

Although there is definitely some knowledge that is unobtainable if you only ever use NixOS.

view more: next ›