Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question about future development & file systems #318

Open
scottperezfox opened this issue Aug 29, 2022 · 2 comments
Open

Question about future development & file systems #318

scottperezfox opened this issue Aug 29, 2022 · 2 comments

Comments

@scottperezfox
Copy link

I just bought a new Mac Studio and have been rocketed into the presented day from my comfy place using Mojave. The new file system seems to be extremely locked down, not allowing any user modifications to the default Apple installation. Is there a future for Monolingual?

Specifically, in Monterey, I ran it, but it hardly made a difference. In poking around, I still see many, many languages (and fonts) installed. What a pain to see Apple forcing this on us and not even allowing a workaround.

The issue seems to be the file system. The whole two-volumes-one-of-which-is-read-only is very new for me, and so far I don't see the upside. Expert users should be able to modify their systems ... I think you all agree.

@IngmarStein
Copy link
Owner

Even before the introduction of the system volume, Monolingual paid attention not to break any code signatures (which sometimes include localized resources, even though they shouldn't) and play nice with System Integrity Protection. Monolingual can still process the user data and remove a fair share of unneeded data, but the impact has been reduced significantly, as you say.

@scottperezfox
Copy link
Author

scottperezfox commented Aug 31, 2022

Thanks for the speedy reply!

You saved me 60MB, which I appreciate, but there are probably another 10GB of languages permanently bolted into the system. So far, I am nothing but disappointed with the new file system and decisions for a read-only disk. Very anti-pro-user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants