2 ms·
Practically speaking maintaining their own private fork of Mesa is probably more work than it's worth. They really don't have all that much vested interest in s
by stormbrew 13y ago
Practically speaking maintaining their own private fork of Mesa is probably more work than it's worth. They really don't have all that much vested interest in stopping people from using this at all, and not releasing it might mean that people using steam on linux (without steamos) may get a bad experience that's not good for their brand.
- malandrew 13y agoWhy? Maintaining a fork is pretty trivial so long as you don't deviate so far from upstream that it's hard to pull in upstream changes. Every time I use a library and need to make changes that are unlikely to be accepted upstream, I just fork it and update it as necessary. If upstream adopts features that solve my original need, I kill the fork and use the original project.
- stormbrew 13y agoObviously there are scales at which this makes sense, but all situations are not equal. Mesa is not a small project and in the long run it will probably change a lot and in unpredictable ways. Even then, though, sometimes even a small effort is not worth it.