trias

Hooks as they are have some non-obvious rules which can make them hard to understand / learn. Also debugging is not great (but that's true for react in general, imo)

> private int tm_year; /* years since 1900 */

when you have 4.3 billion years to choose from but decide for 1900.

Good to see that this approach seems to be working for you, i wish you the best.

I've worked with "configuration-based implementations" and in my experience they are hard to work with (no debugging, incomplete documentation and implementation, little flexibility), require an staggering amount of infrastructure, are hard to test and will approach a programming language over time.

Consider too, that i might be blocked as long as i don't have an answer.

possibly some other social factors at play here, but still, my experience.

also loads code from the internet and runs it no questions asked.

i like that qualification :)

most likely typescript is still a very small minority given how large the javascript world is

It would be rather simple: "Here is the testsuite for our (public) api. We support the use cases tested, but no more.

If you want your use case covered, please submit a testcase.

If we change an existing test, we increase the major version.

If we add tests, we increase the minor level.

If the test suite remains the same and we only change the code, it's a patch-level increase."

This could be verified automatically, increasing trust.

I think the OPs problems are mainly coming from the culture/design of Java.

it is not a full course, but more an introduction.