Prior to sealed classes, I wished they were more like swift enums that could carry dynamic data and have different associated types per case. Now if I want that, I can do that with a sealed class. It’s still nice to have smarter enums if I need a little extra smarts and want to keep the logic close to the enum.

Maybe the code generator? I have no idea. It seems like there shouldn’t be an issue.

Fellow American here, I definitely read it the wrong way.

I only use it when I need to initialize a property in a constructor. Otherwise I consider it a bad idea.

I’ve only tried to write rules for the older realtime database and it was awful. Anything that can help to turn configuration into code is going to be helpful and appreciated.

The only reason I can think of is for more on device ai. LLMs like ChatGPT are extremely greedy when it comes down to RAM. There are some optimizations that squeeze them into a smaller memory footprint at the expense of accuracy/capability. Even some of the best phones out there today are barely capable of running a stripped down generative ai. When they do, the output is nowhere near as good as when it is run in an uncompressed mode on a server.

The back gesture is fine until it takes me out of an app. I hate that. Sometimes I trigger it unintentionally because I’m trying to swipe in an app but the system picks it up instead.

A place I worked at actually did this to a person named Diane Cupps.

As long as the app is storing the auth token received from the lemmy instance securely it makes no difference whether you login once or multiple times.

It depends on what your needs are. Database drivers for connecting straight into a database server will be limited. Dart just hasn’t gained as much momentum on the server side as other languages and most apps use an n-tier architecture so no need for drivers. There’s no server side rendering for flutter so your app startup time might be a hinderance for a user just wanting to pull up a web page and see some data.

Apple will say that SwifUI is already cross platform. 😂 I work in it daily and will say that it’s quite nice and easy to develop in. There are plenty of drawbacks and the “magic” can be quite heavy at times. Compose is making inroads into the spaces that Flutter has been working on. Jetbrains made a desktop port using the JVM. They also have web and iOS ports in various stages. It’s all very early days for them.

I’m still doing all of my side development using Flutter. It’s barely a question in my mind to consider anything else at this point.

That back gesture on android is a system level gesture. On iOS it is an app level thing. If it doesn’t work it’s because the app developer was lazy when they made their own custom navigation controller. File bugs and leave low rating reviews.

I wonder how much Compose and SwiftUI have stolen the wind from Flutter’s sails. It’s either that or Flutter has become a more mature ecosystem and there isn’t as much to talk about or create from scratch anymore. I feel like the weekly newsletters that I get used to have much more and better content than they do now.