801–810 of 837 posts
Please tell me it is more stable than Catalina. I have to reboot my machine every day or two just to keep it going.
Obviously, I'm one person out of many, but a quick Google search indicates that I'm probably not the only one that felt stupid updating today.
PSA: Big Sur forgets where apps' windows are when plugging back into an external display https://developer.apple.com/forums/thread/651131?answerId=64... https://www.reddit.com/r/apple/comments/jt0gjk/big_sur_forge... I've been on the public beta of Big Sur for months (and issued Feedback Assistant bug reports on this). As of 11.0.1, there's still a dealbreaker bug for people who use external monitors. If you unplug a…
Earlier quoted context omitted.
Or they just don't own a Mac and have mixed results with virtualization. Maybe instead of blaming them recognize that Safari is extremely inaccessible software for most people
That is so obvious! But For those of us who has a Mac we dont think about these issues as we can test Chrome and Firefox. How are Windows Dev suppose to test with Safari when they dont have access to it?
I feel like I traded my "MacBook Pro (13-inch, 2017) 16GB RAM 3.1 GHz Dual-Core Intel Core i5" for one 3 years older.
"Use font smoothing when available" is no longer available in System Preferences / General. Text looks blurry and kinda bold on my 27" 2560x1440 screen. Especially in Safari. Anyone has a magic command line?
Haven't tried it on Big Sur, but maybe `defaults write NSGlobalDomain AppleFontSmoothing -int 1` does the trick?
defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO
Yea, logic is inverted here.
Just want to put here that if you're using a Mac and haven't tried Safari recently, you're missing out. A few things: - Battery life is fantastic compared to Chrome/FF - Privacy seems to be top-notch - The tab ordering situation is now chrome-like (my biggest gripe in older versions of safari) - Experimental features are 1 click away, easily enable/disable WebGL2 - Support for the WebExtensions standard means addons…
This is a joke when your telemetry is sent unencrypted over the wire with no way to disable the same. Right now, Windows beats MacOS for privacy. At-least you can disable stuff on Windows with some effort.
Earlier quoted context omitted.
why would a mac with an intel processor need OS binary code for an arm processor? Remember that all of the resources—images, text, icons, etc.—are shared between the Intel and ARM binaries. There are a few use cases: • For troubleshooting, you can have one external hard drive/SSD that can boot both Intel and M1 Macs. This is very handy; this was pretty common back in the PowerPC to Intel days. • Same thing with runni…
- Yes it makes sense that apple might make such a boot tool that has both versions on it. I don't think it helps anything to have m1 macOS binaries on my intel mbp. - again, yes it would make sense to have this if you're booting from an external drive. Should be optional to have both binaries though. - yes, the apps themselves will have binaries for both. That makes sense to me since you want one download link for an…
Drives were much smaller and slower back then; getting rid of a few megabytes of unused across a bunch of apps could make a difference then.
The first Intel Mac mini in 2006 [1] started with a 60GB, 5400 RPM hard drive, so yeah optimizing space was a big deal back then.
There will come a time when macOS will only be updated for M1 Macs and there won't be a need to ship Intel code any longer. But that's at least 3-4 years away.
[1]: https://everymac.com/systems/apple/mac_mini/specs/mac_mini_c...
Twice bitten, thrice shy. Every MacOS upgrade for the past 5+ years has been a bag of hurt: regressions in functionality and stability, annoying "features" like Notification Center and Catalina warning nags, various PITAs on fixing UNIX/dev toolchains, all for little to no benefit. I've stopped upgrading all my machines (other than security updates), unless forced by a mission-critical app or a new machine.
Earlier quoted context omitted.
> Safari is extremely inaccessible software for most people How the hell is it "extremely inaccessible" for "most" people? It's Chrome that has an weirdass non-standard UI (the practice of showing app preferences/dialogs in a webpage needs to burn in the flames of Hades) and other niggles, not to mention being a privacy black hole. If they weren't told to use Chrome (i.e. Google didn't nag people to use Chrome when t…
> How the hell is it "extremely inaccessible" for "most" people? Because most people don't own Macs. The last Windows compatible version of Safari was back in 2012 or so, and as far as I know, it was never available on Linux. Therefore, for me to test on Safari, I either have to spend thousands to buy a laptop, or pay out of my pocket for some sort of cross-browser testing tool (even if it's free, I am spending extra…
That's precisely the 'lazy web developer' that they're talking about. Oh god no, you have to test on a browser you don't use.
Sure Chrome is dominant, but Safari has about 15% of the market so by taking the stance you do, you're dismissing 1 of 6 people. Because you're lazy.
Earlier quoted context omitted.
> Safari is extremely inaccessible software for most people How the hell is it "extremely inaccessible" for "most" people? It's Chrome that has an weirdass non-standard UI (the practice of showing app preferences/dialogs in a webpage needs to burn in the flames of Hades) and other niggles, not to mention being a privacy black hole. If they weren't told to use Chrome (i.e. Google didn't nag people to use Chrome when t…
It’s inaccessible in the sense that most devs don’t have Macs
I don't have a Windows machine. I still test against Edge. No Android phone. Still test against a range of them. How? See above.