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

macOS Sequoia is available today

apple.com

Post reply on HN
Print view View original

571–580 of 643 posts

Re: macOS Sequoia is available today

#571

Post by tpmoney »

IshKebab wrote: post #541
adastra22 wrote: post #529

Earlier quoted context omitted.

That is not at all obvious.

It's very obvious if you're paying attention. What is the security benefit of removing the command-click shortcut?

One argument in favor of removing it (not saying it’s the reason or that they didn’t have other options) is that ctrl-click and open did not obviously do anything different. That is, whether you ctrl-click and open a signed app or an unsigned app, the command in the menu was just “open”, with no indication that you were overriding a security policy. Then the dialog it popped up wasn’t particularly distinct from the “first time run” dialog. There is an argument to be made that going to the security settings and specifically allowing an app is a more clear expression of intent. Kind of in the same way you probably want to open a file you download from the web, but good security practices means the browser doesn’t open it for you on download, you need to explicitly go do it.

That said there’s no reason they couldn’t have fixed either of those issues instead

Re: macOS Sequoia is available today

#572

Post by mdaniel »

int_19h wrote: post #505
mdaniel wrote: post #440

Earlier quoted context omitted.

I can't know what "-dirty" implies, but https://github.com/jqlang/jq/commit/cff5336 is a pretty random commit from 2022 :-( https://github.com/apple-oss-distributions/distribution-macO... hasn't been updated with a "jq" directory yet

"dirty" usually means that the commit doesn't correspond to any specific version tag in the repo (or whatever other mechanism is used to map commits to versions).

Incorrect: https://git-scm.com/docs/git-describe#Documentation/git-desc...

> If the working tree has local modification "-dirty" is appended to it.

and one can see their invocation of --dirty here: https://github.com/jqlang/jq/blob/cff5336ec71b6fee396a95bb0e...

Re: macOS Sequoia is available today

#573

Post by seec »

api wrote: post #551
ac29 wrote: post #421

Earlier quoted context omitted.

Mac isnt even 10% of their revenue, and my guess is developers on Mac are maybe a percent or two at most.

Microsoft figured out long ago that having developers use your platform is a small direct source of revenue but a massive indirect one, not to mention the thing that keeps your platform relevant. Driving them off Mac would be a gigantic mistake that over time would lead to the fading of the whole Apple ecosystem.

Well yeah but you need someone that has some understanding of what he is actually selling to come to that realization, not the greedy bitch that is Tim Cook.

I think the mistake already happened, you can see fewer and fewer macOS only software and there is very little in the way of novelty/exclusivity (both iOS/macOS). Devs are now more and platform stuff more and more (mostly web technologies because it makes for good UI even though performance is not the best, it doesn't matter with today's powerful machines.

I'll add that one key point that Apple was better on is becoming very moot: software optimisation (performance and UI) matters a lot less in today's cheap powerful computing. Apple is supposedly selling top of the line hardware but skimping every way possible so in the end, when price matched, competitive hardware does not do worse no matter how bad the softwares are optimized on concurrent platform.

Re: macOS Sequoia is available today

#574

Post by tpmoney »

setopt wrote: post #549
agys wrote: post #500

Earlier quoted context omitted.

opt-cmd-v for move vs cmd-v for copy? Pretty usable imho!

If it worked like that in other Mac apps, I wouldn’t mind. Then you would just adjust to “this is how MacOS does cut-and-paste” and after an initial adjustment it would make complete sense. But in every other Mac app, even in TextEdit, you would Cmd-X to cut a piece of text and Cmd-V to then paste it somewhere else. The same logic is used to e.g. move an image within a note or email, which is also a file. So Finder i…

The finder probably chooses this paradigm because cut + paste is destructive. If you cut text and never paste it, the next time you copy out cut you lose that text forever. So if you used the same paradigm for files in the finder, you could accidentally and permanently delete a file because you cut it and then fat fingered copy instead of paste. If this happens with text from a file you can often just close the file and not save to get your text back, or hit undo because cut text is part of your undo history (usually). But storing whole files in some undo history seems like it could go wrong real quick since either you couldn’t actually delete the file from disk until the history expired or the finder was restarted, or an undo might take a significant amount of time because you moved between file systems. Or imagine if the destination file system crashed during transfer or unmounted after. Then you couldn’t undo at all.

Re: macOS Sequoia is available today

#575

Post by nailer »

semiquaver wrote: post #429
nailer wrote: post #335

Earlier quoted context omitted.

Is there some way to get things like strace working? Recently it's got weird and strange with the OS protecting me from myself. Or content makers from me breaking their DRM. Or something. Some app tries to open a file and fails. Doesn't tell me what the file name is. I just want to see the open() call.

Presumably you mean dtrace? strace is a Linux thing. dtrace should still work but you need to disable SIP first.

No I mean strace. There’s no need to learn D just to see syscalls.

Re: macOS Sequoia is available today

#577

Post by skrrtww »

dur-randir wrote: post #534
skrrtww wrote: post #299

Earlier quoted context omitted.

> Once you need to be in the apple developer program to build and run from source or something, that’ll be a legitimate nightmare. But we’re nowhere near that yet. This is the case for building and running things with restricted entitlements and system extensions. Unless you disable system integrity protection entirely, which locks you out of your purchased App Store software, DRM content, etc.

>which locks you out of your purchased App Store software, DRM content Also false. But Apple's glad you believe in that.

I was mistaken; I was conflating Permissive Security with SIP. Permissive Security does have those limitations.

Re: macOS Sequoia is available today

#578

Post by doodaddy »

user3939382 wrote: post #252
Hamuko wrote: post #219

Earlier quoted context omitted.

Apple locking down the OS even more by making Gatekeeper harder to bypass makes me want to skip this version for as long as possible. The screen recording permission thing also doesn't help since I'm using Ice ( https://github.com/jordanbaird/Ice ) because somehow Apple still can't Sherlock this feature.

The way it's even implemented now is like the nightmare realized from everything Richard Stallman warned about for decades. Especially for non-technical users, they've practically implemented a system where Apple decides what software you are and aren't allowed to run on your own computer. They can muddy the issue by claiming it's for safety/security but I don't buy it. They could have made the override still clear b…

I’m a fan of Stallman and his ideology toward computing as much as anyone but tend to think that the ship has sailed long ago. We are not living in a world where everyone who touches a computer has the knowledge or skill set to know a good idea from a bad one. Long-gone are the days when our passwords could be blank because the other guy using the system was also a kernel developer. And so unfortunately Stallman’s ideas are mostly a thing of computing utopia fiction.

It’s fine to let the experts worry about securing our systems. The Internet is safer for it. And it’s fine to not think so, too. But for those people, realize that the product may not be for you. That’s why we have a dozen flavors of Linux.

But maybe I’m just getting old.

Re: macOS Sequoia is available today

#579

Post by Hamuko »

adastra22 wrote: post #528
Hamuko wrote: post #482

Earlier quoted context omitted.

Homebrew defaults to downloading binaries.

Defaults to. You can tell it to compile yourself, if that matters to you. I don’t see what the issue is here. Why is it a problem that it defaults to binary distribution?

The biggest problem is that the defaulting to binary distribution also means that building from source is unsupported.

>Building from source takes a long time, is prone to failure, and is not supported.

Having issues building your Homebrew packages from source? Well, you better not take it to the bug tracker.

Re: macOS Sequoia is available today

#580

Post by mmmlinux »

__jonas wrote: post #347
frankjr wrote: post #259

Earlier quoted context omitted.

> The right-click/control-click option for easily opening unsigned apps is no longer available. Users who want to open unsigned software will now need to go the long way around to do it: first, try to launch the app and dismiss the dialog box telling you that it can't be opened. Then, open Settings, go to the Privacy & Security screen, scroll all the way to the bottom to get to the Security section, and click the Ope…

My god, I had no idea there was a shorter way than that, can't believe I'm finding this out just as they remove it, so annoying!

Yeah same. Ive been doing it the long way for years apparently.
Post reply on HN