Flutterby™! : Trying to understand a complex codebase

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

Trying to understand a complex codebase

2025-01-28 01:25:02.86558+01 by Dan Lyke 2 comments

Trying to understand a complex codebase that makes extensive use of XCode's "Package Dependencies", and all of a sudden we're back to find and grep to try to figure out WTF.

Also, love (as in "hate") that XCode 16 won't compile code that XCode 15 will.

comments in ascending chronological order (reverse):

#Comment Re: Trying to understand a complex codebase made: 2025-01-29 00:35:13.901085+01 by: Mars Saxman

These experiences you relate give me a sense of peace about my decision to abandon that platform, eight-ish years ago, after it had been my home for thirty years. Linux never pisses me off like this. I'm sorry you're suffering, but selfishly glad you're talking about it.

#Comment Re: Trying to understand a complex codebase made: 2025-01-29 00:47:29.436802+01 by: Dan Lyke

Current job is going through some upheavals, and I've been keeping my eyes open for other possibilities, just to know what's out there, and every time something Apple related comes through I'm having a "wait, is that really a direction I want to go?" moment.

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.