Just take a look at the security hardening at disk level, war on kernel extensions, continued reliance on entitlements for basic functionality (that is not just limited to sandboxed processes). Coupled with bootargs (like amfi_get_out_of_my_way) being broken for multiple OS versions, and it leads me to a pretty clear conclusion.
Actually, the Mac Pro’s biggest problem is the iPhone. Or rather, Apple’s one-trick-pony design of their quote unquote "desktop class" SoC to be just the iPhone SoC, but a little bigger, with the only scale options being multiples of the same chip, with everything soldered on the SoC, and then some thickheadedness on “we didn’t design the architecture with external GPUs in mind”. Apple is already getting beaten by performance-oriented traditional CPU systems, and soon, other vendors will optimize for battery life as well. And Apple will still be stuck with an iPhone chip in all their computers.
But that’s OK, because it seems they are pushing their desktop OS in the direction of a phone OS too, both in capability and lockdown, so it might all be good.
I don’t think that’s true. I remember, for several years now, how after each VC capital, they boast how they are to “double in size”. That’s not just ad sales.
I am sure that this part of the business is a tiny, tiny fraction of the current bloated workforce. Know what, agree, it’s a hard job, keep all those people in. I think they are mostly relying on the volunteer mod force, rather than internal people, but whatever. Keep them all. Still 200-300 is more than enough.
Trim the workforce. How many engineers, UI/UX, product and QA do you need to run a reddit.com? Likely, 200-300, not 2000! Focus on the core product and the profit will come.
It breaks more often than it doesn’t. Yes, the page “scrolls”, but it scrolls only a few pixels, while the internal “custom” scrolling implementation doesn’t respond to the event and does not scroll to top, resulting in a terrible UX.
Didn’t that team at Apple (with Lattner at the helm) also claim Swift was “faster than C”? I am yet to be convinced that in the general case, this is true, especially with the recent language bloat and lack of substantial compiler optimizations. But it wasn’t true back when Swift was released either.
I am not familiar with any motherboard that does not expose all its capabilities through BIOS or UEFI. Yes, it might be less convenient to have to reboot to set a fan curve, but it’s certainly possible. And the Windows software is so terrible anyway, going through BIOS is always my first choice.
The Mac Studio in particular is a terrible example to use here. At least the first iteration of it. It has a fan that is constantly spinning, and it’s a cheap fan, so it creates a very annoying whine sound at low RPMs:
You seems to live in the 90s or early 00s, sorry. Consumer fan technology has come a long way since those days. Case sound dampening has also come a long way, so the little noise that fans do make, it gets pretty well dampened inside the case.
Really should be no yelling! If the place you are visiting has assholes yelling, just leave for another. But like any major purchase, it takes research. I do this research every 4-5 years or so, when I will be undergoing a desktop replacement. I’d choose the CPU and GPU first, then investigate cooling solutions. Liquid cooling is not always optimal with regard to noise, so another decision to make before committing on a solution is if you’ll be overclocking or not, as there are air-based cooling solutions that could be silent, and give you all the TDP cooling your CPU needs. After you’ve chosen your cooler (liquid or air-based), investigate low-noise, high-airflow fans at the size your cooler accepts. Going the largest fans is not always the best choice for optimal airflow or noise, so factor that in the investigation. I have less experience with custom GPU coolers, as I’ve only used stock coolers—those are pretty silent and well optimized these days.
I don’t know what tower case you are using, or what cooling system you have set up, but in modern times, if you hear much noise from your cooling solution, you have chosen components poorly. From fans to pumps to dampened cases, you could have build a relatively silent system.
I changed the user agent of the Mac Safari to be that of iOS, and changed the window size to be in portrait, yet it still does knows it’s not a mobile device. How does it know?
From my experience (not on the web), frameworks that take their Unicode support seriously fare quite well by now (nothing is perfect), while frameworks that make silly assumptions that everything is ASCII do not.
Should be “תל אביב”, not “ביבא לת”. How do these issues even exists in 2023? Is a team building these renders not aware of RTL languages, or do they just not bother implementing it?
“Runtime dispatch” does not require that the CPU feature be queried on each call. There are designs that can do a single query on launch and set up the environment so that future calls do not incur any additional penalty.
Raw milk should almost never be drunk in today’s reality, regardless if you know where it came from. There is enough asymptomatic bacteria in cows that is really bad for you. Somehow raw milk became a religion in the US, but it’s really really unhealthy.
But isn’t Reforged using the same engine as the original, with higher res assets (mostly textures)? At least, I thought so, as that was part of the criticism of Reforged.
Then something in the UX is broken. From your store images, I understood that clicking on that tab menu item, it would display last archive date and ask to rearchive, no?
There is a reason why most Safari extensions apps do not just show an icon and a label, but actually explain how to use their embedded extensions.
Big reason for this is that most “FOSS” teams are hard-core keyboard navigation nerds (no offense intended, we know who we are), and so, their preferences are completely different from what normal computer users want, so even with access to source and unlimited free time, there is a high probability that a pull request would be shut down because the maintainers don’t want or don’t understand why spacing between elements is 8pt (“2px is just as functional as I want it”) and why keyboard autocorrect should be off for that text field (“what is autocorrect? Never heard of it”).