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

601–610 of 837 posts

Re: macOS Big Sur

#601

Post by Osiris »

mokus wrote: post #587
ellis0n wrote: post #523

Earlier quoted context omitted.

Yes, the biggest surreal challenge of the 20th century is screen rotation and a second monitor, because that's not part of the original OS design. I am having similar problems while developing my phone operating system and one audio channel for multiple events in the same time like call ringtone, alarm clock, speakerphone, recorder. Every early version of android / ios did not work properly with sound and it took yea…

I’m not sure exactly what you mean so maybe I’m missing the point, but pre-NeXT Mac software handled multiple monitors back in at least the early 90’s, maybe even the 80’s. A friend of mine had 4 displays on his Power Mac 8600 for example. I wouldn’t call this a new challenge (for Apple at least), but rather a disappointing regression.

My IBM 8088 had dual monitors (1 graphics card per display, monochrome and EGA).

Re: macOS Big Sur

#602

Post by thewebcount »

FullyFunctional wrote: post #342
egypturnash wrote: post #209

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.

32-bit apps. I have 32-bit apps where the developer is either gone or will not update, thus if I wish to keep using these I have to stay on Mojava. This applies to four Macs which will likely never move away from Mojava.

For what it's worth, it's pretty easy to have a separate Mojave partition that you boot to when you need to use one particular app. That's what I do.

Re: macOS Big Sur

#603

Post by dmitshur »

I’m quite sad about the decrease in information density in the UI. :/

My preference is to able to fit many apps side by side, and bigger fonts and spacing between elements (e.g., in the menu bar) goes against that goal.

I haven’t actually tried it yet so I could be mistaken or get used to it. However, I’ve experienced this before when going from Windows XP to Vista or 7. That change in information density made my 2560x1600 screen worse at fitting many windows without overlapping.

I’m curious how others feel about this topic.

Re: macOS Big Sur

#604

Post by Osiris »

elcritch wrote: post #566
lexusgx wrote: post #456

Earlier quoted context omitted.

>Catalina warning nags I appreciate those nags. Those nags clued me into app behavior; I learned what apps are requesting keyboard access even when they're not in focus, for instance. Blindly trusting our apps to access our keyboards and not gradually become keyloggers is a recurring problem in our industry, it seems, so that was a very welcome change.

The nags for regular apps don’t bother me too much, but the fact that I still can’t figure out how to run GDB worries me. The old CLI overrides don’t work in Catalina anymore. I’ve only ever owned Mac laptops and I’m seriously considering switching to a Linux/arm on the next laptop. I’m fine with the lack of ability to run random apps on my iPad, but not on my computer. Big Sur apparently won’t let me run the ZFS ext…

I switched to Linux after the TouchBar was introduced. I've been using it for work exclusively for 3 years. It crashes, hangs, and generally acts weird every day. It's not always greener on the other side.

The upside is 1) total customization, 2) if there is a problem you have a lot more power to fix it. There are just a lot more problems.

Here's a list of my daily Linux issues (NVIDIA driver required to use external monitors)

1. Resume from sleep causes browsers and electron apps to fail to draw anything. I have to close and restart them. I found a workaround for Chrome (turn on Vulkan) but that's not possible for Slack.

2. Periodically Linux reports I have no internal speakers and I have to kick pulseaudio

3. NVIDIA driver page faults several times a day requiring me to unplug, replug monitors and run xrandr to reconfigure the displays.

4. After an upgrade my system now boots to TTY and I can't figure out how to fix it.

5. Zoom annotations don't work

6. Discord audio didn't work until I found an obscure workaround.

7. External monitor detection doesn't work

8. The laptop display doesn't go into power saving mode ever

9. Usb devices have to be unplugged/replugged to be detected

10. Complete system crashes (hang with no recognition of any input, so no way to switch to TTY)

So, pros and cons.

edit: I should note that the last Macbook (2017 I think) would kernel panic randomly when connecting or disconnecting external monitors (like when going to a meeting).

Re: macOS Big Sur

#605

Post by [deleted] »

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…

[deleted]

Re: macOS Big Sur

#606

Post by zepto »

shangxiao wrote: post #371
greedo wrote: post #346

Earlier quoted context omitted.

Any "professional" who can't spend two minutes googling how to reset this doesn't deserve the title.

"Professional use" just means to use in your profession, not that they are claiming to be an IT expert.

In this case, it means they are typing Unix commands into a shell. That suggests that their profession involves IT.

Re: macOS Big Sur

#607

Post by om2 »

djxfade wrote: post #558
mmastrac wrote: post #417

Earlier quoted context omitted.

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.

They never split from Chrome. Chrome forked WebKit into Blink because Apple's wasn't merging Google's patches

There were many reasons for the split, but as far as I know this was not one of them. There was no patch backlog, and there were many reviewers on the Chrome team. I think it was a combo of desire for control and debates over various architectural approaches.

Re: macOS Big Sur

#608

Post by zoid_ »

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…

As far as I can see, there is literally no way to disable network caching via a toggle in the dev tools. This is a huge problem for me.

Re: macOS Big Sur

#609

Post by alacombe »

tuxone wrote: post #438
gnachman wrote: post #347

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

Being so responsive to macOS updates adds value to an already superb and essential tool. I just donated and added to my things to support list.

What ? Who would ever think they need to update their app to support NEWER OS ? Or are newer generations completely oblivious to the fundamental concept of backward compatibility ?

Re: macOS Big Sur

#610

Post by Shank »

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…

> - Support for the WebExtensions standard means addons are trickling back into the ecosystem - I'm happy with my AdBlocker and Nightmode extensions

The critical functionality required for uBlock Origin and other request-based ad-blockers is blocking using the WebRequest API, which isn't supported in WebExtensions in Safari [0].

[0]: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web... [0]: https://github.com/mdn/browser-compat-data/blob/master/webex...

Post reply on HN