Okay - I am a bit of a dreamer, but I hope that Mojang dropping the obfuscation side of things is a sign that they are interested in working more closely with the community.
Of course, if I were to put on my pessimistic hat, I might think this is a move for Mojang to distance themselves from the Java edition as it’s likely that Microsoft thinks from a business perspective focusing on Bedrock is a better deal.
Get Mojang to pull in large optimizations. Thus far, they have been uninterested in this (though some controversy over Optifine may have left a bad taste).
I remember that. I think the issue there was it mostly handled badly… It seemed like Mojang was trying to go behind the communities back (which I thought sounded a lot like the way Microsoft does things…so I blamed them instead of Mojang). IMO - if this is an era of more open-collaboration it may be possible for Mojang to benefit from working with the community. (There is an excellent example of this in the way AMD has worked with the Open Source community…)
Pull the changes into a modding framework. Understandably, Fabric/Forge aren’t willing to pull in a huge overhaul they’d have to maintain. Mojang may have similar feelings.
I can see that too… That’s why I am thinking that it might be possible for there to be a more collaborative effort… Like a repository set up where community devs can submit PR’s for changes, and Mojang can either approve or deny them. If that started working well, I could see a situation where there are specifically Mojang employed community devs, the role of working on changes that will help both the main Minecraft tree and the modding community.
(Okay, I am probably more optimistic than I should be – after all Microsoft is in the mix here…)
Right, but this means these efforts can be undertaken on the current release, and done without having to work around Mohjang’s obfuscation.
Removing this kind of barrier is a major change. Less time will be spent on trying to understand code that has been obscured from view. It will be easier to ensure “correctness” in code that is optimizing the server (ie, that new code will not break internal dependencies). It will be easier to ensure compatibility between the official release and community based extensions.
I understand that the modding community has been able to do a lot up to this point…(I play on an optimized modpack). But, I’m betting this will actually produce a larger jump in terms of the efficiency of all codebases - including Mohjangs. Just the reports that document issues (not CVE level issues) for Mohjang will lead to them improving the base code.
Not only do I think this will generate a fair number of CVE’s, I think there will be a lot of optimization of the code going on.
Look at what happened with OpenOffice a few years back – the Oracle buyout of Sun Microsystems forced the forking of OpenOffice to LibreOffice – during which the new Dev team took the time cleanup and refactor the code. This resulted in a suite that was about 10 percent smaller, and removed a bunch of redundant things (like multiple copies of icons).
I bet we see something similar with Minecraft – even if it can’t be an “authorized” version.
Yeah, Mojang’s conservative development style is arguably the reason for Minecraft’s success, while also being a source of frustration and friction for the community, IMO.
MS is another story altogether, though. While Mojang is a very thoughtful company, MS is driven by profit. I’m honestly surprised there aren’t more collisions between the two cultures.