This is for STEM, it's possible the humanities are different, but I get the sense from friends that it was not.

My university classes had extensive online learning materials. I never needed to take notes. Or attend classes mostly.
The few that didn't it was easy to get notes from previous years from sharing websites.
At worst you could get notes from friends.
You really only went to TA practice sessions 😄

I thought it was generally accepted that the Nazi party wasn't socialist in any way despite the name.

The company got cursor a few months back and we're trying to use it whenever we can. Context load is much reduced. Especially for legacy codebases or large refactors. Coding velocity definitely increased.
PR review for junior/mids has become a lot more time consuming and madness inducing.

Implicit type conversion. Even back then, even in a scripting or teaching language, that's just such a dark bottomless hole of hair pulling bugs that I can only imagine it was done as a practical joke and went too far.

Your saying that teams that won't adopt SSR out of principle would be okay with adopting RSC without SSR?
It seems unlikely to me that the principal would not extend to RSC on it's own

How about writing a blog post on "when not to use RSC?". Or "the tradeoffs you get when using RSC?"
In one of your earlier comments you said sync engine proponents don't differentiate what scenarios it should be used for. It feels the same with RFC honestly.

I don't know there's a reference. You do offline sync when data is containable and highly reusable - where you'll use database per user pattern is a good indicator.
Social networks, marketplaces, e-commerce don't usually work well. Best use cases are SaaS.

You don't really do social networks as offline-first (even if they have a cache). If you take firebase as an example, security rules on server define filters for data out and reject on data in. When all data is local, aggregations are always cheap.

firebase.google.com/docs/firesto...