Right... I mean the idea is obvious so why even bother with any of it? The only interesting reason is to demo that it actually works in reality which clearly they didn't.

Yeah in order to access native features that Node supports and you can't do on the web, like running processes and opening TCP connections.

Thanks for finally being explicit about the kind of person you are.

As if wokeness isn't a thing 🙄

Woo and it only took 15 years!

The only interpreted language that can compete with compiled for execution speed is Java

"Interpreted" isn't especially well defined but it would take a pretty wildly out-there definition to call Java interpreted! Java is JIT compiled or even AoT compiled recently.

it can be blazingly fast

It definitely can't.

It would still be blown out of the water by similarly optimized compiled code

Well, yes. So not blazingly fast then.

I mean it can be blazingly fast compared to computers from the 90s, or like humans... But "blazingly fast" generally means in the context of what is possible.

Port component to compiled language

My extensive experience is that this step rarely happens because by the time it makes sense to do this you have 100k lines of Python and performance is juuuust about tolerable and we can't wait 3 months for you to rewrite it we need those new features now now now!

My experience has also shown that writing Python is rarely a faster way to develop even prototypes, especially when you consider all the time you'll waste on pip and setuptools and venv...

Unless the C++ code was doing something wrong there's literally no way you can write pure Python that's 10x faster than it. Something else is going on there. Maybe the c++ code was accidentally O(N^2) or something.

In general Python will be 10-200 times slower than C++. 50x slower is typical.

I think it depends on your field and level of experience. I work in silicon verification and most jobs seem to be from recruiters. There's a domain specific recruitment company in the UK that has all the market.

But previously I've mostly got jobs from sending CVs.

Gil looks quite interesting, thanks for the link!

Do you actually have any specific, tangible issue with submodules?

Yeah sure. These are few that I can remember off the top of my head. There have been more:

• Submodules don't work reliably with worktrees. I can't remember what kind of bugs you run into but you will run into bugs if you mix them up. The official docs even warn you not to.

• When you switch branches or pull you pretty much always have to git submodule update --init --recursive. Wouldn't it be great if git could do that for you? Turns out it can, via an option called submodule.recurse. However... if you use this you will run into a very bad bug that will seriously break your .git directory.

• If you convert a submodule to a directory or vice versa and then switch between them git will get very confused and you'll have to do some rm -rfing.

Even in the cases you’re clearly and grossly misusing them

Oh right, so the bugs in Git are my fault. Ok whatever idiot.

the occasional submodule hiccup because it was misused as a replacement for a package manager when it really shouldn’t

I don't see why using submodules as a package manager should excuse their endless bugs. I think you just have low standards.

The UX flaws of Git are very obvious IMO. Even the naming is terrible ("index"? What was wrong with "draft"?).

In normal English, when not using a number, sure! But in software, with numbers versions it almost universally means chronological releases of something.

There are many different versions of Windows, like Home or Enterprise. You can get hardcover or paperback versions of many books.

Great examples! Those are both called "editions", not versions. Thanks for proving my point 😄

That's totally orthogonal to whether your config is source code or not though.