Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
It can be daunting to look at a popular project in it's current state. Thankfully with Open Source Projects you can go back in time and see how the code evolved.
Here's [1] the first few commits to OpenCore. Much more approachable and inspiring.
[1] https://github.com/acidanthera/OpenCorePkg/commits/master?af...
Depends on the age of the macbook. Older models have reasonable support, newer models are (at best) a pain in the ass.
I generally hit the arch wikis with specific models for the best information.
This github repos also does a good job laying out current support for the 2016 models. https://github.com/Dunedan/mbp-2016-linux
Frankly, I haven't tried on a newer model then that - I don't buy apple hardware anymore.
Can anyone comment on the possibility of going in the opposite direction?
I’m considering buying the frame.work laptop, daily driving pop_os and then virtualizing OSX on it for the few OSX programs I use (this supports framework and not apple).
It looks like it may be fairly easy and possible with a 10-20% performance hit?
https://github.com/foxlet/macOS-Simple-KVM
From what I can tell you can pass through a single GPU with a bit of work, even a iGPU? Is that correct?
> But yes, the serialized dict-of-arrays-of-dicts type stuff can be approached in a few ways, none of which are particularly beautiful.
For what it's worth, this sounds somewhat similar to protobuf (which also supports dicts, arrays, etc).
After spending many years trying to figure out the smallest, fastest, and simplest way to implement protobuf in https://github.com/protocolbuffers/upb, the single best improvement I found was to make the entire memory management model arena-based.
When you parse an incoming request, all the little objects (messages, arrays, maps, etc) are allocated on the arena. When you are done with it, you just free the arena.
In my experience this results in code that is both simpler and faster than trying to memory-manage all of the sub-objects independently. It also integrates nicely with existing memory-management schemes: I've been able to adapt the arena model to both Ruby (tracing GC) and PHP (refcounting) runtimes. You just have to make sure that the arena itself outlives any reference to any of the objects within.
I don't know about Windows, but it runs on Linux, yes, and it works on all M1 Macs (as targets) to my knowledge. See: https://github.com/libimobiledevice/idevicerestore/pull/406
Related posts
- Proxmox VE: Import Wizard for Migrating VMware ESXi VMs
- Quickemu: Quickly run optimised Windows, macOS and Linux virtual machines
- Darling: Run macOS Software on Linux
- Network Type to get Apple Services / iMessage working?
- MAC vs. PC : + Does any M1 or M2 MacBook Air / Pro support nested virtualisation?