News for hackers. Stuff that matters.
Re:The origins of Objective-C at PPI/Stepstone and its evolu... by ChrisMarshallNY on Sunday June 14, 2020 @08:19AM (#23517146)
> I also don't think it's really how we do everything

Good point, and I agree. It was probably a rather "generalized" statement, on my part. I really meant "clumped-together opaque modules."

Yeah, COM worked (sort of), but CORBA has always struggled, and that was probably the real methodology that expressed the concept.

What I was thinking, was the "dependencyshere" that pretty much describes software development, these days; often linked through communications networks (as opposed to binary APIs). A bit like the distributed nature that was a big part of CORBA, but without the common data link layer.

There's an entire generation of engineers that can create marvelous applications, but barely understand what's going on in the components they use (which is not necessarily a bad thing. I don't know what's going on inside my calculator).

BTW: Thanks for the excellent article.

For what it's worth, I use frameworks a lot. I have always believed in modular development, with modules being atomic, standalone entities with independent lifecycles.

Not all of these are "frameworks," per se. For example, my RVS_Spinner project, which implements a powerful "prize wheel spinner" in UIKit, is actually just a single source file, and not really worth importing as an opaque framework: https://github.com/RiftValleySoftware/RVS_Spinner

Same with my persistent prefs project, which is just a single, 300-line file: https://github.com/RiftValleySoftware/RVS_PersistentPrefs

Most of the code in these projects is testing code (I like testing. It's a good thing).

Modern package managers help that along.

Re:The origins of Objective-C at PPI/Stepstone and its evolu... by mpweiher on Sunday June 14, 2020 @03:24PM (#23520550)
> create marvelous applications, but barely understand what's going on in the components they use

Totally agreed that this is the vaunted reuse that we were desperately trying to achieve in the 80s and 90s. Did we ever achieve it! And yes, this is a Good Thing™, and it really irks me when people claim we have the same "software crisis" we had in the 80s or 90s, or even since 1968. I just want to shake them an go "open your eyes, look around"

Yes, we have problems with the state of the art, but these are new problems that are due to our past successes.

Re:The origins of Objective-C at PPI/Stepstone and its evolu... by ChrisMarshallNY on Sunday June 14, 2020 @03:52PM (#23520771)
Thanks. I know that you are someone that is a bit on the older side (maybe not quite my age, but a bit more experienced than many).

I am glad to see your optimistic outlook. I have a similar one. I have often been accused of being "negative," which makes me laugh.

It's just that I have been delivering software for more than 30 years, and have come to learn that there's a great deal of work necessary, when creating and nurturing a vibrant, growing, and attractive future.

There's a lot of compromise, as well as many layers, built over time, with care and patience. Testing, documentation and support are necessary, as well as a commitment to "seeing the story through to the end."

I have compared creating SDKs and modules to having children. Once we have brought them into the world, we are responsible to maintain them, and support them for the rest of our lives.

Those are "classic" values that are just as valid today, as they were when Fred Brooks was a kid.

In reality, we are standing on a mountain of work, done by our predecessors.

We don't need to rebuild the mountain; just put on oxygen masks.