So, as I update mods and switch more of them over to Fabric, I'm sure I'll frequently get asked "Will you port to Forge" or "Why not Forge," so I figured I'd make a document explaining why and link to it instead of typing up the explanation every time.
Maintaining mods for two different mod loaders is time consuming, and when choosing between them, Fabric is the clear choice to me. If I ever get to the point where my mods are all updated, I will consider porting mods to Forge on a case-by-case basis, but it will not be a priority. The lead developer of Forge, LexManos, has essentially told me he will not support features that allow me to update at least one of my mods past 1.12.2, and on top of that, he did so very rudely while treating me like a complete idiot for trying to make it possible to continue using Forge for that mod. I am not the only person he has treated in this manner, and I do not support this kind of toxic behavior.
I've considered this too, and it is generally more flexible in terms of what I can do with it, and more lightweight. In addition, it has several performance mods which make it so larger packs will generally be able to perform better on Fabric than on Forge. It has all the features I'd expect from a modern mod loader, including a mod menu, a robust configuration library and config GUI (both of which work work better than Forge's), the ability to load mods and hook in to Minecraft where necessary to run code, and the ability to help ensure that mods don't conflict with each other.
As I mentioned, I'd have been forced to abandon a mod. Forge has since added Mixin support, but very reluctantly and only after a very popular modder told them it was needed, despite the reasoning being the same as when requests for it from others were previously shut down and denied. This brings me to my next point, getting fixes or necessary features into Forge is more difficult because it usually requires a lot of argument with LexManos about why it should be added, and his unwillingness to have a reasonable conversation about issues makes that more difficult. If you wish to see the specifics of numerous incidents with LexManos, hop on my Discord and check out the channel dedicated to talking about toxic behavior in the modding community, #lexposting. I've pinned a few good examples, but there are others there too. Another good post is this one by jellysquid3, who has encountered similar issues with LexManos and the Forge community and decided on the same solution.
All of my mods are openly licensed. I do not plan to release any more updates to my mods on Forge, but you are allowed to do so. I'd appreciate getting a split of the CurseForge rewards if you do port any of my mods. Not a modder but still want to give it a shot? I recommend starting off by learning Java. Once you have that down, there are plenty of modding tutorials out there for Fabric and Forge, you'll want to look at both so you can understand what the code is doing before you port it and what you need to do to get it to do the same thing after porting it.
As someone who's mostly worked with mixins in fabric I'm very curious of the actuall benefits of each.
For example I have spent a stupid amount of time trying to get the camera roll to sync with elytra movment in fabric
while glancing at a forge camera capture mod that seemed to do it with ease
(On second thought this rly does not belong here, i might of forgetten that after reading all of that)