There’s almost an actual basis for this in the rules, in a “near-disaster” situation where a team loses all quarterbacks in season, they’re essentially allowed to loan one out for the season from another team.

Just need to define “all the available QBs are ass” as near-disaster

boneheaded throwaway pick-six notwithstanding, it feels like this game is going to be a hard game on which to judge that

Why risk an unblocked rusher into your boot on 4th&1? Just run the damn thing

Most of all, I love that I can just Use The Platform™ (async/await, classes if I want for things, custom elements)

React is fine, but there's enough abstraction away from The Platform (esp. if using popular ecosystem libraries) that it's sometimes frustratingly difficult to just get to The Platform

The problem is certainly more pronounced in certain ecosystems than others. e.g. I notice it more in JS/TS and Python, than say Ruby, Go, or Rust, which is to say the much larger ecosystems

... and because there's so many of these higher-profile commercial OSS projects now, I think there's a perception that its a requirement to have this polished level of marketing from folks whose introduction into open-source is these primarily projects, vs. some C library made by one person in NE

I think a large part of this is related to the commercial capture of OSS by SaaS companies that are mostly looking to attract free labor

OSS projects funded by large companies that have paid teams dedicated to them can spend time (or hire out) the effort to polish their marketing...

I could not have done that Raiders punt (complimentary)

eventually you get numb to the pain