Getting a CD on the N64 would have allowed for some cooler videos in the middle of the game (and would probably have made things cheaper for developers), but, in my opinion, the thing that really killed the N64 is the tiny (4k) texture cache combined with high latency RAM on the system.
That’s why N64 games have a “look” that can be easily identified.
I mostly have the same experience. I did a Xamarin.Mac app to port some windows code to the Mac. In some senses, it was amazing, because most of the business logic just worked and that saved a bunch of time. The UI was app kit, but with c# to obj-c bindings. That also mostly worked, however, when something broke, it really broke and was incredibly difficult to debug.
There are some use cases I’d recommend Xamarin for still, but the majority of cases are probably best solved by writing native code directly. (Or at least using a portable language such as C, C++ or Rust for cross platform business logic)
Agreed. It’s an awesome feature, but Apple isn’t likely to do the work to replace crappy enterprise software. Those software companies spend lots of time developing central management consoles (is everyone up to date?), they provide “reports” to show that the company is compliant to a ton of requirements (ie. SOX compliance), and other features that describe exactly what their software protects against. While none of those tools provide benefits to the end user, companies dig that crap.
And just to be pedantic, if it’s a newer MacBook, then the included cable is a “MagSafe” cable, which has USB-C on one end and a magnetic rectangle to plug in to charge. (You can still do regular USB-C charging if you want)
I’d prioritize as much RAM as you can afford. It’s shared between the CPU and GPU, and since you seem to have tasks that stress both, extra RAM would be beneficial.
Both the pro and max SoCs can support 2 external displays (max can support 4). The Max has more GPU cores, so some of your workflows will benefit from that.