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:
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.
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
We’re already on the 6th generation of folding phones though
What priorities are there? I’m talking about emotions, not actions.
You can feel bad for both the children of this guy that will now grow up without a father and the millions of people he harmed at the same time. I’m not even saying I feel equally as bad for his children as his victims’ children (because losing a parent to a preventable death due to insurance is objectively a worse situation). All I’m saying is it’s reasonable to feel sympathy for both. It’s not like the kids had a choice in what their dad did.
It isn’t impossible to feel bad for both?
You can feel bad for his family while also not feeling bad about his death. Losing a loved one is hard regardless of how much money you have. That doesn’t mean it wasn’t ultimately a net positive (although I’m doubtful that UH will actually change any policies because of this)
Decentralized/OSS platforms >>> Multiple competing centralized platforms >>> One single centralized platform
Bluesky and Threads are both bad but having more options than Twitter/X is still a step in the right direction, especially given the direction Musk is taking it in. As much as I like the fediverse (I won’t be using either Threads or BlueSky anytime soon), it still has a lot of problems surrounding ease of use. Lemmy, Mastodon, Misskey, etc. would benefit a lot from improving the signup process so that the average user doesn’t need to be overwhelmed with picking an instance and understanding how federation works.
Archinstall exists which does something similar but with a TUI. I disagree that it’s as easy as Debian’s graphical installer but it is significantly easier than it used to be before archinstall existed.
I like the idea of the local feed, especially for smaller, less generalized instances, but the default should definitely be federated and the wording could also be changed if only because the word “federated” would probably be confusing to non-technical people. Replacing it with something like “All” might be a better idea
Piggybacking off this comment because I completely agree with it.
Did we not learn anything from CrowdStrike? If a comparatively simple fix was able to wipe out half the world, how would something that requires an active choice (where to get certs from) not completely cripple all of our infrastructure?
The problem is that it won’t stop people from using Google. Most people probably wouldn’t even notice aside from having to spend more time searching for local things, which incidentally will give Google more ad money.
The average person probably doesn’t know that search engines other than Google or Bing (or maybe Yahoo if they’re old enough) even exist. As much as it worries me that most of Firefox’s revenue comes from having Google as the default search engine, regulating that practice might actually give other search engines a chance to be seen.
Zangoose is a Pokemon, there’s probably hundreds of sites with it
You have found neither my site nor a site talking about me
Hey did you know that any JSON file is also a valid YAML file? I bet you’ll love YAML a lot more now that you have this information
I don’t have any GitHub.io sites but I appreciate the joke :)
How did you find one of my GitHub repos?
I’d say it is (was? It’s been ~a year and a half since I used it consistently but I’m guessing it hasn’t changed too much since then) moderately left by US standards but definitely not progressive left - you don’t have to go very far to find thinly-veiled sexism/racism/homophobia, though that might just be because a large portion of the people there are terminally online in a bad way. That being said, there are definitely also communities ranging from conservative to hardcore conservative as well but I actively tried to avoid those so I didn’t really see them in my feeds. The same is true with progressive communities but they tended to drift away from being actually progressive once they got to a certain size.