Live data from Hacker News

OS X is now macOS and gets support for Siri, auto unlock

techcrunch.com

431–440 of 578 posts

Re: OS X is now macOS and gets support for Siri, auto unlock

#431
post #409
post #272

Earlier quoted context omitted.

Apple lists a few limitations for APFS, one being: "Filenames are currently case-sensitive only." My thought: hey, that is a feature!

HFS+ can be configured to be both case-sensitive and not (the default). So in that sense it's a regression.

As I seem to remember running in case sensitive mode broke tons and tons of apps that made assumptions based on the history of HFS+ being case insensitive.

I'd be very interested to know if they run case-sensitive by default are not in the final release.

Re: OS X is now macOS and gets support for Siri, auto unlock

#432

Will this make the OS suck less? Seriously, at least for my use case, and in my opinion, OS X has been on a downward trend for a while (since 10.6). They need to fix the bugs, and get back to a nice stable OS that "just works." That's all I'm interested in.

I had kept my Macs at 10.6 for a long time but had to "upgrade" one of them to help my daughter with an iPhone problem (really annoying that you have to update your Mac just to copy files to a phone, but whatever). Everything was worse. Search was terrible. Mail was in the crapper. The weirdest shock was when I was using Apple apps and discovered they'd changed Shift-Command-S from "Save As" to "Duplicate." That move…

> Shift-Command-S

Basically at this point I'm recommending everyone to forget about iWorks apps (even though I brought a few people onto them earlier). I'm still holding on to Keynote even though the version compatibility issues are absolutely horrible, but it still produces the best presentations with the least effort, so I'm biting that bullet. To everyone else who's still using the old Keynote: Don't even think about trying out the redesigned one, nothing will be compatible anymore, just stick with it as long as you can!.

Meanwhile Google Docs impress me more and more.

Re: OS X is now macOS and gets support for Siri, auto unlock

#433
post #325
post #22

Earlier quoted context omitted.

https://github.com/Homebrew/homebrew-dupes is your friend.

Does anyone know if this is a bad idea? Like do any of the system provided utilities do anything special in OS X that will be broken if they are replaced? I'd like to do install these replacements, but am concerned about possible side effects.

By default, it will append a "g" to all the coreutils at least, like ls -> gls, sed -> gsed, etc. And things that are already default on OS X, like curl, perl etc, will not be symlinked into /usr/local unless you force it.

But personally, I changed my coreutils over a year ago to the GNU ones (via symlinks), and I force link every single package, I've never had a single issue.

Though our use cases may be different, and you may have issues. In which case you can just `brew unlink $package`.

Re: OS X is now macOS and gets support for Siri, auto unlock

#434

Earlier quoted context omitted.

Nothing. Apple is just being overly paranoid or hoping to some day do things that GPLv3 won't allow them to do. Microsoft, Facebook, Google, Intel, IBM; all of these companies have some interaction with GPLv3, but Apple staunchly refuses to even touch it. It's a real pity, because Apple's popularity is sending some message that GPLv3 is poisonous, when it reality it's only a problem for them because they chose to mak…

> because Apple's popularity is sending some message that GPLv3 is poisonous Doesn't Linus' refusal of GPL3 damage its reputation much greater than Apple?

The Linux devs publicly denounced an early draft of GPLv3 and never reconsidered the question. Yeah, I think they just didn't feel like trying to understand it, and Linus's own anti-FSF attitude spreads to his followers.

Re: OS X is now macOS and gets support for Siri, auto unlock

#435
post #333
post #119

Earlier quoted context omitted.

> Copy/paste across iPhone and Mac is very useful. I don't use a Mac or an iPhone, but I applaud this sort of device harmony. That said, I am worried that it would unnecessarily leverage the cloud. My guess is that instead of the two devices directly communicating with one another—that is, instead of leveraging the fact that they are probably on the same local network and should just work in concert—the clipboard dat…

This enables an interesting new kind of attack. 1. Attach an attack device to someone’s account. 2. ‘Poll’ the clipboard by pasting every ~5 seconds. 3. If the contents of the clipboard appear to be ‘secure’ (looks like shellcode, bitcoin address, url, etc), quickly replace the contents with an attack string with same datatype. If you have an untrusted device attached to your Apple account, your local clipboard can n…

Indeed, WHATWG is currently considering [1] a related scenario where rogue websites with access to the clipboard will inject formats with dodgy payload to exploit flaws in some app if the user pastes.

[1] https://github.com/whatwg/html/issues/1244

Re: OS X is now macOS and gets support for Siri, auto unlock

#436
post #54

This is all shockingly "meh."

Half the people here are complaining about too many new features and not enough stability, and the other half are complaining that there aren't enough new features. This is why Apple doesn't listen to consumers and instead just puts out whatever they want to.

It's not about quantity, but quality. People are complaining because these new features are (mostly) unsubstantial gimmicks.

Re: OS X is now macOS and gets support for Siri, auto unlock

#437

Earlier quoted context omitted.

> As someone who does not use or want Apple's mobile devices My guess is that most of Mac users do want/use Apple mobile devices, and that in fact the majority of their computing time is now on those devices so it makes sense that the team would focus heavily on the interface and overlap between iOS / MacOS.

"My guess is that most of Mac users do want/use Apple mobile device" That's what it is... a guess. Unless you can produce some data to back it up. There's a huge community (especially outside of US) who use Macs for day-to-day work but use android mobile devices as that's the most sensible choice for a majority of the world.

Yep. Macbook + Android here.

Re: OS X is now macOS and gets support for Siri, auto unlock

#438
post #390

Earlier quoted context omitted.

You could say that macOS was responsible for a good amount of the iOS revenue, insofar as 1. devs using Macs are a lot more likely to spontaneously decide to try developing iOS apps, and 2. having more iOS apps sells more iOS devices. If Apple only sold iOS devices and you had to develop for them from e.g. Windows, I don't think the app ecosystem would have been nearly as large—making getting one a rather less attrac…

I got my first mac product (mbp) a few months ago, I've dabbled in OSX development but still feel guilty for not trying iOS dev yet, despite not even owning an iPhone.

You honestly don't even need an iPhone until serious testing seeing as the Xcode simulators are amazingly functional.

Re: OS X is now macOS and gets support for Siri, auto unlock

#439

Earlier quoted context omitted.

Some features are not intended to maximize penetration; they are differentiators for their platform. Super Mario has a real future and you can only get it on Nintendo.

Right, but we are talking about a communication platform which inherently should be crossplatform

"Should be" does not equate to "no future"

Re: OS X is now macOS and gets support for Siri, auto unlock

#440
post #113
post #105

Earlier quoted context omitted.

I would settle for fixing the bug where I have to restart Finder to rebuild the connection every time my NAS drive spins down. Also the combination of screensharing to a headless MacMini and then AirPlaying to an Apple TV produces some fairly loathsome results.

How about the bug where you need to force quit coreaudiod to restore sound to the speakers after resuming from sleep?

Funny I have the opposite. I often need to induce a sleep/wake cycle to restore detection of external speakers. Killing coreaudiod does not fix it, but a restart or (I recently learned) sleep/wake does.
Post reply on HN