How do their APIs compare?

Both repositories are not software libraries or services — they are curated Java learning/study repositories made up almost entirely of Markdown documentation (interview prep notes, technical articles, and code snippets used as illustrations). Neither one exposes a public "API" in the conventional sense (no packaged classes, published SDK, REST endpoints, etc.), so there isn't really an API surface to compare.

What each repo actually contains:

h2pl/javatutorial

• A structured set of Markdown docs organized under docs/Java/basic/..., covering core Java topics: OOP basics, generics, annotations, reflection, exceptions, code blocks/execution order, Java 8 features, etc.
• Code snippets are embedded purely as teaching examples inside .md files — e.g., a Generator<T> interface example in [docs/Java/basic/泛型.md:L171-L213], or an annotation-processing/AOP example in [docs/Java/basic/Java注解和最佳实践.md:L214-L283]. These aren't part of a distributable library API; they're illustrative snippets meant to be read, not imported.
• RepoPilot's computed verdict flags this repo as "WAIT — Slowing — last commit 12mo ago," which is a project-activity signal, not an API-quality one, but it's relevant if you were considering depending on it as a reference source that's actively maintained.

hollischuang/tobetopjavaer

• Similarly structured as topic-based Markdown docs (e.g., docs/basics/java-basic/..., docs/basics/concurrent-coding/...), covering things like BIO/NIO/AIO differences [docs/basics/java-basic/bio-vs-nio-vs-aio.md:L1-L31], autoboxing/unboxing pitfalls [docs/basics/java-basic/boxing-unboxing.md:L175-L196], fastjson serialization gotchas [docs/basics/java-basic/bug-in-fastjson.md:L117-L156], Apache Commons Collections usage examples [docs/basics/java-basic/apache-collections.md:L272-L358], and thread pool best practices [docs/basics/concurrent-coding/why-not-executors.md:L1-L10].
• Again, the "APIs" shown (like CollectionUtils.subtract, CollectionUtils.isSubCollection, fastjson's JSON.toJSONString) are third-party Java library APIs being explained and demonstrated, not APIs belonging to this repo itself.

So the meaningful comparison isn't API design but content/documentation style:

• h2pl/javatutorial leans toward foundational language-level topics (generics, annotations, class loading, OOP mechanics) with more emphasis on JVM-level internals — e.g., a deep dive into static vs. dynamic dispatch explaining overload/override at the bytecode level in [docs/Java/basic/继承、封装、多态的实现原理.md:L262-L365].
• tobetopjavaer leans toward practical/production-facing gotchas (fastjson deserialization bugs, thread pool misuse, IO model comparisons, library utility usage) — content oriented more toward "things that bite you in real systems" than pure language theory.

If you meant something more specific — like comparing how a particular Java feature (e.g., generics, annotations, IO models) is explained across the two repos — I can pull that comparison directly from their docs.

FOLLOW_UPS:

• How do the two repos cover Java concurrency topics?
• What does tobetopjavaer say about thread pool misuse?
• How does each repo explain Java serialization?