3 ms·
How much have Windows and Linux changed since 10.6. Quite a bit. But the MacOS X UNIX userland has not. It's over a decade out of date at this point. I've b
by rleigh 8y ago
How much have Windows and Linux changed since 10.6. Quite a bit. But the MacOS X UNIX userland has not. It's over a decade out of date at this point. I've been increasingly running into portability problems, from missing or non-functional commands and associated command-line options, to long-fixed bugs which they haven't bothered to update. Stuff which has worked on Linux or BSD for the last 9+ years, is failing hard on MacOS. Because it's long out of date. The OpenGL deprecation is just another nail in the coffin.
What do I need to do to support the Mac Pro specifically? Well, it's a wider question than that. It's more like: will I drop MacOS support entirely, or will this have sufficiently decent specification that it's worth re-evaluating dropping it entirely. For that, I would need to know about its GPU and VRAM, max RAM, storage options, connectivity, etc. The CPU itself isn't too exciting. And on top of that, what the software support for the GPU would be like. Such as how well supported it would be by MoltenVk, and the existing deprecated OpenGL drivers. Since I will not be using Metal, I need to know if the workarounds are acceptable, or if the result will be awful.
I'm a cross-platform developer in the typical meaning of the word: cross-platform for desktops/workstations of all common operating systems. Serious visualisation software isn't for phones. If "cross-platform" means MacOS and iOS, then lord help us. iOS devices are toys in this realm. Poor GPUs, not enough memory, storage, or power. Most of Apple's Macs are also woefully underpowered, and that's the big reason for abandoning the platform, because they don't actually make a system worth having for high end usage. While they admitted they made a mistake with the Mac Pro, there's zero information about whether their replacement will be adequate for high end needs, or yet another hot mess. Will they be able to return to function over form? I'm doubtful. But without some concrete and sensible information from Apple, it's looking like complete abandonment from over here.
- scarface74 8y agoHow much have Windows and Linux changed since 10.6. Quite a bit. But the MacOS X UNIX userland has not. Still quite vague.... I've been increasingly running into portability problems, from missing or non-functional commands and associated command-line options, to long-fixed bugs which they haven't bothered to update. So you’re writing software that depends on the shell commands... Well, it's a wider question than that. It's more like: will I drop MacOS support entirely, or will this have sufficiently decent specification that it's worth re-evaluating dropping it entirely. For that, I would need to know about its GPU and VRAM, max RAM, storage options, connectivity, etc. You’re basing your software road map on what may appear on the hardware landscape 2 years from now? I hope you didn’t base your development on Intels road map for the last few years.... Since I will not be using Metal, I need to know if the workarounds are acceptable, or if the result will be awful. If you’re basing your roadmap on a deprecated API, that doesn’t say much about your product planning.... I'm a cross-platform developer in the typical meaning of the word: cross-platform for desktops/workstations of all common operating systems. So you’re a “cross platform” developer complaining about Unix support on the Mac? How is that Unix support working out on Windows?