Seems likely that they're submitting here as Reclaimer. The single comment on these submissions has that same fervent religious writing style as the readme on that EXA repo, itself just a fork of an "awesome-multimodal-ml" collection: https://news.ycombinator.com/submitted?id=Reclaimer

I am here, and saying something is just a fork is very easy to say. There are dozens of models, optimizers, all-new activation functions, and data cleaning and other stuff!

Supposedly a major justification for the continued separation of Mac and the others (especially iPad) was differing UI interaction patterns.

So what are they doing now? Using tools that evolved to serve touch-first interfaces to build desktop applications.

The Mac/iPad split grows more confounding with every iteration. Now it feels like familiar desktop features are being reimplemented poorly in both iPadOS _and_ macOS.

it’s not that confounding when you consider that iphones dominate apple’s earnings, and so apple wants to unify the platforms under ios (via ipados) rather than under macos where they have no app store lock-in.

It shouldn’t be confounding. It seems clear:

Apple views the Mac as an iPad with an attached keyboard and optionally cooling.

There will be touch on the Mac very soon and they are preemptively getting the Apps ready. The whole Apple Silicon migration is to facilitate this merge of macOS and iPadOS. As soon as the 3 year migration to Apple Silicon is complete and most developers have stopped relying on Rosetta, Macs will have touch and there will be no longer two OSs.

What a depressing future we're headed into :/ Instead of iPad becoming a "proper" computer, the Mac is being dumbed down to become a tablet with a keyboard attached. Sometimes I wonder if the people making decisions at Apple, Google, Microsoft etc. live on a completely different planet than me.

I wouldn’t worry about that. They need to hire developers, etc and they need to be able to build their own software.

The new iPad-Mac merge will have Xcode and maybe a Unix like terminal.

I knew something had to be up with them. It’s bad when I come across a round-up or comparison that fails to even mention my top options, and that seems to be the norm over there.

If those instances are only for tests/validation it could simplify some overall pipelines quite a bit.

This was a great read, thank you. I’m just now removing my application-focused blinders, but I already see the same technical, organizational, and financial issues.

> I do not own any HiDPI monitors

This is a major factor. macOS has aggressively optimized for these in recent years, often at the expense of classic 1x display experience. I use 5K 27" and 4K 24" monitors at 2x scaling (this is the default), and the result is excellent.

> The applications broken in v4 are so niche that most people won't notice.

Except when you’re building these applications. Then it’s infuriating! Maybe more often a feeling of hopelessness than anger.

This is a pretty grim outlook. It’s at best a false dichotomy between “code lovers” who write beautiful code and “money lovers” who write ugly code. An engineer who can adapt their output based on constraints and requirements deserves to be well compensated for that flexibility.

I didn't mean it to sound grim.

>An engineer who can adapt their output based on constraints and requirements deserves to be well compensated for that flexibility.

Yes, but somebody that is not motivated by money will have no incentive to adapt to the constraints and requirements. Which is what the whole thing is about.

Except perhaps if they are motivated to make the rest of the team happy I guess.

Most businesses exists to make money. I think having everybody in the room on the same page is very valuable.

No apparently that means you don’t know what you’re doing, and you’ll corrupt the repo, and you’re not a real software developer so we’ll come to your desk and rip up your I’m A Very Serious Professional card.

It's funny, because most devs that are pro CLI for these kind of things, are actually unable to operate vi, or install any server / container without installing a complete desktop environment.

Let's all go back to the ed line editor

Swift is multi-paradigm. Improved support (over ObjC) for functional style, protocol-oriented design, and value types has led many to overuse them.

Multi-paradigm isn’t a cop-out, it’s a pretty specific goal of the language. Being overly “faithful” to particular patterns will conflict with this, as you’ve likely experienced. I appreciate the ability to break out and use different styles where appropriate. That pesky “last 10%” is now far less painful. It also allows for varying styles per module based on functionality required and libraries in use.