2021-07-29 19:55:02.163403+02 by Dan Lyke 2 comments
I understand how some decisions in NeXTStep ended up there: Young brash programmers thinking they're doing amazing things by pushing the envelope. I do not understand why some of those flaws ended up carried over into Mac Cocoa. And I hate NSSplitView with a white hot passion.
[ related topics: Macintosh Race ]
comments in descending chronological order (reverse):
#Comment Re: I understand how some decisions in made: 2021-07-30 19:08:30.737979+02 by: Dan Lyke
Oooh, good to know! We're *this* close to writing our own, but we're also looking at business direction, and Apple may not be in the cards for the next iteration here.
It wouldn't be so bad if Apple didn't blow chunks about multiple calls to
layoutSubtreeIfNeeded. I mean, it'd still suck, but less.
#Comment Re: I understand how some decisions in made: 2021-07-30 04:38:13.804758+02 by: markd
having just wrestled with NSSplitView and NSSplitViewController, it has always been a flaming hot mess. I don't know if RBSplitView is still updated, but it was the go-to fixer for the built-in split view.
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.