Can a Bare Essentials Mountain Lion be made?

You will find that the applications within OS X are mostly very small in size, because they rely on frameworks built-in to the OS. TextEdit is just a app that uses NSTextView. It's 10Mb. Notes is 8Mb.

Most of the other bundled apps are in the order of tens of Megabytes. The whole Utilities folder is a little more than 500 Mb.

You're not going to save much space, particularly if you want iWork and Office, which are going to be huge by comparison. EACH of the iWork apps is over 600Mb.

As for removing system frameworks and components: therein lies trouble and madness. You will almost certainly break something and cause kernel panics or applications quitting unexpectedly.

Next: you will not improve the performance of OS X by removing stuff. If it's needed, it gets loaded into memory. If it isn't, it doesn't.

The question was asked on the forum recently of how much space does OS X take up. It's very little -- something like 11GB, IIRC.

benwiggy said:

You will find that the applications within OS X are mostly very small in size, because they rely on frameworks built-in to the OS. TextEdit is just a app that uses NSTextView. It's 10Mb. Notes is 8Mb.

Most of the other bundled apps are in the order of tens of Megabytes. The whole Utilities folder is a little more than 500 Mb.

You're not going to save much space, particularly if you want iWork and Office, which are going to be huge by comparison. EACH of the iWork apps is over 600Mb.

As for removing system frameworks and components: therein lies trouble and madness. You will almost certainly break something and cause kernel panics or applications quitting unexpectedly.

Next: you will not improve the performance of OS X by removing stuff. If it's needed, it gets loaded into memory. If it isn't, it doesn't.

The question was asked on the forum recently of how much space does OS X take up. It's very little -- something like 11GB, IIRC.

Click to expand...

I find it absolutely hilarious that 11GB is considered "little" by todays standards.

BeOS, OS/2 Warp, heck- even Windows XP used to fit on a CD image. You might take up 500mb installed (the entire utility folder of OS X as you say). Even Haiku OS today is about 250mb installed, and I've worked with Windows XP Embedded images that were just over 120mb installed (and that came with everything you needed to run and "use" XP- just without the legacy cruft).

As for what the op is asking...

A stripped down version of OS X might be possible (the bootable install system uses one such installation). To my knowledge, nobody apart from Apple seems to have the knowledge or capability of creating one. I'm guessing that if it were possible, it would involve installing OS X from the distribution packages manually by hand using the Terminal included in the installer image. This would be neither simple nor trivial.

As you can tell, I haven't looked into this, and I don't think anyone else has. All I know is that OS X is distributed as a series of *.pkg files, technically they're *all* installed by the standard graphical installer but it might be possible to selectively install only what you want instead. Who knows what the side effects of this might be though.

-SC

benwiggy said:

Next: you will not improve the performance of OS X by removing stuff. If it's needed, it gets loaded into memory. If it isn't, it doesn't.

Click to expand...

I wish Apple would treat the system like it does printer drivers. When you download OS X from the App store it should be a bare essentials install, as the OP asks for, then as you need frameworks and other features, it should download it and then use them (i.e. load it into memory). Kinda like with Xcode. Sure having it on the disk doesn't really impact performance, but its rather a matter of principle, why should I have a bunch of crap installed that I never use?

My proposal would make the downloads from the App store and the installation process faster. And before people complain but that'll take a long time, it doesn't take any longer than it currently does. Right now you download all those apps/drivers anyway, my proposal just postpones that for the future.

You're not going to save much space and you're asking for issues when you go to install OS X updates.

The updates expect all the default stuff to be there. Note that iPhoto/iMovie/GarageBand are not part of the OS X distribution, they just happen to come on every Mac.

I don't use those 3 apps, so after i got my iMac I did a clean reinstall and just didn't install them. This is the biggest savings of disk space you can get on a fresh install.

JohnDoe98 said:

its rather a matter of principle, why should I have a bunch of crap installed that I never use?

Click to expand...

Because that would make for a sucky user experience.

Assuming that you don't use some bit of most of the frameworks most of the time (in which case they would be even less point), then every time you did access a new framework, you would have to wait a minute or two:
"Installing OS framework..... Please wait".

To say nothing of the unnecessary added overhead of a manager that checks what APIs an application is using, whether they are installed, etc, etc.
Disk space is cheap. Bandwidth, for the most part, is not.

A printer is not something you install every day, and most people only use one at a time, so it makes sense to download drivers when needed.

ScottishCaptain said:

I find it absolutely hilarious that 11GB is considered "little" by todays standards.

Click to expand...

The first OS I ever used was on a 16Kb ROM. It had 32Kb RAM, a 1MHz 6502 CPU. The spec of a modern computer is several orders of magnitude larger. This is progress.

benwiggy said:

Assuming that you don't use some bit of most of the frameworks most of the time (in which case they would be even less point), then every time you did access a new framework, you would have to wait a minute or two:
"Installing OS framework..... Please wait".

Click to expand...

No, only the first time you used it. Which you wait for anyway when you download and install the current OS, so its the same, just split up a little bit.

To say nothing of the unnecessary added overhead of a manager that checks what APIs an application is using, whether they are installed, etc, etc.

Click to expand...

This can be included within the apps themselves.

Disk space is cheap. Bandwidth, for the most part, is not.

Click to expand...

Exactly, so instead of downloading everything from the beginning, you only download what you need, i.e. you use less bandwidth.

A printer is not something you install every day, and most people only use one at a time, so it makes sense to download drivers when needed.

Click to expand...

A framework is not something you'd install every day either. It would be installed once.

JohnDoe98 said:

No, only the first time you used it. Which you wait for anyway when you download and install the current OS, so its the same, just split up a little bit.

This can be included within the apps themselves.

Click to expand...

There seems little point is arguing about something entirely fanciful, but you missed the point:
Yes, every time you FIRST used one of the frameworks, there would be a pause while the installer downloaded the framework.
This is when you're trying to do something with your computer, not when you've set aside time for installing.
It would be an appalling user experience, and it will never happen.

And each app having its own routine for checking whether its own APIs are currently installed in the system? Madness.

JohnDoe98 said:

I wish Apple would treat the system like it does printer drivers. When you download OS X from the App store it should be a bare essentials install, as the OP asks for, then as you need frameworks and other features, it should download it and then use them (i.e. load it into memory). Kinda like with Xcode. Sure having it on the disk doesn't really impact performance, but its rather a matter of principle, why should I have a bunch of crap installed that I never use?

My proposal would make the downloads from the App store and the installation process faster. And before people complain but that'll take a long time, it doesn't take any longer than it currently does. Right now you download all those apps/drivers anyway, my proposal just postpones that for the future.

Click to expand...

The odds are you'd need most of the frameworks for every day use. Also having the frameworks be separate downloads would make a nightmare for OS X updates.

What you're suggesting would need Apple to do a lot more testing for each OS release. And cause more user issues. And what if a user isn't connected to the net and needed a framework for the first time?

Your suggestion is just bad in my opinion.

ScottishCaptain said:

I find it absolutely hilarious that 11GB is considered "little" by todays standards.

BeOS, OS/2 Warp, heck- even Windows XP used to fit on a CD image.

Click to expand...

And so would Mac OS 9, but you wouldn't want to run that as your main OS now would you?

As time move forward and capabilities improve, so does people's expectations of the systems.