Did someone work w/ #HorizonOS yet? I assume it is essentially like Android development? Or would you always use sth like Unity and never touch the actual "2D" GUI things? Is there a good introduction article for developers?
It is a little annoying that AsyncStream is named like that. Now I have to come up w/ other names for bidirectional streams, which is slightly annoying 🙂
@gruber Those memory comparisons are quite off really. There is nothing wrong with apps consuming all the memory available, it’s there, use it.
The key difference is what the memory is being used for, and for Electron that is largely just infra.
@stroughtonsmith@gruber They are certainly not native. Yes a set of builtin apps (like Messages) use that zombie and that is awful.
What system features does it power?
@stroughtonsmith@gruber For me native means that it follows the system UX conventions, UIKit is of course closer to that than say Electron, but it is still quite off. Just like you can easily tell an Electron you can usually tell a Catalyst app (eg via resizing behavior)
What language is being used doesn’t matter that much for me, a PyObjC Cocoa app can be perfectly sound.
An app using a different framework isn’t native 🤷♀️
Remember that I was confused and worried about #SwiftUI buttons in background windows not being "click-through" (aka acceptsFirstMouse) once you add custom styles?
I just started on a way to handle click-through events and then the very first step sufficed to make it work:
This wraps the SwiftUI.Button in an NSHostingView that always wants acceptsFirstMouse. And with that, the button it contains receives the click, not the hosting view!
Imo, an internal policy change Apple should adopt that would be great for everyone is if they release a new API in UIKit, it HAS to also be available in SwiftUI. If SwiftUI is indeed the future, no exceptions
@christianselig#SwiftUI is part of the future, it is not "the" future. It is still unclear how sth basic like a text editor can work with the scalability constraints of SwiftUI. Or a List w/ more than 1k items.
Everything becomes easier if you start to acknowledge that SwiftUI is a convenience extension to Cocoa, not a replacement in any way. And miraculously SwiftUI also allows super easy integration w/ Cocoa, making sure it is no either or 🙂
Is there a way to look inside PrimitiveButtonstyle or its effect on the button and see whether it can be replicated?
Because with .plain, some things break that work with .bordered -- and a custom regular ButtonStyle also doesn't work. So the bordered one must be doing something interesting, but I can't get to the honey 🍯
@ctietze@chris The plain button doesn't respond to -acceptsFirstMouse: while the bordered one does. And this is because the plain button doesn't end up being an actual NSButton (which has this behavior), while the bordered one become an NSButton.
@343max@ctietze@chris Those are the "little things" that b0rk if you use a non-AppKit app, say Electron or Catalyst, ... or SwiftUI sometimes.
AppKit has a very specific set of buttons available. And I'd say you are not really supposed to style them in the first place (which clashes w/ what SwiftUI allows). @mackuba has a nice overview: https://mackuba.eu/2014/10/06/a-guide-to-nsbutton-styles/
@Migueldeicaza@david It doesn't say Safari but HTML 5. I think the idea here is that you host the Wasm in JSCore and expose a UIKit API towards it. (within an app, not Safari)
(but I don't understand that HTML5 thing, but 4.7 specifically talks about in-app)
So you spend years and years to make sure that the Swift compiler makes super highly optimised binaries possible (in release mode), so much that it rivals C++ and Rust in performance.
And then you take that highly optimized binary, and run it in a JavaScript interpreter. Or even better, a JIT 🙈 Which is running on either an ARM or an Intel server.
I'm still hoping for Apple to add support for time-limited trials and paid upgrades to the App Store. No, I'm not interested in IAP. Maybe EU could force them.
@gregtitus@sindresorhus Yes, but why implement it on your own? (and yes, the iAP messaging is not helpful) Everything being custom everywhere is not good for the customer either?
Just implement the trial and upgrade flow in the AppStore. They get paid to run that, maybe they should make features their customers, the devs, want?
