Flutter

3 readers

1 users here now

Flutter and the related logo are trademarks of Google LLC. We are not endorsed by or affiliated with Google LLC

founded 1 year ago

MODERATORS

Ategon@programming.dev

Maybe we should have switched to C#, @flutter , or @slint , instead of porting from #Qt5 to [#Qt6] (mastodon.green)

submitted 1 week ago* (last edited 1 week ago) by taschenorakel@mastodon.green to c/flutter@programming.dev

3 comments fedilink hide all child comments

Maybe we should have switched to C#, @flutter, or @slint, instead of porting from #Qt5 to #Qt6.

@qt

#Programming #CPlusPlus #Sigh

you are viewing a single comment's thread
view the rest of the comments

[–] hunger@fosstodon.org 2 points 1 week ago (2 children)

@taschenorakel @flutter @slint @qt I'll always argue for #rust + #slint, but I am heavily biased.

[–] taschenorakel@mastodon.green 1 points 1 week ago (1 children)

@hunger I'd argue this team here lacks the required skill level to take advantage from Rust. (Well, and I lake the patience for Rust's compile times).

I still like alot what you guys are doing.

@flutter @slint @qt

[–] hunger@fosstodon.org 1 points 1 week ago

@taschenorakel @flutter @slint @qt #rust is not that hard for a C++ dev IMHO... the biggest change is that you need to learn to trust the compiler: It does have a point when it flags something, even when you go "that is wrong, I do that in C++ all the time and it never caused any problem".

Compile times are not that much worse than C++ and are actually improving -- slowly.

But #slint has great #cpp support, too, so just use that till your team is ready to adopt rust.