What's the advantage of compiling to Rust here? Maybe it would be faster if they just skipped straight to LLVM.

I don't think this is intended to fundamentally change what a terminal/shell does - it doesn't even go as far as Nushell. It's just about modernising the interface.

Nonsense. There are way more programmers now than there were in the Windows 3.1/9x era when you couldn't avoid files and folders. Ok more people are exposed to computers in general, but still... Anyone who has the interest to learn isn't going to be stopped by not knowing what file and folders are.

It's like saying people don't become car mechanics because you don't have to hand crank your engine any more.

Typescript is far nicer than Python though. Well I will give Python one point: arbitrary precision integers was absolutely the right decision. Dealing with u64s in Typescript is a right pain.

But apart from that it's difficult to see a single point on which Python is clearly better than Typescript:

• Static typing. Pyright is great but it's entirely optional and rarely used. Typescript obviously wins here.
• Tooling. Deno is fantastic but even if we regress to Node/NPM it's still a million miles better than the absolute dog shit pile of vomit that is Pip & venv. Sorry Python but admit your flaws. uv is a shining beacon of light here but I have little hope that the upstream Python devs will recognise that they need to immediately ditch pip in favour of officially endorsing uv. No. They'll keep it on the sidelines until the uv devs run out of hope and money and give up.
• Performance. Well I don't need to say more.
• Language sanity. They're pretty on par here I think - both so-so. JavaScript has big warts (the whole prototype system was clearly a dumb idea) but you can easily avoid them, especially with ESLint. But Python has equally but warts that Pylint will tell you about, e.g. having to tediously specify the encoding for every file access.
• Libraries & ecosystem. Again I would say there's no much in it. You'd obviously be insane to use Python for anything web related (unless it's for Django which is admittedly decent). On the other hand Python clearly dominates in AI, at least if you don't care about actually deploying anything.

What is fatphobia? I think he was just saying it's easier to let yourself go and turn into a blob than to stay healthy. Definitely true no?

This is just an excuse. A poor one.

I think those jobs are a myth. You probably get like a 20% premium for using COBOL, so if you look up the salary of a Cobol consultant in America it's going to seem like an enormous salary on an absolute scale.

But so is a C++ consultant in America or whatever. Probably not worth learning COBOL for.

Feel free to correct me if I'm wrong, but I have looked once or twice and the COBOL salaries seemed entirely normal.

Why would you be interested in 6 levels of abstraction at once?

Because there aren't 6 interesting levels of abstraction. It's like talking to a child:

What are you doing?

Finances

What does that involve?

Processing money.

What kind of processing?

Summarising

What kind of summaries?

Summaries of everything

What specifically though?

Summaries

Ok so you're just displaying total balance then...

Haven't tried Rye but I have used uv (which Rye uses to replace pip). Pip install time went down from 58s to 7s. Yes really. Python is fucking slow!

Honestly it's quite obvious from the code snippet and the diagram but I can spell it out:

Go is a quite nice language but mainly because of its fantastic infrastructure. Compilation is very fast, cross compilation is trivial, it makes static binaries that don't even depend on glibc (compatibility nightmare on Linux), the module system is great, it even has built in fuzzing support - how many languages have that?

However the language is decidedly meh. It doesn't have some modern features that make programming much more pleasant. Notably:

• Tagged unions, aka discriminated unions, aka sum types. These vastly improve type safety and are just very convenient.
• Expression based. People can go overboard with this but I don't think anyone who has used an expression based language would want to go back. Some common tasks like the let msg in the example are just so tedious if match is a statement.
• Optional. Somehow Go copied the billion dollar mistake. In fairness languages like Typescript and Rust weren't around when Go was designed so it may not have been obvious to the authors that this was the way to go.

So this is basically a do-over of Go but if it had been designed by someone familiar with these modern best practices in language design.

Why is that a hard pill to swallow? Longevity doesn't imply goodness, especially in software. Same for Bash, C and gnu utils.

It also doesn't mean it's a good idea to use it. I would strongly recommend... basically anything else over Jenkins.

Maybe I missed your point there.

I liked Netbeans much more than Eclipse. It didn't have that stupid workspace system at least.