Live data from Hacker News

macOS Big Sur

apple.com

281–290 of 837 posts

Re: macOS Big Sur

#281

Running iOS apps on the M1 Macs feels like such a game changer. Literally too cause a lot of games have been ported to iOS and now you can easily run them on Macs that were not possible before (Final Fantasy franchise for example). People can now play PUBG (although the mobile version but still). Fortnite (which have been removed but if you have downloaded it before you can still play it). And so many other games. I…

I wonder if any game (or other) developers are going to have major heartburn over this. "Woah, pricing/releasing this game this way was part of our mobile strategy, not our desktop strategy - how dare you run that game on a computer!" I know not all iOS apps target all devices - some are iPad only, etc. Is Apple allowing developers to arbitrarily prevent their apps from running on Macs? Can an app tell it's running o…

You can opt out of them being available on the Mac.

“All iPhone apps and iPad apps that run on Apple silicon Macs will be published automatically on the Mac App Store, unless you edit their availability. Edit Availability | Learn More”

Re: macOS Big Sur

#282
post #101

Earlier quoted context omitted.

You're not going to find the same AdBlockers that Chrome/FF have, but you will find AdBlockers that _work_. I agree that ads make the web unusable, but I've been content with the various blockers I've tried on Safari, and there's more every day. I use ABP, but 1Blocker and Wipr look good, and Safari's got the first 30% of privacy/adblocking taken care of with their various privacy and reader features.

1Blocker is a rip off. Wipr doesn't work properly. ABP lets a lot of ads through. There is nothing that approaches uBlock at all.

Wipr works outstanding for me on both iOS and macOS.

Re: macOS Big Sur

#283
post #222
post #166

Earlier quoted context omitted.

> - Actually decent dev tools (used to be terrible) As a daily user of Safari, I can't let you say that. The devtools suck. The network tools suck (why is it so hard to find the request payload??), the elements tools suck, there are basically no extensions (React, Redux, etc.). They are just horrible. As much as I try to use only Safari, I still fallback on Firefox Dev when I need some real devtools. I use it for the…

I'll second the text selection (on Catalina, but the new safari). Not sure how they messed up so badly on that. Also, safari on my iPad sucks as well, but got better with the 14.2 update. EDIT: Screenshot here of Apple's Big Sur page NOT rendering! https://imgur.com/a/tF4TDPH

Screenshot of the sidebar of GitHub rendering only partially: https://i.imgur.com/Fa370r2.png (I hid the center feed myself, but the left sidebar is blank)

Re: macOS Big Sur

#284

Earlier quoted context omitted.

Some people use tabs the same way others use bookmarks My wife does this on her phone. I find it maddening, and tell her to just bookmark her sites. But that's just not how her brain works. Fortunately, even between iOS updates, Safari remembers all of her old tabs.

Maybe this should be formalized, like automatically get open tabs into easily searchable persistent storage, whether they are called Bookmarks or not. Then they can be closed by prompting to "clean up". Maybe even skip that manual step entirely. People use browser histories like emails now -- by searching, not by active organizing.

I was about to say, you just described browser history!

Re: macOS Big Sur

#285

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.

Same here. I eventually upgraded to a Linux distro and couldn't be happier.

What finally did it for me was when I did an "ls" in a terminal after an upgrade, accidentally hit the wrong button when the OS asked for permission, and locked my terminal out of file system access. Mac OS is no longer any good for professional use, outside of media creation.

Re: macOS Big Sur

#286
post #112
post #8

Any updates to the firmware or drivers for bluetooth? My 2017 Mac has had many issues with bluetooth consistency. Keep on hoping they will announce performance improvements.

I doubt they'll ever update firmware on these older models :(

Given [1] I really hope they do.

[1] https://github.com/seemoo-lab/internalblue

Re: macOS Big Sur

#287

I hope they provided with this update a way to examine the Others category that usually takes up so much space in our Mac devices. I've emptied my documents, removed as much possible clutter I can see and still, that Others space is taking 60% of my storage.

._DS_Store folders take up a huge amount of space.

Re: macOS Big Sur

#288

Man I still haven't even left Mojave for Catalina. I don't think I'm gonna be changing OSs until I buy a second or third generation ARM Air that comes with whatever they're calling the 2022 Mac OS.

> whatever they're calling the 2022 Mac OS.

My money's on "Sequoia".

Re: macOS Big Sur

#289
post #221

I’m on Mojave still, are you able to move or hide the FaceTime dialog that appears in the upper right when making or answering a FaceTime audio call so it doesn’t block whatever is behind it such as the taskbar ?

How has Apple not fixed this? Looks super easy.

Re: macOS Big Sur

#290

> “Big Sur has been engineered, down to its core, to take full advantage of all the power of the M1 chip” Does that mean that all of the OS code has been recompiled for Apple Silicon / ARM? And if so, does that mean Big Sur has two binaries: 1 for ARM (new M1 Macs) and 1 for Intel (existing supported Mac devices) and there is a flag at boot-time to determine which mode it runs in?

> all OS code recompiled for Apple Silicon / ARM?

Yes, of course.

> two binaries

Yes and no. Technically, they are single binaries. The Mach-O binary format has supported the concept of a "fat binary" at least since NeXTStep was ported to Intel. So it's a single file, a single "binary", but with different sections for different architectures. Kernel selects the right bits of the binary to executer when loading.

> flag at boot-time

Nope. On an ARM Mac, ARM code will run natively, Intel code will run via Rosetta. On an Intel code, Intel code runs natively and ARM code does not run. This is done transparently for each binary.

Post reply on HN