Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

macOS Big Sur

apple.com

Post reply on HN
Print view View original

421–430 of 837 posts

Re: macOS Big Sur

#421

Post by aledthemathguy »

trevorishere wrote: post #80
jkelleyrtp wrote: post #18

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…

The lack of integration with other services is why I don't use it. I stick to MSFT Edge which also has improved battery life over Chrome.

are you saying edge on macos is better than chrome on macos? curious about how this is even possible, considering google has been at this (meaning - developing chrome for macos) for more than a decade (i think)

Re: macOS Big Sur

#423

Post by GnarfGnarf »

lukifer wrote: post #130

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.

Have you tried dual-booting the newest OS from an SD or USB memory card? Hold down the Option key at power on and it prompts you for boot device.

It runs a bit slower, but at least you can try it out.

Re: macOS Big Sur

#424

Post by SaulOfTheJungle »

ksec wrote: post #159
jkelleyrtp wrote: post #18

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…

It is great, but: 1. Just lost a few hundred Tabs from last session. Not the first time this has happened to me on Safari. ( Firefox used to have this problem as well, they implemented multiple LastSession.json to combat the problem and it is basically a thing of the past. ) 2. Fav Icons meant they are no longer showing the Tab Description once you have a dozen tabs as they will shrink to Icons Size. So you either ha…

I can confirm point 4.

I have a small, open-source Chrome/Firefox extension that has about 260 active users.

I was considering porting it to Safari, but I can't justify the $99/year fee for it.

Re: macOS Big Sur

#425

Post by hungrywolfinc »

kxcz wrote: 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.

Still wack. If my iPhone or iPad is between my mouse+keyboard and my 2019 mbp, Bluetooth shot to hell. Moving devices even a foot away helps dramatically though I still have to turn my mouse on and off every time I return from sleep. Happens with Logitech Mx, Matias keyboard, keychron mechanical keyboard. Maddening.

Re: macOS Big Sur

#426

Post by ianwalter »

lilyball wrote: post #379
thiht wrote: 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…

> The network tools suck (why is it so hard to find the request payload??) Speaking as a non-web-dev who looks at web inspector once in a blue moon, this took me about 5 seconds. I looked at the Network tab, selected a resource, noticed the information in the detail pane had headers but not payload, and then right-clicked the resource and selected "Reveal in Sources Tab" which revealed the payload there.

Isn't that the response payload and not the request payload?

Re: macOS Big Sur

#427

Post by sysashi »

I have not even upgraded to Catalina yet, fearing all the breaking stuff I've heard of on HN.

I'm just so frustrated about upgrade process, 90% of the time it won't work first time and will break my Windows partition in some way. Why can't it be like upgrading bunch of packages with `pacman -Syu`...

Re: macOS Big Sur

#428

Post by ianwalter »

usmannk wrote: post #415
lilyball wrote: post #379

Earlier quoted context omitted.

> The network tools suck (why is it so hard to find the request payload??) Speaking as a non-web-dev who looks at web inspector once in a blue moon, this took me about 5 seconds. I looked at the Network tab, selected a resource, noticed the information in the detail pane had headers but not payload, and then right-clicked the resource and selected "Reveal in Sources Tab" which revealed the payload there.

If I followed your instructions correctly, that's the response payload not the request.

Yes, which I think helps prove the parent's point!

Re: macOS Big Sur

#429

Post by andreasley »

makecheck wrote: post #311

Not a great download experience so far. It has already failed twice partway through (2nd time after 9.0 GB out of 12.0 GB). And since this is Apple, who has somehow never figured out how to implement resumable downloads, it just starts from scratch again.

Even worse, other stuff is breaking because Apple's infrastructure is on fire. Apps don't launch because signature checks are failing (ocsp.apple.com and crl.apple.com seem to be unreachable for me) and my Mac Pro hangs randomly for a few seconds every minute or so. It's quite ridiculous. :)

Re: macOS Big Sur

#430

Post by michaelwilson »

There is a problem with Drobo Devices connected via Thunderbolt and Mac OS Big Sur RC2 (and probably Big Sur Release). Their Customer Support page says:

"NOTE: Drobo Thunderbolt had been working properly up to RC2 posted on Nov. 11. If your Drobo has a USB port, use this. In the interim we are looking into the issue. "

My experience is a combination of kernel panics on startup, volumes not mounted, and not showing a filesystem in the Disk Utility. I was worried I'd lost all my data until I ran across this and was able to plug one device in via USB. Unfortunately, my Drobo 8D doesn't have a USB port, so I'll have to wait for a software solution.

Post reply on HN