Live data from Hacker News

macOS Big Sur

apple.com

411–420 of 837 posts

Re: macOS Big Sur

#411
post #301

Earlier quoted context omitted.

You can still only open about 15 tabs, after which the Safari tab bar turns into a completely unusable horizontally-scrolling list. Chrome solved this a decade ago... just keep shrinking the tabs down to Favicon size or smaller. Safari just added Favicon images last year, and I don't even think they're visible by default. --- EDIT: Favicon-only compact tabs to have actually been changed/added in Safari 14 for Big Sur…

My current tab bar on 10.15.7 with Safari 14, you don't even need to upgrade to Big Sur. Cmd + hover lets you preview a page or close it. https://i.imgur.com/NS6Zjd6.png

Cmd doesn't do anything. The preview shows up on hover after a second.

Re: macOS Big Sur

#412

I released iTerm2 version 3.4.0 this morning with Big Sur support. Please update because 3.3 has various issues with it.

Oh man, iTerm2 is the main reason i could switch to mac os from linux. Thanks for the great work.

Re: macOS Big Sur

#413
I've learned the hard way not to jump on new macOS versions. I've found it's safer to wait at least 6 months, if not one year.

Thank god I don't use Xcode or do iOS/Mac dev anymore.

Re: macOS Big Sur

#414
I use my machine for work, and although I am interested in this release, I cannot afford having downtime because any of my crucial apps could break. Will wait a few months.

Re: macOS Big Sur

#415
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.

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

Re: macOS Big Sur

#416
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.

Personally I'm usually looking through a bunch of responses trying to find the one I'm interested in, and that workflow sounds pretty awful.

Re: macOS Big Sur

#417
post #166

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…

> - 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…

Devtools on Safari have been a joke for 5 years now. Ever since they split from Chrome and went down the Xcode "fancy" route, I have not been able to accomplish anything debugging in that browser.

Re: macOS Big Sur

#418
post #305

Earlier quoted context omitted.

Either that or “Alcatraz”

They’ve had almost as many California places as they had big cats, so it might be time for a new theme soon.

The legendary crack marketing team better get on another drug-fueled minibus-driven vision quest!

Re: macOS Big Sur

#419

Earlier quoted context omitted.

that seems like more of an app level compromise. I'm guessing on the OS itself they don't include the unneeded binary data.

* I'm guessing on the OS itself they don't include the unneeded binary data.* The operating system can on both M1 and Intel Macs; therefore, the OS has binaries for both. Wouldn't be much of an operating system if the frameworks and APIs weren't available for applications regardless of which architecture they're running on.

[deleted]

Re: macOS Big Sur

#420
Every MacOS upgrade for the last few years has made my computer less stable and required me to reboot more often. So I'm going to hold off as long as I can.

Just this moment my laptop's keyboard and mouse took well over a minute to work after coming back from sleep. Twice in a row so time to reboot I guess.

Post reply on HN