Flutterby™! : I understand how some decisions in

Next unread comment / Catchup all unread comments User Account Info | Logout | XML/Pilot/etc versions | Long version (with comments) | Weblog archives | Site Map | | Browse Topics

I understand how some decisions in

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 ascending chronological order (reverse):

#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.

#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.

Add your own comment:

(If anyone ever actually uses Webmention/indie-action to post here, please email me)

Format with:

(You should probably use "Text" mode: URLs will be mostly recognized and linked, _underscore quoted_ text is looked up in a glossary, _underscore quoted_ (http://xyz.pdq) becomes a link, without the link in the parenthesis it becomes a <cite> tag. All <cite>ed text will point to the Flutterby knowledge base. Two enters (ie: a blank line) gets you a new paragraph, special treatment for paragraphs that are manually indented or start with "#" (as in "#include" or "#!/usr/bin/perl"), "/* " or ">" (as in a quoted message) or look like lists, or within a paragraph you can use a number of HTML tags:

p, img, br, hr, a, sub, sup, tt, i, b, h1, h2, h3, h4, h5, h6, cite, em, strong, code, samp, kbd, pre, blockquote, address, ol, dl, ul, dt, dd, li, dir, menu, table, tr, td, th

Comment policy

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.