Unfortunately this isn't true. They're certainly better than what they used to be, but they are no where near as reliable as Nvidia's. We tried a build out roughly 6 months ago and we couldn't switch back fast enough.
Are you talking about windows GPU drivers for gaming? I haven't had problems on Linux in a long time and I am honestly surprised with how many hours I have spent gaming on Linux with Proton.
The funniest outcome with this whole “Apple vs. Beeper” saga would be if Apple said, “Fine use the iMessage protocol. We won’t break interoperability and you can even have full feature parity…
BUT… Any messages sent this way will still show up as the dreaded “Green Bubble”.
(I hope Eric and the Beeper team can pull through!)
Messages sent via SMS or iMessage already look identical to the recipient, the only distinguishing feature is a small header at the top of the conversation that says either "Text message" or "iMessage".
SMS doesn't support emoji reactions, read receipts, typing indicators, high quality pictures/video, or groupchats over 10 people. These are deal-breaker for anyone that texts regularly
Before M1, Hackintosh was giving top-tier performance for 3-4x less money. With a day's worth of research. And then an hour here or there when doing yearly upgrade.
This is bad advice in general, but it's especially poor advice given the fact that the "crazy person" is running the company. OP needs to lawyer up immediately before (more) damage can be done.
I've had noticeable issues with "WindowServer" in the past (taking 80% CPU usage and causing the fans to ramp up even when the system seemed like it should be idling even after a reboot) so I decided to give this a shot.
This is anecdotal but there is a noticeable difference for me with responsiveness after following these steps. Currently the WindowServer process is hovering around 14%.
Most likely the issue was resolved by the reboot, not by uninstalling Chrome. From my experience Mac OS tends to slow down after a few days. Animations and scrolling gets choppy and there's nothing I can do to fix it, short of rebooting.
I can assure you that it wasn't related just to rebooting as this has been something that's been bugging me for months. I had previously rebooted earlier in the day because of this exact same issue (a runaway WindowServer process), before I saw this article. I also did a fresh reboot before following these instructions too as a sort of "control".
The change only happened for me after removing Chrome as well as the launch agent for keystone.
I use macOS daily for months at a time without rebooting and have not seen this problem on any of the 5 Macs I've been using for the past several years, for what that's worth. It does seem like it's something specific to your machine.
Does your system have Chrome on it, because if it doesn't then you observations don't really apply since the conversation is centered around a bug possibly associated with that. Personally I don't allow chrome on my machines. I do install brave for those cases where I have to use "chrome" because some company simply doesn't design their web app for anything else otherwise it's firefox.
(I have recently started using Apple tools for developping with Swift/Xcode on iPad. I am very unimpressed by the quality of the tools, and quite impressed by the range and depth of features....)
I was pleasantly surprised how fast I went from signup to actionable data/graphs (roughly 2 minutes). Based on your landing page I was expecting to have to spend considerable more time on it.
Perhaps you could include a demo to show how quick it is to get setup and have something useful?
Demo is a great idea! It's easy enough to record myself going through it. Like you said, it takes just a couple minutes to get going so it would help to highlight that :)
You can combine your demo and onboarding process into one thing. My favorite example of this is NewsBlur: https://newsblur.com/ (Hit the "Try out NewsBlur" button)
Basically, drop them into a demo of the product with pre-filled data. They can make changes all they want, and if they want to save it, they'll need to register an account.
The reason f.lux sideloaded app got pulled is because they didn't release their source code. Instead, f.lux relied on loading/patching a binary that bypassed some of iOS security features and could load unsigned binarys (read: it could then run pirated apps).
This order of operations is incorrect, though the grandparent set you up a bit by saying "released on iOS". In order to install the f.lux app you would first need to be jailbroken, ie able to run pirated apps.
Not true, f.lux released a version of their app in the App Store. Apple pulled their app and so they added another method to sideload it https://justgetflux.com/sideload/ using xcode. Apple then revoked their development license which broke that method as well. It's always been available as a jailbreak tweak but it's also been available to the general, non-jailbroken public
I don't think you understand how Apple works. They love to promote proprietary software in their "walled garden".
Apple's concern was that f.lux changes the color of the screen outside the app, and that fact alone goes directly against Apple's philosophy of keeping apps in their own respective sandboxes. Only Apple is allowed to change UI outside of an app. Consistency at all costs.
I think you don't understand what the comment was implying. If it was open source anyone could build it using xcode and install it in their devices themselves.
