Tuist VS tart

Yes! That’s actually what https://tuist.dev is doing. They use Lume to spin up ephemeral macOS VMs with Xcode preinstalled, so they can run builds in clean, reproducible environments. It’s great for CI workflows where you want full macOS without managing long-lived hosts

At my current workplace, we use Tuist. It's a great tool, but there are 20 of us, so it's necessary. In smaller teams (up to 5-7 people) I didn't feel like there were huge problems with .xcodeproj. Sure, some conflicts now and then, but far from every time you merge something. https://github.com/tuist/tuist

Tuist Projects ('Project.swift'), Swift packages ('Package.swift'), and barebone xcodeproj are now supported.

On a project I worked on I transitioned the codebase to a micro framework setup using tuist.io.

I think the hate comes from seeing its unresponsiveness and slow builds in large-scale projects. Everything works great in a recently-creates project until your project turns into a complex dependency graph of targets with intricate and inconsistent build settings. That’s the main reason why we are building https://tuist.io

The title is a bit misleading then :)

What’s the difference between this vs just using your lume CLI? Right now it feels like a worse interface to lume, but maybe I’m not getting a use case for this.

Also, any thoughts on https://github.com/cirruslabs/tart? (alas, not open source)

the inability to log in with an Apple ID in a MacOS VM is a decision made by Apple. you can certainly sign without logging in, but I don't think you can submit to the store in a VM.

you can see how they build tart here, including signing and entitlements and so on: https://github.com/cirruslabs/tart/blob/main/.cirrus.yml

Boots in 5 minutes, minimum allocation of 24 hours, is "low stock" if you actually try to allocate one, and was recently "no stock". I'd be unsure if its actually available when you need it.

Would be nice to see a Virtualization.Framework as a service, such as with Tart [1], but perhaps there are performance and security issues when making those M1s multi-tenant. The license limits it to a maximum of two guest systems, and only for the purposes of software development and testing [2].

[1] https://github.com/cirruslabs/tart/

[2] https://www.apple.com/legal/sla/docs/macOSVentura.pdf#page=2 (2B iii)

I haven’t used UTM personally so I can’t vouch for that. There is also Tart.

For a full reproducible solution, I thought of this: https://github.com/cirruslabs/tart

tart, uses also new Virtualization framework and supports ARM Linux on upcoming macOS Ventura

An alternative: https://github.com/cirruslabs/tart