• by skybrian on 7/6/2024, 10:44:20 PM

    For every sufficiently successful single-language ecosystem, there will be people trying to use a different language, turning it into a multi-language ecosystem.

    Also, for every sufficiently successful multi-language ecosystem, there will be people trying to get it to support one more language.

  • by j-r-d on 7/6/2024, 11:02:08 PM

    Why though? Flutter was built for Dart and, while not my favourite language, it does that job very well. When the major drawback of all multi-platform frameworks tends to be performance, how does using a much slower, non-compiled language improve things?

  • by hgyjnbdet on 7/7/2024, 12:58:50 PM

    I have some confusion how a dynamically typed interpreted language that allows nulls interfaces with something that expects types, null safety, and ultimately is compiled.

  • by bozhark on 7/6/2024, 9:51:04 PM

    “View via iOS Flet app” is not “enables developers to easily build realtime web, _mobile_ and desktop apps in Python.”

  • by vouaobrasil on 7/6/2024, 9:55:08 PM

    All these multi-platform kits are getting fatiguing. Electron, sciter, neutralino, proton native...there are hundreds of others, and now Flet. Reminds me of the Google/Apple app stores, where there are 100+ solutions for the same problem, and all of them suck.

    I wonder if we really did a good thing by building this "app culture" where everything needs a little "app" as a way of extracting a little more money from people. Although "app" means application, the word "app" is apt because it signifies the commercialization of applications into advertisements-as-a-program, in the same way that YouTube transformed videos into advertisements-as-a-video.

    What a mess.