Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Fabric's dependency situation is broken, in some pretty bad ways. It was a good idea! If everyone used jar-in-jar resolution, it'd have solved a lot of problems. But you don't, and the economics of CurseForge make it very unlikely that it'll ever even be possible. Not every player will want Quilt's proposed library resolution auto-download, but it'll be very convenient to most players, and for everyone else it'll be better than getting a random runtime crash with zero useful details.
Fabric's Lead Developer as a Tyrant philosophy isn't necessarily bad; there are significant benefits to having a very unified vision and avoiding design by committee. But it necessarily limits throughput at that Tyrant, and in Fabric's case, that lead to a generally slow level of progress on a lot of important aspects, partly because people spent a lot of time in Discord talking about making a perfect Fluid API, or Config API, and never actually got around to making one, and partly because once they were made it'd spend the better part of a year with things sitting in PR or only as an issue. Forge had a similar problem back in the 1.6-1.7 days (until it finally just got in the habit of getting people sick of having to deal with dependencies and just merging in a best extant normal-person library), but Forge could get away with that when the alternative was vanilla. From a user's perspective, if you want a config system, or standardized (not-TechReborn) energy api, this matters.