Live data from Hacker News

Apple introduces macOS Mojave

apple.com

101–110 of 665 posts

Re: Apple introduces macOS Mojave

#104
post #33

Wow, they are DEPRECATING OpenGL from both macOS and iOS: https://developer.apple.com/macos/whats-new/ This is in addition to last year's announcement that "macOS High Sierra is the last version of macOS to run 32bit apps without compromise " I wonder if we will soon see a new lineage of Macbooks fitted with Apple-specific arm64 chips. The most scary thought is if UIKit-on-macOS starts requiring Developer ID entitlem…

I'm curious about this – does it really matter? How important is it that the Operating System has OpenGL? Can't individual apps just static link to (and ship) their own versions of OpenGL?

Re: Apple introduces macOS Mojave

#105

WWDC 2018, from underwhelming to boring. I will lose my mind if i hear *oji one more time. Will they ever stop with this nonsense? Favicons in Safari? It took them 6 years for the browser to remember the zoom setting per site, now we have the luxury of having favicons.

I deeply suspect that the lack of features is because the releases this year internally centered around responding to the negative buzz associated with iOS 11 problems. I remember when emojis were showcased at WWDC 2016, a fairly low-feature release. Whenever that happens the true feature is unannounced: it's simply stability.

"Whenever that happens the true feature is unannounced: it's simply stability."

Can't remember which version it was now, but I remember when Apple heavily marketed a Mac OS X version dedicated almost exclusively to bug fixes and performance enhancements.

It was very well received. I'm sure the same would happen if they announced they were dedicating an iOS version to bug fixes and performance enhancements.

EDIT: I think the version may have been Snow Leopard. :)

Re: Apple introduces macOS Mojave

#106
post #19

The News, Stocks, Voice Memos and Home apps were brought to Mac using iOS frameworks that have been adapted to macOS. Starting in late 2019, these additional frameworks will make it easier for developers to bring their iOS apps to macOS — providing new opportunities for developers and creating more apps for Mac users to enjoy. Looks like UIKit is the future, despite protestations to the contrary.

Hope significant are the differences between cocoa and uikit? I don't have any experience besides some light source browsing and it seemed the big difference is the NS to UI prefix change. Anyone care to summarize for the unenlightened?

[deleted]

Re: Apple introduces macOS Mojave

#107
post #13

Earlier quoted context omitted.

Have you seen the part where you can easily port iOS apps to macOS that was probably in the making for a few years? That's pretty huge for a developer conference. Changes to the app store to make discovery easier and feature more developer stories also have a huge impact on Mac/iOS developers and their revenue.

Is that an OS update? Do you really need iOS apps on the Mac? How about having decent apps in the actual native apps store?

If iOS has the dominant app platform, wouldn't making it easy to port to macOS be a good thing? You get to harness all those iOS app developers (who code on the mac anyway) able to have their apps run on both platforms. Seems like a win.

Re: Apple introduces macOS Mojave

#108
post #98
post #19

Earlier quoted context omitted.

Hope significant are the differences between cocoa and uikit? I don't have any experience besides some light source browsing and it seemed the big difference is the NS to UI prefix change. Anyone care to summarize for the unenlightened?

The differences are more in implementation than anything else: - AppKit isn't layer-backed by default, requiring you to handle this. Something as simple as setting the background color for an NSView is far more of a ritual than it is for a UIView. - NSColor/NSImage under the hood are different than UIColor and UIImage. - NSTableView and NSCollectionView have big differences (NSCollectionView is more subtle, I should…

Similar to some markdown parsers, you need to have multiple newlines in the source in order for the presentation to have a newline.

EDIT: Looks like you got there before I finished typing.

Post reply on HN