Skip Navigation

Posts
1
Comments
139
Joined
2 yr. ago

I'm the Never Ending Pie Throwing Robot, aka NEPTR.

Linux enthusiast, programmer, and privacy advocate. I'm nearly done with an IT Security degree.

TL;DR I am a nerd.

  • Storms

  • Yummy electrolyte drinks

  • It is definitely a Firefox fork, the images of the UI are near identical to Firefox, and the one with addons shows the option to search addons.mozilla.org

  • Ubuntu is a corporate/popular distro. It wouldn't make much sense to move to do as when it lacks much of the functionality of sudo and isnt in a memory safe language, which is Ubuntu's goal with replacing user space software with Rust.

  • But stale bread for French toast??

  • Sad but understandable. I saw the donation button but I don't have spare money atm.

  • No

    /jk obvi I like Python

  • Zig is designed as a successor to C, no? So i assume it does syntax and things quite similarly. Rust is not a C-like language, so i dont think this a fair comparison at all.

    But in the end, learning syntax isnt the hard part of a new language (even if it is annoying sometimes).

  • All the different tests ive seen comparing Rust and C put compile times in the same ballpark. Even if somehow every test is unrepresentative of real-world compile times, I doubt it is "order[s] of magnitude" worse.

    I remember watching someone test the performance of host a HTTP webpage and comparing the performance of Zig, Rust w/ C HTTP library, and Rust native. Rust native easily beat them out and was able to handle like 10s of thousands more client connections. While I know this isnt directly relevant to Kernels, the most popular C HTTP library is most likely quite optimized.

    Memory related vulnerabilities are consistently in the top reported vulnerabilities. It is a big deal, and no, you can't just program around it. Everyone makes mistakes, has a bad day, or something on their mind. Moments of human fallibility. Eliminating an entire class of the vulnerabilites while staying competitive with C is a hard task, but entirely worth doing.

  • Never ask it to do regex. Holy fuck, thank God I was just doing it for funsies as a test of local LLMs. I got it to go into an infinite loop trying to figure out what I asked.

  • Yeah, I've seen them called guard or guardian models.

  • And I dont deny that. There are a lot of programmers, and not all had eduction on designing secure software. Even with the knowledge and experience, what if the programmer is tired or makes a similar mistake. Only one mess-up away from a potential vulnerability or instability of the app and system as a whole. I need more experience with C to form a better opinion.

  • I do not agree with the Dev who stepped down.

    But on the topic of C, I wouldn't measure the quality of a language based on its adoption. C is a relatively old language and therefore benefits from getting wide-use before other languages were born. It will never die because who would ever want to rewrite every project in existence in another language.

    Memory safety is very important since it has consistently been one of the largest sources of vulnerabilities throughout software history.

    C is not a bad language, but it has flaws. Performance at the cost of safety is not a good trade-off in most scenarios. There is no such thing as a "perfect programmer" who won't make mistakes.

  • Vim

    Jump
  • People on Snapchat dont give a fuck about cleanliness.

  • Legit. Even if documentation can be time-consuming, it is such a lifesaver and makes the whole process of coding much smoother. It means not as much time wasted backtracking. If you think there is any part of your code you won't understand when you coming back to it, document, document, document.

    Sometimes I write some multiline psuedocode comments or/and an explaination of specific choices, especially those invisible choices you make while debugging that aren't apparent when your just reading through your code.

    Good thing to do is make code that is generally readable too lol.

  • Gender is obviously a signed byte.

  • Docker is good when combined with gVisor runtime for better isolation.

    gVisor is an application kernel, written in memory safe Golang, that emulates most system calls and massively reduces the attack surface of the kernel. This is important since the host and guest share the same kernel, and Docker runs rootful. Root inside a Docker container is the same as root on the host, as long as a sandbox escape is used. This could arise if a container image requires unsafe permissions like Docker socket access. gVisor protects against privilege escalation by only using root at the start and never handing root over to the guest.

    Sydbox OCI runtime is also cool and faster than gVisor (both are quick)

  • Where? Have a link?

  • Until a port to Wayland is made, I would avoid using this DE. X.Org is unmaintained legacy software. Maybe Sway would work as a replacement?