Zangoose

That's entirely fair for the usecase of a small script or plugin, or even a small website. I'd quickly get annoyed with Python if I had to use it for a larger project though.

TypeScript breaks down when you need it for a codebase that's longer than a few thousand lines of code. I use pure JavaScript in my personal website and it's not that bad. At work where the frontend I work on has 20,000 lines of TypeScript not including the HTML files, it's a massive headache.

This is the case for literally all interpreted languages, and is an inherent part of them being interpreted.

It's actually the opposite. The idea of "types" is almost entirely made up by compilers and runtime environments (including interpreters). The only thing assembly instructions actually care about is how many bits a binary value has and whether or not it should be stored as a floating point, integer, or pointer (I'm oversimplifying here but the point still stands). Assembly instructions only care about the data in the registers (or an address in memory) that they operate on.

There is no part of an interpreted language that requires it to not have any type-checking. In fact, many languages use runtime environments for better runtime type diagnostics (e.g. Java and C#) that couldn't be enforced at runtime in a purely compiled language like C or C++. Purely compiled binaries are pretty much the only environments where automatic runtime type checking can't be added without basically recreating a runtime environment in the binary (like what languages like go do). The only interpreter that can't have type-checking is your physical CPU.

If you meant that it is inherent to the language in that it was intended, you could make the case that for smaller-scale languages like bash, Lua, and some cases Python, that the dynamic typing makes it better. Working with large, complex frontends is not one of those cases. Even if this was an intentional feature of JavaScript, the existence of TypeScript at all proves it was a bad one.

However, while I recognize that can happen, I've literally never come across it in my time working on Typescript. I'm not sure what third party libraries you're relying on but the most popular OAuth libraries, ORMs, frontend component libraries, state management libraries, graphing libraries, etc. are all written in pure Typescript these days.

This next example doesn't directly return any, but is more ubiquitous than the admittedly niche libraries the code I work on depends on: Many HTTP request services in TypeScript will fill fields in as undefined if they're missing, even if the typing shouldn't allow for that because that type requirement doesn't actually exist at runtime. Languages like Kotlin, C#, and Rust would all error because the deserialization failed when something that shouldn't be considered nullable had an empty value. Java might also have options for this depending on the serialization library used.

As a TypeScript dev, TypeScript is not pleasant to work with at all. I don't love Java or C# but I'd take them any day of the week over anything JS-based. TypeScript provides the illusion of type safety without actually providing full type safety because of one random library whose functionality you depend on that returns and takes in any instead of using generic types. Unlike pretty much any other statically typed language, compiled TypeScript will do nothing to ensure typing at runtime, and won't error at all if something else gets passed in until you try to use a method or field that it doesn't have. It will just fail silently unless you add type checking to your functions/methods that are already annotated as taking in your desired types. Languages like Java and C# would throw an exception immediately when you try to cast the value, and languages like Rust and Go wouldn't even compile unless you either handle the case or panic at that exact location. Pretty much the only language that handles this worse is Python (and maybe Lua? I don't really know much about Lua though).

TLDR; TypeScript in theory is very different from TypeScript in practice and that difference makes it very annoying to use.

Bonus meme:

Gelid cryotheum my beloved

It really depends on what you're printing, how strong you need it to be, and/or what axis you don't mind looking uglier because of layer lines.

In this case OP might have been able to print it on a side with minimal supports, but the idea is that printing it at an angle turns things that would have been overhangs (which are hard for printers to do because of the melted plastic sagging) into upwards slopes. The alternative is adding support material that is intended to snap off (i.e. The block at the bottom of this picture), but those would be hard/impossible to remove in models like OP's that would have supports inside the holes.

Rust is only huge because it doesn't have an ABI. If you had an ABI (and didn't have to compile every single dependency into the binary) the binary sizes would probably drop a lot to the point where they're only slightly bigger than a C counterpart

Edit: I don't know if Go has an ABI but they also include a runtime garbage collector in their binaries so that probably has something to do with it.

The year after epoch overflows?

Step 1: Add ads into [insert app of choice here] that are really annoying

Step 2: Make people pay to get rid of them. Bonus points if it's a subscription

Step 3: People hate your app but it's the one that's installed by default so they use it anyway

Step 4: Profit

You also probably want to put the resin printer in a well ventilated area, as resin printers can also release particles into the surrounding air (and you really don't want to be breathing that in)

We're already on the 6th generation of folding phones though

If I try to switch accounts, tapping an account just doesn't do anything unless I press it a bunch of times and then even then it doesn't really work consistently. It usually works once after restarting the app though (but then goes back to not working after that). Same thing with the "Add account" button

Edit: I lied about the "Add account" part, it looks like that's just hidden behind the side menu which I'm assuming is still a bug, but it does work

Anyone else having issues when switching between multiple accounts?