261–270 of 343 posts
SwiftUI has a lot of failings, but it can also do a lot of things that are really tricky in UIKit. I can render Metal shaders trivially in SwiftUI. Rendering glows, and blurs, and animated effects is much easier in SwiftUI than in UIKit, just use `.blur(radius:)` or `.blendMode(...)` I have used AppKit and then UIKit since its inception. Creating visual effects like layer masks that modulate the opacity of underlying…
SwiftUI has a bunch of problems but almost none of them have anything to do with what this guy has to say :( Like, there are issues with almost every point: > We started with @State, @Binding, and ObservedObjects. Then Apple realized the performance was disastrous and SwiftUI was re-rendering views all the time. That’s when it introduced the Observation framework and the @Observable macro. They tried to solve the pro…
The problem with complex systems is that you can be dead long before you realize you're dead. Things can continue to seem "pretty good" for a long time just from the inertia of past good decisions and built-up infrastructure. You see some fraying or cracks but everything looks fundamentally sound, until it isn't. Apple's inability to deploy a new UI framework that's better than the previous one is troubling. This is…
> Could Apple build MacOS X and Cocoa today if they didn't already exist? Apple got rid of all the NeXT people long ago, with Tim Cook stabbing Scott Forstall in the back, so the answer is No.
Earlier quoted context omitted.
I like my Controller to be responsible for all the "business logic" so that its all in one place. It's the important part. The View layer is always fairly verbose and full of fluff. Especially if you have a lot of animation and formatting type code.
> I like my Controller to be responsible for all the "business logic" so that its all in one place. Business logic is supposed to go in the model. All of it. Because it's the important part. Controller these days can be largely empty. "MODELS Models represent knowledge. A model could be a single object (rather uninteresting), or it could be some structure of objects. There should be a one-to-one correspondence betwee…
Earlier quoted context omitted.
It was a bit more than that, including how out of place it looked in fruity platforms.
No, they did not change the renderer because of Apple. That is a complaint about Flutter, the iOS-aping widget set can't stay up with current iOS, and I don't think they have a real solution yet. There's something about pulling out the Material UI library from Flutter itself that's supposed to help (I don't quite understand why, modulo "we can make a focused team work in a package instead of in the big ol' framework…
Earlier quoted context omitted.
Genuinely curious, what’s wrong with it? I’m no huge apple fan, but I didn’t really think the 17 was more than a regular boring spec upgrade, which seems fine all things considered. (Currently on an iPhone fucking 17)
Apple did not use to be in the business of producing version 17 of something.
Earlier quoted context omitted.
Which tasks ? I don't believe your claims.
If you dont believe me… nobody is stopping you from testing various things on the same model? And if you dont have it already… then what could I possibly say that would motivate you to buy a used one to do the testing to confirm? Edit: And even on my ipad pro m2 doing literally nothing other than swiping to the app library often causes a visible stutter and lag for hundreds of miliseconds… so if you really think it’s…
And your iPad example doesn't make sense at all, you compared 2 Macbooks and now you're talking about another OS altogether.
> idk what to say.
You could just tell us one example of something that's faster on your 2019 Macbook Pro 15 versus a M5 Macbook pro and how to reproduce it.
Earlier quoted context omitted.
Apple seems to be loved by users, but hated by developers (and for good reasons). They just seem to not give a shit about the developer experience. You mention some examples, I have experience with lower-level stuff: terrible. Poorly documented, and actually not really working well. IMO they should focus on improving the developer experience instead of wasting money on the joke that is Liquid Glass (even users don't…
This used to be different. NeXTstep and early MacOS-X were pretty much the finest platforms to develop on.
Earlier quoted context omitted.
That's pretty much where immediate mode GUIs and to a less extent React came from. (Though for React the provenance is probably closer to the HTML web-app: send request - update model - return HTML with complete and completely new UI.) The difference is that for most games, throwing away the complete rendered graphics and re-rendering from the world model is often the right approach. For most UIs, it isn't, unless th…
> For most UIs, it isn't Why? Genuinely asking, this topic is very interesting to me.