I'm a programmer in Portland, OR doing video processing, graphics and performance on Apple devices. I'm into games, hardware and software.
Currently porting Myst Online to Apple Silicon/Metal as my side project!
| GitHub | https://github.com/colincornaby |
| Homepage | https://colincornaby.me |
I know unified memory is snazzy - but not having RAM slots feels more and more like a mistake. Which my Intel Mac Pro is reminding me of.
I wonder how much ewaste will be created if RAM eventually becomes affordable again and everyone starts swapping out their configs for the ones they really wanted. Instead of the low RAM configs they had to order.
I finally unplugged my Intel Mac Pro and plugged in my M1 Max MacBook Pro instead. It's still under my desk - maybe it gets plugged in again. But software compatibility is becoming a problem. And something is up with the Radeon card in it - and I didn't want to bother figuring out if it was hardware or software.
My MacBook Pro's GPU is slower. But I might move heavy GPU sorts of stuff over to my Windows box. Until Mac Studios are available/affordable.
It's feels like a very classic Apple problem to push the limits of what a reasonable price would be, but then complain that you need to have high prices because no one is buying the thing so the production volume remains low.
Studio Display should be an easy thing to convince most people to buy with their Mac. Tons of people still use eternal displays. Apple treats displays like a luxury upgrade.
5k monitors are really dropping in price - starting to see good quality IPS ones in the $600 range. Apple's pricing of the Studio Display Series is really starting to get indefensible.
I have a 5k mini LED one that I got for around $1000. Not quite as good as a Studio Display XDR. But it's close enough to a Studio Display XDR to make the $2800-without-stand price look real bad.
There were a few announcements before WWDC that made me wonder if this was happening. Guess it didn't happen in time before WWDC!
There have been numerous proposals for a NuGet style package repository - at one point it seemed GitHub was going to be leading the efforts. I'm hoping this is Apple's way of moving back towards named package resolution instead of Git repo URLs.
https://swiftpackageindex.com/blog/swift-package-index-joins-apple
