4wd

When I started learning programming, I was like “tf is a map function?” and I always forgot about it. Then I tried the functional programming language Erlang and understood all these functions very well. But there is a downside, now most for-loops in C++ look terrible to me :)

What about using enums? In this case you will have to specify them for all records, but this ensures that the field will always be present.

enum license_owner {
    regular_citizen = 0,
    embassy,
    government,
    ...
}

It would be better for your nerves to just do a normal GNU/Linux installation. There are too many ways the installation can go wrong:

replace swap partition with ISO contents

For example, Ubuntu ISO has a size of 5.7G. But my swap, which you previously deactivated, was 4G. Either 2G, or it didn’t exist at all.

move user data from C:/ to other partition

The other partition may not exist or may have capacity smaller than C:/.

replace C:/ with linux

The installed Linux must also be stored somewhere. And there is also a copy partition for C. The same problem of lack of space.

move user data to /home/$username

From %APPDATA%? You would have to be a know-it-all to resolve the location paths and configuration names of literally every existing program.

reboot into linux

And it is at this moment that Windows will completely randomly decide to update and rewrite the bootloader :)

In Elixir, we mark statuses by using a question mark at the end of the variable name. Something like this:

authorized? = user |> get_something() |> ensure_authorized?()

I like this better than the is_ prefix

console.log() is really easy to learn, but what happens after that is a complete “wtf”

Why don’t you just remove all plugins and use standard zsh? All sorts of oh-my-soy are not really needed.

The language idea is good, but: THREE.WebGLRenderer: A WebGL context could not be created. Reason: WebGL is currently disabled.

Seriously? Why do I need WebGL to read TEXT in docs? :/

I used DuckDuckGo a couple of years ago, but they added their own blacklist of sites (pretty stupid), and for my language it started returning crappy generated spam sites instead of relevant results. They shouted at the top of their lungs that for my language they simply index the results from Yandex, but this is a lie, they are different.

StartPage gave the best results, but they introduced a captcha that I got every damn request.

I’m currently using SearXNG, which collects results from Google. And these are damn normal results, unlike other search engines that consider themselves the smartest and edit the results.

EndeavorOS offers a choice of systemd-boot and GRUB. So, if you don’t have GRUB, you probably have systemd-boot.

Don’t forget https://zed.dev/docs/telemetry

This way we will have multiple sudo-tools on one system without the ability to remove all but one. Like now with all this crap like systemd-resolved, systemd-networkd, systemd-anothershitd and a bunch of tools that do the same thing, but are all required.

The main problem with sudo and doas is that they are not developed by Lennart. Seriously.

Try not to work in pitch darkness :)

Used dark (not black) themes everywhere for 8 years. My eyesight is still good according to my annual physical, but recently I’ve noticed that I have a hard time reading text written on a dark background. It is slightly blurred, especially when there is no light in the room.

Somewhere I still use dark themes, but I always try to switch to light mode if things look okay with code highlighting or smth.

If you build your app with glibc 2.32 and then run it with glibc 2.39, it will run fine. But it won’t work the other way around.

There is no best README template, but for my personal projects I use this:

1. Title

• Brief description of the project
• Features

2. Build

• List of supported OS
• List of dependencies (what packages do I need to build your application)
• Commands to build the application (what do I need to do to build your application)
• Binary Locations (where can I find the built binary)

3. Usage

• Program arguments (what do I need to provide to use your CLI application)

You can find an example here. I’m not saying this is the best README, but I think it’s simple and informative.

Just build the app on very old distros like Ubuntu 16.04 if possible. But in general, packaging should be handled by the maintainer. If you want to be both a developer and maintainer, packaging problems will take up 75% of your time.

It’s not really hard for us users to follow your README and just copy the built binary to ~/.local/bin.