zongor
Now
•
100%
I have it running on a x86_64 Pentium III server; works great!
zongor
Now
•
100%
The grid will connect the world!
zongor
Now
•
100%
I seems like the consensus from people here is to start with the stand-alone package manager. So I shall look into that thanks!
zongor
Now
•
100%
This does make a lot of sense. From what I could tell a lot of devs talk about nixos in the same way that they talk about docker.
zongor
Now
•
100%
Yeah Ive been using hy-lang about half the time I have to do things in python; so I would assume weirdness is bound to occur :). Yeah I believe someone else mentioned that it could be used as a standalone package manager so I shall look into this.
zongor
Now
•
100%
Yeah thats a good idea. I know that guix can be used as standalone package manager but I didn't know you could do that with nix as well. I shall look more into that, thanks
zongor
Now
•
100%
Yeah one of the reasons I was looking into Guix was because it has a lisp based configuration. (I use emacs semi regularly so I imagine guix would fit into the emacs config mindset well).
zongor
Now
•
100%
I am a hobbyist programming language developer so I program in a lot of different languages (c, rust, go, js, python, various lisps, forths, esoteric langs). I did read an interesting article about someone daily driving Debian Sid, so maybe I will look closer into that. I also have heard of a distro called rhino linux which is supposed to be a "rolling release ubuntu". Yeah I always forget that docker dev containers are an option, maybe I should look into that more.
TLDR: is the amount of time used to switch to these distros worth it? (compared to Debian, Fedora, etc.), or is there a better distro that fits my use case? I have been using Linux for about 4 years now as my daily driver, distro hopping a lot. I have used PopOS (for a few years), Manjaro, Garuda (for a year or so), KDE Neon, Debian, Linux Mint, Nobara (for some months until I ran into system breaking issues), and lastly EndeavourOS. Issues I have run into in the past are around the different packaging systems and versioning. The Debian/Fedora based ones seem to be fairly slow to update and so they have out of date packages, which sometimes is ok, but sometimes if they are too out of date I have to compile it from scratch. Also the different packaging systems (like apt, pacman, dnf...) means that depending on what flavor I am currently running there may not be a analogous system or maybe a package will be missing and I end up (once again) having to build it from scratch. On the other side I have Arch Linux based ones, which usually works great (especially having access to the AUR) but I end up spending a lot of time configuring stuff that isn't built in (which is by design I know), or having stuff randomly be broken after an update. (which I suppose is my own fault I should have probably set up btrfs or something). Also some libraries will build/work great out of the box on some distros and be completely unusable on others for no apparent reason. I looked into Gentoo, NixOS, and Guix SD as possible solutions for my issues. Gentoo because since it seems like I have to compile a lot of my libraries anyways maybe I should use a system where you have to compile everything. NixOS and Guix since it seems they are designed for package management and versioning built into the system which might be exactly what I am looking for. I am worried about the learning curve of all of these. I don't have a lot of time to mess around with configuring stuff all the time. Ideally I'm looking for a distro that works well with my old-ish hardware (with NVIDIA support unfortunately) where I can sit down, program and/or play games on steam+proton; but it seems like I have to choose between "system is stable but packages are old" and "system and libraries are new but is very unstable. Or if I am using snaps or flatpak its "install 5 things and now you are out of memory" (thanks electron). Also concerned about both NixOS and Guix since they seem to be designed behind "everything goes through the package manager", which is super cool for making it so the environment is the same, but I am concerned about getting stuff to work if a package doesn't exist or if the library is designed to use like 'pip' or 'bun.sh' or some built in package manager. Any thoughts about this? any non popular distros that might fit my use case? did I give up on some distro too soon? am I just a confused newb?
zongor
Now
•
100%
The header file was not originally made for the purpose it is used for today. In previous languages (like Fortran or COBOL) they had a preprocessor which was used for defining constants and macros and the like. The preprocessor is like a glorified cut and paste machine, it can’t do any complex processing by itself. (In fact the C preprocessor is not even Turing complete although it is close)
The reason why the headers are included at the top is also for historical reasons. In single pass compilers a file is read line by line and parsed into an Abstract Syntax Tree; the function has to be declared before it can be used but sometimes it may be declared in a different file or later in the file. So it’s convenient to put that information in the header.
Many modern languages use compilers that take multiple passes to generate the code. They will also use internal databases for the objects and their prototypes like a v-table to store data about the program to do optimizations and the like.
Languages like rust, zig, and go use modules where they have namespaces where specific definitions of code are declared and able to be used later. They also had a series of built in tools like dynamically managing dependencies, linking, etc.
For most languages they also have a Foreign Function Interface which allows them to call functions written in a different languages (like C shared libraries). All of the managers you mentioned have great FFI functionality and work well with C shared libraries. You can often use C header files in these since they give the function prototype without needing to read the whole source code and find all those definitions (often if the library is proprietary you will only have access to the shared library and the header files).
zongor
Now
•
100%
If you don’t mind using a different system GURPS has a free 32 page lite version of the system that gives you all the basics
zongor
Now
•
100%
Many years ago now I was told that we needed a way to turn a series of lights on and off for a custom bit of hardware. The hardware ran a Unix-like system so I decided that a daemon would be a good fit for the use case. I do not know what has become of my daemon of light but I do know whomever uses it must call the “summon” function to daemonize the process
zongor
Now
•
100%
They have an especially great selection for cheese. The only place I can find reasonably priced Brie and Camembert
zongor
Now
•
100%
Moth mode should be a required feature in every web browser
zongor
Now
•
100%
Keep putting points into “inland empire” until you start understanding
zongor
Now
•
100%
Now feed it nonstop terrywads
zongor
Now
•
100%
This should have been an option in Kerbal Space Program, the kerbals totally would have done this
zongor
Now
•
100%
It happens in Star Trek online kind of
Playing around with plan9’s webfs, have a prototype for reading/writing to the lemmy api as if it were a series of files. The program creates the files dynamically and it can then be mounted to wherever, in the case of the example here I just mounted it to the /n directory. Currently I only have one api endpoint but this is good enough for a proof of concept.
Now