What is the best forum for Mac Development nowadays? Any active developer groups (Facebook, Slack, LinkedIn)? My local so-called Mac Dev group has mostly become iOS developers and server-side programmers. I have been working on some open-source projects (announcements in the near future), but I am surprised how few people are working on Apple desktop coding.
This may be a repeat of last generation square off, where PS4 outsold the Xbox about 2 to 1. Nintendo will continue to be the popular niche console, mostly due to its exclusive like of Mario/Pokemon games.
Years later, the concept of reconciling patterns into various different types of formulas and algorithms is a major part of software engineering. I find it fascinating that these young mathematicians were not complaining that the older generation was not being flexible, but that they were not being organized enough.
A follow up for today's post: Apparently, Pepsi can not do an ad campaign without getting in trouble. They accidentally offered to give a $30 million fighter jet for $700,000.
If you want to be able to loop thru the content of your custom Swift object, you need the Sequence protocol Navdeep Singh article explains the working and requirements of this useful Swift protocol https://medium.com/swlh/swift-sequences-fc388635c4af
Before the Mac with its 3.5 drive, there was a prototype Mac using the Lisa 5.25 twiggy disks. There are only 3 of these still existing, and they work!
One was on sale last year, and sold for $150K. And to think I had my hands on a broken one once, and could have grabbed it, instead they threw it out.
Side note: I am working on a public Swift Package release of my closure based SlamKit. It replaces Mac & iOS user interface elements (with Target/Action, DataSource, Delegate patterns) with a Closure approach. Since it works on almost all older OSes, I will probably stick with that until iOS14 becomes more common, before using UIActions.
Tom Scott explains what is happening when Green Screening fails badly.
Sometimes you know it looks wrong, with understanding why it does. Scott explains the why, and suggests how to get around these issues. (Hint: don't try to be realistic)