If they removed it once they knew it:
- People would not have used private modules today
- No one would have cared
- A sufficient replacement would have been made which we would have been able to use today
If they remove it now:
- Thousands of game = broken
- Many upset developers and players
- Owners of smaller places need to pay a lot for the same functionality they had with private modules
- Basically removing a little needed feature on the Roblox platform
- People care
- Almost forgot; people lose their income
Removing items after it’s being used by a large amount of users, you should not remove it without a replacement. The same story can be told about NPM (Node Package Manager) once had an incident, where a module was used widely, and millions of users relied on a package.
Then, Kik (messaging app) had an infringement with a package named “Kik” by an author. The author of course had no right to continue to keep the name, but in the discussion, he got so sad and upset, that he removed every package that millions of users used and relied on, and several thousand sites went down because an important thing was removed. This is not related to this story, but it shows the consequences. It was so dramatic for NPM that they decided to make huge internal and functional changes to their site to avoid situations like this.
Now think of this with private modules. Thousands, if not tens of thousands or hundred thousand places use private modules in their game and potentially rely on them. Removing them would break those games that rely on them.
No, we cannot change the past, you are right, and yes we can change the future, also right. Why remove something thousands of games rely on without a sufficient replacement. Here we go, “security risks”. There is no longer a point for me to continue in this discussion as all my points have already been stated in this, and in my former posts.