There's a lot of nuance to that statement. Most languages, including e.g. Java or Typescript, would not be strongly typed according to your definition, because their type system is "unsound": there are known cases where the type system does not protect you and the types are wrong. We generally still call these languages strongly typed.
In Typescript this is by design. The most obvious is array variance. Typescript makes them covariant because that's what a lot of sane TS and JS code uses them as, but they should be invariant because you can write to them.
Example:
const dogs: Dog[] = []
// A sound type system would error here,
// but there's too many useful cases where you want to do this
const animals: Animal[] = dogs
animals.push(new Cat())
animals[0].bark() // runtime TypeError here
It's non-trivial to implement XML parser in a secure way, many stdlib ones are insecure by default. That should just not be a thing. XML has a bunch of vulnerabilities very specific to it, XXE is the most well known one, but you also have a bunch of DoSes due to expansions and XPath injection etc.
An object serialization format should not have a bunch of footguns and vulnerability categories specific to it.
Microsoft just tried a generation too early. They could have gotten away with it this gen, and assuming 2028 will be start of next gen it looks like next gen it will go over without a fight.
Their managed solution is pricey and especially the linear scaling with how much you use it is very meh. It's comparable with AWS lambda which also isn't cheap. However it's minor on a typical cloud bill.
Self-hosting is very easy in my experience, I've done it for 2 years but management wanted to move to Temporal Cloud. They have a helm chart which just works including upgrades. This does assume you have the whole k8s shebang set up and working in your company. I never had to touch is outside upgrades which took maybe 30m including validation.
This is fully on Apple themselves. USB consortium asked apple to use lightning for what became USB-C, but Apple didn't want to give up the ecosystem control.
That's just plain bullshit? I just checked my local second hand marketplace, and 2 year old flagship models seem to go for about 35-50% of the current equivalent newest model price.
I don't but this. The first 2 generations of iPod didn't even have USB connectors, only FireWire, which was a PITA as most PCs had a USB connection by that time but FireWire wasn't common as opposed to Mac.
It was probably very localized, where my parent worked in the late 90s every office room had at least one, so my parents also bought one for home so they could easily transfer files.
It almost dissapeares overnight once 32MB+ usb drives became common, much more convenenient.
In Typescript this is by design. The most obvious is array variance. Typescript makes them covariant because that's what a lot of sane TS and JS code uses them as, but they should be invariant because you can write to them.
Example: