Your wakeup call

[pie_flavor]

@BrainStone

The thing is to my knowledge (which is public announcemnets and discussions) it was never attempted to overcome. It was ruled out right from the beginning.

There’s literally only two status updates to look at and it’s smack dab in the middle of one of them:

@Owen

As many of you have noticed, the 1.13 update has been taking a significant amount of time to complete as a result of the significant changes that were made to both the base game and the simultaneous changes to Forge’s toolchains (more on that below). These changes have meant that in order to properly update Sponge for 1.13 approximately 150,000 lines of code need to be updated, in addition to the time spent waiting for the new toolchain to be built. While it would have been possible to rush out an update earlier by making a lot of quick fixes, we’ve decided to do this update properly so that our developers don’t have to maintain those hacks in future. Thankfully this is largely a one-time effort, for 1.14 and future releases we should have an easier time updating as a result of doing this update properly. We appreciate the Sponge Community’s patience while we continue the development process.

@BrainStone

I’m not talking about minutes, hours, days, weeks or even months. I’m talking about years. The Forge permissions API implementation is a great example of it.
My favorite part of the discussion is the part where Lavitan essentially say “We should have done it from the beginning”. Which I do agree with. The question remains, why is it not merged then yet?
The code is ready. It has been reviewd several times, it has been confirmed to work and it bridges a gap that never should have been there in the first place. Now this carries special significance with me because I’m on the other end of the issue. I as LuckPerms support get constant complains about that exact gap.

And yet more work gets done, even after your comment. If it was as cut and dried as you say it is, it would be pulled, and I note that you have not waited around to hear phit’s elaboration. Meanwhile, this is an isolated phenomenon. I’ve never experienced slowness like this with any of my own PRs.

@BrainStone

And while you think that shimming 1.13/1.14 support is a bad idea for your reasons I’ll say I think it’s a good idea for my reasons.

Your reasons are ‘because it would be faster’. You do not seem to grasp that Sponge’s reasons are ‘no it absolutely wouldn’t’. The majority of the work is in updating the implementation; the shim would take development time away from the implementation and so it’d end up taking even longer.