I pretty much agree with all the people who replied. VSTs with heterogeneous interfaces, windowing issues, and having to use a mouse all just get in the way of making music for me. Obviously you wouldn’t produce / master some serious but if you’re jamming it’s leagues better imo
I agree you won’t find a DAW as powerful, but some of the purpose built DAWs are so much fun. Loopy Pro you can build whatever interface you want via widgets.
And while VSTs don’t run, the AUv3s on the App Store tend to be much cheaper.
If for nothing else, I think it’s an excellent replacement for a guitar effects processor like Helix. Plus everything is backed up / restorable and you don’t have to suffer with a knob-based interface
Music production is the killer feature that benefits a lot from CPU performance.
I only recently bought an iPad for the first time this year after realizing this was feasible. I’ve always preferred digital music workflows, but hated dealing with a laptop and DAW. iOS supports AUv3 plugins and cross app audio, so it’s pretty much a full DAW experience (I use loopy pro). The form factor forces AUv3 devs to design smarter interfaces.
Plus, I dislike using the iPad for literally anything else, so I’m less likely to get distracted :)
I build the ISO via a Github action as well. The biggest pain point is adding / removing disks after initial install, which I do imperatively (but still disko for mounting / fstab equivalent)
My brief insurance experience with Medicaid was the best I ever had. It was through State of NY. I happened to break my wrist during that time. It was easy to find a doctor, low/no copays or deductible, and they were comparatively easy to contact.
Every other insurance company I've dealt with has actively cost me money, time and unnecessary pain through ineptitude or beurocracy. My FAANG healthcare was good, but had relatively fewer health issues
It's funny, because AWS devs are also a bit guilty of slamming admin credentials and calling it a day.
I was testing out sagemaker studio. I just did the quick setup wizard and the default managed execution role was insanely permissive. I believe read/write to all of the accounts S3 buckets and broad List* for account resources. There are multiple parts of the documentation that also recommended you use this role. It seemed especially wild for a product with so many ways to access. we have good account hygiene but still