4 ms·
I wrote it because I was interested in the project. I like hearing about technical challenges in graphics and overcoming them. But as I got into it, it wasn’t j
by thewebcount 4y ago
I wrote it because I was interested in the project. I like hearing about technical challenges in graphics and overcoming them. But as I got into it, it wasn’t just a list of “we faced x, y, and z challenges, and here’s how we overcame them.” It was “because Apple are jerks, they didn’t do everything exactly like everyone else.” For example, they say:
“Even with all the hurdles, roadblocks and brick walls put in our way, we're finally back on Mac!”
Hurdles - sure, things are different and it’s a challenge. “Roadblocks” and “brick walls” say that the author believes Apple made things that way with an intention to keep them from writing their software. This isn’t like some copy protection that is literally trying to fool would-be hackers. It’s just a slightly different way of doing the same thing. (I’ve done ports from OpenGL to Metal, so I’m aware of many of the differences.)
It wasn’t even specifically about Apple. It was just the fact that I didn’t want to hear a list of personal grievances with a company they don’t like. I just wanted to understand the technical challenges and solutions without all the moaning and bitching. As I said, it’s pretty impressive on its own. No need to add a bunch of fluff that detracts from it. It just reads like somebody typing “Micro$oft” on Slashdot 20 years ago. Grow up already.