Among a strong field, this is the single most depressing comment I’ve ever read on Hacker News. Several grim components but it’s the “I don’t understand why” which seals the deal.
The game’s difficult to understand so it’s too punitive to not offer even a single practice/example puzzle to use for learning. One puzzle a day is nice once you’ve got the hang of it, but it’s discouraging to “waste” today’s puzzle on learning the rules and not be able to try for real until tomorrow.
What do you mean by “Pagemorphs”? A quick Google search suggests you’re the only person using this term so it’s hard to know what you’re recommending. I think it must mean e.g. https://turbo.hotwired.dev/handbook/page_refreshes?
> Instead, because hooks are they only non-terrible way of using libraries (again say apollo), users/codebases are basically forced to convert their OO components over to FP.
I know what you mean, but in practice it’s easy to retrofit a hook into a legacy class component by wrapping the hook in a tiny functional component. Sure, you have to find some other mechanism (e.g. make it a HOC, or use render props, etc) to make that wrapper component compose nicely with your class component, but that’s the price of not porting the whole thing over to hooks.