3 ms·
That "esoteric usecase" was one reason people opposed that change. There are other concerns as well (you can find them if you read the discussion in the GitHub
by dark-star 3y ago
That "esoteric usecase" was one reason people opposed that change. There are other concerns as well (you can find them if you read the discussion in the GitHub issue linked elsewhere in the comments).
For example, it made SimH alter disk images by itself, without warning, even if you only wanted to use them in a read-only manner.
There was also concern that sticking metadata right into the data itself was bad from a preservation standpoint.
Also there was the point that such things should be opt-in instead of just appearing ferom one version to another, without warning.
All of these concerns were dismissed as unimportant or flat out ignored by Mark. Then he went full overboard with his license change (which made a free project non-free)
Edit: removed incorrect reference to the GPL
- trn 3y ago> you're not allowed to add additional usage restrictions to GPL software SIMH is not GPL'd software.
- dark-star 3y agoyeah, you're right, of course. What I meant is that it made a free license non-free and that got people concerned
- swagempire 3y agoMaybe they shouldn't have harassed him -- sounds like he was doing it on his own time.
- rnd0 3y agoPresumably still is -he continues to be involved in both projects (judging by the commit histories).