I’ve considered switching several times in the past, but each time there was something I needed that was not supported (e.g. - this issue with Zoom screen sharing)

In the last of these times I found no such dealbreaker, but I did want to try a dualboot setup - or dual-login, actually, because I should be able to switch at the greeter - first, to make sure I’m not breaking anything I need for work. This required switching from LightDM to a display manager that supports both X11 and Wayland. I don’t remeber which one I’ve chosen, but I do remember having hard time installing it (I think I couldn’t get it to launch i3 for whatever reason)

I’ve just checked and is seems LightDM supports Wayland now, so maybe it’s time to try the switch again. Being able to use my current DM means I’m not going to risk breaking anything. Probably.

I’m sorry, but the pink&white striped ones are canonically Arch.

1. Approach a business.
2. Request the service or product they provide for free.
3. Suggest that instead of paying, you’ll advertise the fact that you “bought” from them.
4. Argue that your brand is so awesome that associating with it is valuable enough to substitute for the payment.

Isn’t this basically what influencers do?

Neovim has something better - there is a plugin that installs the servers for you - https://github.com/mason-org/mason.nvim - and then you can just use the servers that plugin has installed (which should be more trustworthy because you just need to trust the plugin and not some random executable)

There is also https://github.com/mason-org/mason-lspconfig.nvim which bridges the two and automatically enables servers that were installed via Mason.

The LSP support itself is builtin in Neovim (not in Vim though, AFAIK), but each language server needs to be configured and activated. There is a plugin with all(ish) configurations - https://github.com/neovim/nvim-lspconfig - and activation is done with a vim.lsp.enable("server-name") command, which you just put in your config and the Neovim will start the LSP when you open a relevant file.

This is not about mistakes in the Git-managed code. This is about mistakes in the Git commands themselves. Anything that involves merging/rebasing/conflict resolution can potentially be botched. These mistakes are usually fixable, but:

1. Fixing it requires some Git proficiency behind the level of the common Git user.
2. If you don’t catch it in time, and only find the mistake when it’s deep in your layers of Git history - well, good luck.

So it turns out artificial intelligence can beat natural stupidity after all?

I asked why they had this terrible process and they said it was because people were caught cheating with AI.

How does conducting many interviews help against candidates cheating with AI?

It’s still in the AUR though: https://aur.archlinux.org/packages/neofetch

The demon is Microsoft’s AI

Monkey is for MoonScript

N is for Node.js

O is for Objective-C

P is for Pascal

Q is for QBasic

R is for R

S is for Swift

T is for TypeScript

U is for …

Fix it now, or you go to jail

chmod +x virus
sudo ./virus

I like the description by a Finn who said: Rust is like a car with automatic, while in C (or Zig) you need to change the gears.

I don’t think this metaphor is correct. The automatic gear’s analogy would be the Garbage Collector, which almost every mainstream language has. Rust’s memory management, in comparison, is still manual. Maybe not as manual as C or Zig - but I’d say about as manual as C++. The difference is not that it has some weird gear-changing (memory cleanup) scheme that does not require human intervention - it’s that it yells at you when you don’t do the regular gear changing (memory management) properly.

My condolences

Certainly not for running an LLM on all your files to figure out which ads to show you in the start menu. Why would you even imply something like that?

Why are you asking? Are you trying to prematurely optimize these apps?

I want to forget SVN

Hard drive was made by Tesla