-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
MinecraftForge
Modifications to the Minecraft base files to assist in compatibility between mods. New Discord: https://discord.minecraftforge.net/
Forge comes with a big "standard library" as part of the loader itself, which doesn't count as a mod. Fabric Loader, on the other hand, barely knows anything about Minecraft at all, and "Fabric API", a very popular dependency, is structured as a big jar with like 40 or 50 little mods in it. Each one is counted separately by the loader.
Forge wrote an entire EventBus library, Fabric API has ...pretty much this one class that I could print on one piece of paper?
Fabric API's events are scattered all over the place so there isn't an easy resource to point at, but I can point at Forge's event folder. Have a look around and make sure to check the entity package too. There's hundreds of different events. Oh and there's a whole client events package too. Any given mod is gonna use a bunch of these, especially if it changes existing content in some way, rather than strictly adding simple forms of content like items and blocks.
This means Fabric API's API surface is much smaller compared to Forge's, because you are expected to use Mixin to write your own shit when you need it, instead of relying on the loader or standard library to provide a wide surface of events. Almost every mod, including very simple ones, probably ships with at least a couple mixins. Any given Fabric mod is very likely to be "a coremod" in the Forge terminology.