4ffy

joined 2 years ago
[–] [email protected] 28 points 3 months ago* (last edited 3 months ago)

The reason that Doom is so portable goes beyond Linux and is an artefact of its development. id developed Doom on NeXTSTEP (i.e. Unix) machines and obviously targeted DOS. This is pretty unique among DOS games at the time and required id to write as much code as possible in a platform agnostic way. This means that the main engine does not care about where it is running and the usual DOS hacks are contained to DOS-specific files. In order to port Doom to a new platform, ideally one only needs to rewrite the system-specific implementation files for video, sound, filesystem access, etc., and this mostly holds true today. (These files are prefixed with i_ in the Doom source).

The Linux port is just one of many versions developed at the time. I don't believe that it was commercially released; it was more of a portability test. The reason that the Linux version was chosen for the source release over the DOS version was because it didn't rely on the proprietary DMX sound library that the DOS port used.

[–] [email protected] 5 points 11 months ago

Emacs's regular clipboard is the "kill ring" which also allows you to retrieve any previously cut/copied text. It also has "registers" where you can store and retrieve snippets of text, which can be considered clipboards when used for this purpose. Registers can be referenced by any character you can type on your keyboard, including control characters like ^D.

This totals... a lot of clipboards.

[–] [email protected] 16 points 11 months ago (7 children)

My heart sank upon reading the word "electron" and rose again on the very next paragraph. I'm looking forward to seeing it in action.

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

I think that this is above all else the reason that I use Arch. Arch Linux makes creating packages trivial, basically just wrapping build instructions into a shell script template. Arch handles the rest. The build systems for deb or rpm packages don't come close, and good luck rolling your own flatpak.

This allows me to use pacman for everything outside of my home directory. Pacman is practically the central feature of my computer, and it's wonderful. I'm sure those Nix people can relate, though I guess my method is a bit less robust.

[–] [email protected] 175 points 1 year ago* (last edited 1 year ago) (29 children)

This might be the first time I've ever seen something productive happen in the Phoronix forums. I love that place. Go to any topic with more than about a dozen posts and it's almost guaranteed to be a flame war. Genuinely one of the funniest places on the Internet.

Check out this one. It took like three posts!

1
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

It has been almost two years since the last ReactOS newsletter. Despite no new releases, the project is still active. Much work has been done on different parts of the operating system, from improvements on the 64-bit port to protections against registry corruption.

[–] [email protected] 1 points 1 year ago (2 children)

This is the main reason that one should learn to read PKGBUILDs. Any AUR helper like Yay or Paru should give the option. Just make sure that the package downloads from an official source and contains only the necessary build and install instructions.

But I agree. Some people treat the AUR as just another repository, when it most definitely is not.