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

831–837 of 837 posts

Re: macOS Big Sur

#831

Post by GnarfGnarf »

lukifer wrote: post #545
GnarfGnarf wrote: post #423

Earlier quoted context omitted.

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.

True, that's an option; but there's been nothing in new releases that justifies going through the effort (for my own n=1, anyway). It's not that the new releases are awful; they're just a hassle that fail a cost-benefit analysis.

I take your point. I don't have a choice, I have to confirm my app runs on the latest version because some of my customers will be going there :o)

Re: macOS Big Sur

#832

Post by ideologysec »

jlokier wrote: post #584
tobr wrote: post #552

Earlier quoted context omitted.

I would propose that the issue is that browser history navigation is generally poorly designed, at least if you want to do something more sophisticated than hit “back” or search it as a set of URLs. It should be richer and store much more details about each entry.

I'm not sure how to improve history navigation to help with this, as the browser doesn't know which 1 in 20 history entries are worth finding again, and which are junk traversed on the way to something worth finding. It can't figure it out from content search, because the junk is often the stuff that resulted from useful searches and was assessed by the user as not worth keeping. Keeping tabs is a signal from the use…

Something like this, evolved, perhaps?

https://getmemex.com/

Re: macOS Big Sur

#833

Post by macjohnmcc »

Tepix wrote: post #715
macjohnmcc wrote: post #647

My Early 2013 MacBook Pro 15 just old enough to not get this update.

Once your Apple Silicon Mac is too old to receive an update, you can't just install anything else on it because it's boot process is completely locked down.

At least once I feel that the MacOs version on my MBP is too old to risk putting it online I can just replace the OS with Windows 10 and get a few more years out of it.

Re: macOS Big Sur

#834

Post by wffurr »

modeless wrote: post #316
wffurr wrote: post #164

Earlier quoted context omitted.

That's great that it's fast, but do they have WebGL 2 support on by default yet? Six years and counting on the WebKit bug: https://bugs.webkit.org/show_bug.cgi?id=126404 WebGL 2 is required for MSAA-enabled offscreen framebuffers among other features that aren't available in WebGL 1 as extensions.

Almost! WebGL 2 is now enabled by default in Safari Technology Preview, as of September. Please give it a try now before it goes out in a Safari release and file bugs if you see any issues.

I just tried it out with the rendering engine used on keep.google.com for drawing notes (among others) and it works flawlessly with WebGL 2.

Thanks for the hard work!

Looking forward to it rolling out on by default in Safari.

Re: macOS Big Sur

#835

Post by sweetlucipher »

om2 wrote: post #617
sweetlucipher wrote: post #483

Earlier quoted context omitted.

The latest Safari breaks many of the WebGL demos on Shadertoy where Chrome has zero issues. I haven't investigated the reason but that could affect more than just games. TensorflowJS relies on WebGL backend for heavy model weight lifting (lots of puns)

Could you share which specific ones? In Safari 14 we changed our WebGL to be fully based on ANGLE, and that fixed more compact issues than it caused, but there may still be some bug tail which we are trying to clean up in updates.

Sorry for the very late reply. Contrary to the other response which I find baffling, it’s not a WebGL2 vs WebGL1 issue. Safari 14 on Catalina was able to render 4 out of the 6 shader demos on the Shadertoy homepage on a MacBook Pro 16 2020 with AMD Radeon 5600. Chrome was able to render all. Obviously, if it was a case of WebGL version support either all would run or none would run depending on the supported version. That comment really made no sense.

Anyway, I had to return the MBP 16 as I wasn’t happy with it’s performance when the browser has to deal with multiple GPU contexts. I’m waiting for an M1 laptop and it won’t arrive till next month.

My old MBP 15 does not have Catalina so it doesn’t have the latest Safari.

Hope that helps.

Re: macOS Big Sur

#836

Post by kjakm »

catach wrote: post #640
kjakm wrote: post #521

Earlier quoted context omitted.

> I think the problem is that people generally don’t know when they’ll return to a tab, so they leave it open, and that creating a bookmark is asking too much commitment for something potentially ephemeral. Safari's reading list is my solution to this. CMD+SHIFT+D adds the current tab to the reading list which is visible on a new tab page or in a side panel. Syncs across devices too. You just right click > delete to…

As someone who doesn't use Safari this just sounds like a secondary Bookmark list.

Kind of but I think the implementation matters. I use this and bookmarks in very different ways. I can also add to it from the iOS share sheet so add links I see on the web/social media that I want to read later.

Re: macOS Big Sur

#837

Post by geoelectric »

saagarjha wrote: post #683
bartvk wrote: post #679

Earlier quoted context omitted.

It's been like that for ages, isn't that typical macOS behavior? Note that I hate that behavior as well :) I fixed it first with a hotkey and a little Lua hacking within Hammerspoon. Now I just use Amethyst.

Yes, it is. I think most people hate it ;)

I tested it on a few apps before I posted (and after you replied) and it looks app-specific.

Finder actually fills the screen (the Apple app I did originally test since it used to represent reference windowing behavior) but only in list mode, which happened to be my default. In icon mode it does the old school top-to-bottom thing, as I found out after the replies.

But Chrome fills the screen, OmniFocus fills, Keyboard Maestro's editor fills, Firefox fills, etc. I think a lot of third party apps will fill the screen since it seems to come down to whether the dev gives it a different aspect ratio than native to "show all content." Most stuff seems not to do so anymore, presumably because that behavior is weird.

But to your point, apparently Safari was a huge oversight on my part and it's definitely not as consistent as I thought it was. Sorry if I got hopes up.

That said, to the extent an app will do that at all, opt-click-max or title bar double-click is the way to do it. Otherwise you're stuck with one of the screen snap apps that can also redefine the buttons for you.

Post reply on HN