It's still grossly negligent from a security perspective.

I was born in '90. Some of my most cherished memories as a kid are playing 90's video games: Donkey Kong Country 1-3, Super Mario World 1-2, and later, the revelation that was the N64. I didn't get to watch a lot of TV, but when I did I loved 90's cartoons like Dexter's lab and Arthur (and Mobile Suit Gundam Wing whenever I could catch it, though that was exceptionally rare)

I vividly remember people stockpiling for Y2K and my mom turning on a radio to listen to the reports of 9/11.

I'm definitely a 90's kid, and so is my brother who is a year younger than me ('91).

Confused what you mean. OpenAPI has nothing to do with JS.

Ah my bad, didn't see that Rust was the implementation language. Carry on.

This is a community for Rust, not JavaScript. This doesn't belong here.

I was replying to the other comment, not yours. Though there's not really a way of using rebasing without force pushing unless it's a no-op.

Rebasing is really not a big deal. It's not actually hard to go back to where you were, especially if you're using git rebase --interactive. For whatever reason people don't seem to get that commits aren't actually ever lost and it's not that hard to point HEAD back to some previous commit.

Nope, based on the user's comment history, they're a conservative nutjob.

Yeah, in most statically-typed languages this is simply the default behavior unless you specifically declare a field as optional.

Rust does a lot more than that. It has a far more powerful, flexible, and higher-level type system than Java all while being much more performant.

Every single time I've heard people cite Java's ecosystem, I've yet to see them using anything that Rust doesn't have a better alternative to. Java's ecosystem is massive, but most of the time, you don't actually need it. Unless you are doing a lot of third party integrations that have Java sdks or something, there's not a lot it buys you. If you're just making typical web applications with a database, Rust has you completely covered and will do a better job of it to boot.

That is rapidly changing. More and more huge tech companies are spinning up sizable Rust teams. Rust is basically at the place Go was a few years ago. It's on the verge of becoming mainstream and has a huge community behind it.

I personally view sublinks as pretty pointless and short-sighted. It is frankly not that hard to pick up a new language and contribute to a project for an experienced developer, so I see little reason to try to rewrite it if nothing new is really being offered. If you look at the GitHub of each, sublinks does not have more contributors or anything like that, so the value proposition seems dubious at best.

AC is more than a dex save... And in fact may not involve dex at all if the target is wearing heavy armor.

It's a very consistent system. Direct, targeted attacks with a physical manifestation (that is, some kind of targeted projectile or weapon swing) roll against the target's general-purpose defense stat (AC). Indirect attacks (e.g, fireball) or things that are otherwise simply "happening" to the target has the target rolling a save of some sort to resist the effects somehow (dodge out of the way, resist mental influence, hold themselves upright, etc.). There's nothing arbitrary about it, and a unified defense system would no doubt involve a lot of special-casing/ad-hoc calculations to be at all worthwhile, to the point at which it would be far more cumbersome and confusing.

Let's say we only use AC as a defense and have no saves. How does a spell like Hold Person work? Does the target use their wisdom modifer instead of their dex modifer for calculating AC? Does the armor they're wearing affect their defense against it? What about proficiencies or other bonuses? Since the target is no longer making a roll, how do buffs to protect against the effect (e.g, bardic inspiration) work? I don't think there's a way to do it that is not more convoluted.

Skill checks don't really overlap at all, other than the fact that they use the player's attributes, I guess.