ProxyJump is a special case of `ProxyCommand ssh -p @`. Can't replace the `ssh` in there when using ProxyJump.

"It was the Hyundai Corpo that broke the law! They're stealing American jobs! That's why ICE targeted them! No, I have no evidence, only blind belief. Why are you even asking me for evidence?! What about when Hyundai did bad things in the past???!!?1?"

----

If it:

1. Repeats the arguments of fascists.

2. Defends fascists.

3. Attacks the victims of fascists.

What do you think it is? A duck?!

In fact, this party has a — by now well-established — track-record of precisely this bad behaviour. They haven't even tried to hide their actions, only their individual faces. They've been public about their disdain for the law, for humanity, and their general evil plans.

And here you are accusing their victims of crimes you, like them, have no evidence of.

If humans had evolved to do prompts (while retaining everything else that makes human thought human), that number doesn't sound that big.

OTOH, if LLMs had to do everything humans need energy for, that number would be waaay too big for LLMs.

----

Humans don't even have an efficient energy input system. How many of those 1.3M joules actually get assimilated? Silicon is a lot more efficient at energy, because a lot of effort has been put into making it so, and is fed raw energy. It doesn't need to process food like humans, humans already did that for it when they captured the energy in electricity.

----

I'm sure there's more ways of making the comparison more fair, but I doubt your parent was trying to prove their claim with such deep research. So let me try another angle: No human can burn through as much energy as the top hosted LLMs do for one prompt, in as much time.

Not a hard rule, honestly.

Some Indian languages exhibit a blurring of sorts with Ye- sounds. E.g., in Telugu, the word for 'How' is 'yela', which is often also pronounced as 'ela'. TBF, Telugu also blurs Ve-/We- sounds similarly.

I belong to the class of people who believe in customising their tools as they please. So I'd have written an Emacs package to do this. But then again, this is Emacs, so someone's probably already done it. Oh, here it is: https://github.com/mooreryan/markdown-dnd-images

Patently false. Been using profiles for years.

> bunch of hacks, such as containers, which are cumbersome to use. Firefox's "solution" forces you to switch Github tabs between personal and work containers constantly.

Rarely have I had to that. Until I added rules to open certain URLs in specific containers.

> Chromium provides separate windows with different profiles, and Firefox should follow Chromium here.

Absolutely not. Profiles are a poor "alternative" to containers. How do I add a rule to pin URLs to specific profiles? How would that even work, if it did? A new window for some links? Re-use some random window with the same profile? How do I switch to it? Switch back? Don't tell me to use the Window Manager via Alt-Tab. I organise tabs into windows by shared context.

Then there's the whole issue of sync. Profiles don't share anything. Each profile needs to be configured individually. I like not having to add uBlock Origin to every browser profile. I like not having to think if I have my password for this rarely visited site in this profile or another one. Or a bookmark. Or form info.

----

Just because containers have no use to you / you couldn't find a use for them, doesn't mean the rest of us also shouldn't have the luxury of using this feature. Feel free to use Profiles as you'd like. Leave what works for us alone.

Too bad all you're gonna get is a botched and broken nation and years of misery, but that shouldn't matter as long as you get "something for my money".

And you're sure you're gonna get "something for my money" with people that make no attempts to even veil their corruption and lawlessness. Right? Say, are you, by any chance, "rich"? I mean, rich enough to be considered rich by the oligarchs, that is.

> modern email

That can't be true. Now, I haven't used Outlook myself, but I've received enough garbage from that godforsaken relic of a time when MS wanted to EEE email to know that that can't be true.

FWIW, I've posted patches to the PG mailing list just fine with GMail. The web app, that is.

But I think the biggest reason I hit that number so easily was the ridiculous ease of batching. Starting with a query to select one task at a time, "converting" it select multiple tasks instead is ... a change of a single integer literal. FOR UPDATE SKIP LOCKED works the same regardless of whether your LIMIT is 1 or 1000.

A single application-layer thread doing batches of batch creation (heh). Not instant, but fast enough. I did have to add 'batchmaker is done' onto the 'no batch left' condition for worker exit.

> ... that pushes the locking from selecting queue entries to ...

To selecting batches. A batch is immutable once created. If work has to be restarted to handle new/updated objects, all batches are wiped and the batchmaker (and workers, anyway) start over.

Redesigned to create batches on the fly and then `SELECT FOR UPDATE batch SKIP LOCKED LIMIT 1` instead of `SELECT FOR UPDATE object SKIP LOCKED LIMIT 1000`. And just like that, 1000x reduction in load. Postgres is awesome.

----

The application is for processing updates to objects. Using a dedicated task queue for this is guaranteed to be worse. The objects are picked straight from their tables, based on the values of a few columns. Using a task queue would require reading these tables anyway, but then writing them out to the queue, and then invalidating / dropping the queue should any of the objects' properties update. FOR UPDATE SKIP LOCKED allows simply reading from the table ... and that's it.

> ... takes solutions that require engineering teams.

All it took was an understanding of the data. And just one guy (me), not an "engineering team". Mongo knows only one way of sharding data. That one way may work for some use-cases, but for the vast majority of use-cases it's a Bad Idea. Postgres lets me do things in many different ways, and that's without extensions.

If you don't understand your data, and you buy in to the marketing bullshit of a proprietary "solution", and you're too gullible to see through their lies, well, you're doomed to fail.

This fear-mongering that you're trying to pull in favour of the pretending-to-be-a-DB that is Mongo is not going to work anymore. It's not the early 2010s.

----

I work on a large C++ codebase that takes quite a lot of CPU and RAM to build. To ease development access, we set-up a beefy VM in the cloud, put LXD in that, and gave every developer an LXD container of their own. Access via SSH was simple: ProxyJump via the LXD host (VM) into you container.

Now, I don't use VSCode, I use Emacs, and my container was setup by me to do everything The Right Way™. Devtools like clangd and clang-format were installed via the OS package manager. Everything Just Worked™. The VSCode users on this team had their own containers, so however their setup was didn't affect me.

Until one of them connected their VSCode to my container. My dev setup broke because their VSC decided to download a Microsoft-built binary of clangd and install it onto the PATH in my container. I was horrified, but the coworker who had (inadvertently) done this didn't see the problem. Their VSC worked just fine. I had to write-off that container of mine and create a new one.

Today, we mandate use of the LLVM-provided clangd extension in VSCode in the team, which does not automatically download anything from the internet. But this habit of "helpfully" auto-downloading LSP servers is apparently still common among VSC extensions. To the point that the Emacs lsp-mode package also offers to do that. Thankfully, it's Emacs, so it's pretty easy to disable that behaviour.

----

As we SSH into machines quite a lot, we strongly discourage per-container SSH keys and strongly encourage SSH Agent Forwarding instead (with per-use confirmation). VS Code found a way to break that too. But we couldn't wait for the VSCode overlords to fix it — we were affected already, and urgently needed a fix — so we looked into what could be happening.

Turns out, VSC hijacks the way your shell loads, all so it can inject arbitrary stuff into the embedded terminal. You think you know how and when bash loads ~/.bash_profile and ~/.bashrc and so on. None of that matters because VSC uses its own homebrew init script for bash. A script that tries to, emulate how bash loads, though not entirely accurately.

If you're building a terminal emulator and you want shell integration, the correct way to do it is to ask your users to load your terminal's support code into their shells. The VSCode way is to never tell the user anything and just silently take over their shell for them.

----

Now, I no longer even try to support VSCode on the team. VSCode users are on their own. I help them setup Vim, NeoVim, Emacs, or even IntelliJ. If they have to have VSC, I might look into Eclipse Theia. But, as far as VSC is concerned, I expect nothing less than this malware-style behaviour and thus refuse to waste my time on it.