That place you were going to will owe to give you the thing you want as a reward for your effort. This is exactly how the world works.

Yes

I prefer Borking News and it’d just be videos of dogs.

Also, 30 years and he didn’t bother with a cover up?

If I was doomed to spend my entire life alone in a spaceship, and the only memento I have from another human being (even if they are my clone) is some stupid ass tattoos on my face - I’d want to keep these tattoos.

*Gasp!*

A talking cat!

Don’t be ridiculous. Where would they get sunlight in England?

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.

made it costly for colors to attend

Are you sure that’s the right link? The Wikipedia page talks about a law that mandates a permit for carrying firearms.

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.

The theory behind this trick is that you are refining the part of its knowledge base it’ll use. You are basically saying “most of the examples you were trained on was written by idiots and is full of mistakes, so when you answer my query limit yourself to the examples that have no mistakes”. It sounds stupid but apparently, to some extent, it kind of works?

That life hack didn’t work for Persephone.

Dr. Seuss would be proud.

The conmen whom you question will make the effort to color your skepticism as demeaning and rude.

You can probably get away with it if you write it in a confusing enough fashion; but you need to make it really confusing - to the point even CPU architecture experts could miss it unless they pay very close attention; and remember that the claims - which are the only part of the patent that has any legal meaning - may be limited by law to a single sentence each, but there is no limit on how cumbersome each sentence is; additionally, semicolons are not sentence terminators; this means that this entire comment I just wrote is technically a only one sentence.

I find no joy in anyone’s death, but in some deaths I do find amusement.

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