Live data from Hacker News

macOS Big Sur

apple.com

821–830 of 837 posts

Re: macOS Big Sur

#821

Earlier quoted context omitted.

more than that. They reiterated that they will continue to sell Intel Macs for the next few years. I reckon we'll get another decade at least

Did they say that? I would be surprised if they released more Intel Macs.

in an interview with TheTechChap on YouTube, they said they intend to create more Intel devices for the coming years

Re: macOS Big Sur

#822
post #326
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 ?

Yes, that's now draggable.

Thanks for this. After the whole phone home saga of this week I think this is now down the bottom of my list of concerns.

Re: macOS Big Sur

#823
post #668

Earlier quoted context omitted.

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

"Therefore, for me to test on Safari, I either have to... pay out of my pocket for some sort of cross-browser testing tool (even if it's free, I am spending extra time)" 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 peo…

Supporting 85% of the market is basically free - because you already have a PC, and all browsers can be installed on that, except for Safari. But supporting the remaining 15% requires paying several hundred dollars for hardware that you don't really need for any other purpose. I don't think that refusing to do the latter is a case of "lazy".

Re: macOS Big Sur

#824
post #306
post #159

Earlier quoted context omitted.

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…

"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." Everyone has a story like this - from all of the browsers. It seems like FF behaves better in this way now, but I still do silly things like rsync my home directory…

I do have a story like this for all the browsers, save one: Opera, from back when it had its own rendering engine. It's not that it never crashed, mind you - but, somehow, the tabs would always be back after. Makes me wonder just how much effort wend into the error shutdown code path to make sure everything is saved.

Re: macOS Big Sur

#825

Earlier quoted context omitted.

Even then, you can sync open tabs with Firefox Sync! (Or Chrome sync, or Safari via iCloud)

Yes, though I find I want far fewer tabs on Mobile than I do on Desktop.

Tab sync usually doesn't maintain the same list of tabs on all devices like that - it just lets you see what you had opened elsewhere, and easily re-open it. My desktop and mobile browsing sessions are very different, as well - but I "move" tabs across devices all the time to continue some research etc.

Re: macOS Big Sur

#826
post #805
post #759

Earlier quoted context omitted.

Haven't tried it on Big Sur, but maybe `defaults write NSGlobalDomain AppleFontSmoothing -int 1` does the trick?

Thats what did the trick, its hard to say for sure: defaults write -g CGFontRenderingFontSmoothingDisabled -bool NO Yea, logic is inverted here.

That was wrong one. This looks better:

defaults -currentHost write -g AppleFontSmoothing -int 0

Re: macOS Big Sur

#827

Earlier quoted context omitted.

The only reason I'm using FF is TreeStyleTab. I seriously don't understand how people live without it. Right now I have 993 open tabs, sometimes I have 100, sometimes 2k - don't really care, but they are easily navigatable as a tree-like structure on the side of the screen.

Genuine question because our tab handling strategies seem to differ - how frequently do you return to a given tab? Do you keep them for reference in some way, or is it more out of concern of having to navigate back over again?

- First, bookmarks - if you bookmark something and close the tab, the bookmark stays there forver. If you bookmark something that you know you won't need later (e.g. after you finish researching something), then it adds a mental burden of having to clean it up later. When a lot of them accumulate, it's really hard to recall why exactly they were added in the first place and whether each one of them should be now removed or not.

- Open tabs are the opposite - if you close them, they're gone forever. So once you no longer need a certain tree of tabs (e.g., like above, you've finished researching something), you just dispose of the whole tree; if there's anything particularly valuable in there, you can add it to bookmarks.

So, e.g. if I'm doing house renovation I may have trees of tabs with hundreds of open tabs in them while researching something. Same when coding, if I'm investigating a particular topic I may have tons of open tabs that will eventually get closed all together.

In some rare cases, I keep a tab or a tree of tabs open just so I don't forget to navigate back to it in the foreseeable future (at which point it will likely get closed).

Re: macOS Big Sur

#828

Earlier quoted context omitted.

Out of curiosity, what apps are those?

Of the top of my head: - software for a "smart pen" where the company went out of business - some label printing software - some Steam games - some games from GOG Even if I don't run these daily, I don't like to be cut off from my past.

Ah. I forgot there are so many games still only built for 32bit. Is there any kind of workaround using qemu?

Re: macOS Big Sur

#829
post #668

Earlier quoted context omitted.

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

"Therefore, for me to test on Safari, I either have to... pay out of my pocket for some sort of cross-browser testing tool (even if it's free, I am spending extra time)" 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 peo…

[deleted]

Re: macOS Big Sur

#830

Earlier quoted context omitted.

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)

Wont use Chrome because of the Google services. But given Edge is Chromium, they're benefiting from that development.
Post reply on HN