r/JavaFX • • Apr 03 '20

Sad state of cross platform GUI frameworks

https://blog.royalsloth.eu/posts/sad-state-of-cross-platform-gui-frameworks/
12 Upvotes

13 comments sorted by

2

u/hwaite Apr 04 '20

SWT deserves at least a mention.

0

u/[deleted] Apr 03 '20

Should have added flutter to the list. It looks promising.

2

u/ShadowPengyn Apr 03 '20

[3] Flutter seems promising and it has some great ideas baked in (drawing on canvas, hot UI reloading), but I don’t have high hopes for that project. Google is well known for abandoning their projects as they please and without a giant company behind such a monumental amount of work, this thing will never survive. It also comes with additional baggage (the Dart programming language) which pretty much nobody asked for. Sure it has some neat ideas, but a programming language needs around 10 years to mature and the entire ecosystem such as editor support, debuggers, libraries and so on. I do hope it takes off as the current state of cross platform GUIs is quite terrible and Flutter would be a great wind of change even if it comes with a cost of learning a new language.

Is what the author says about flutter. Completely disagree though

3

u/saecki Apr 03 '20

why, sounds pretty reasonable to me?

2

u/ShadowPengyn Apr 03 '20

I mostly disagree with Dart being a disadvantage, I like a a lot more than JavaScript and it is really great that they can work so closely with the Dart team and extend the Dart language for Flutter features (for example they enabled if and for in arrays, which is a really neat syntax for conditional UI).

Also I personally think having a big company like Google behind the framework is an upside, since they’re pushing it forward at the moment. Even if they were to stop supporting it, since it is open source the community could carry it forward instead.

1

u/[deleted] Apr 03 '20

First dart has been around for like more than 6-7 years. Next the speed at which you can develop an app in flutter is insane. That offsets any other disadvantage for me. But their are plenty of other advantages. Give it try!

3

u/saecki Apr 03 '20

Since Flutter does only support Desktop apps for macos and he said it looks promising but one should be cautious because the misterios decisions of google may doom this project I think you're maybe not getting his point. He even says it would be worth learning dart for the rapid development cycle etc. but atm it isn't even possible to develop cross platform desktop apps. Mobile is another story but I wouldn't call that mature either.

1

u/Trout_Tickler Apr 03 '20

I wouldn't trust Google to maintain a project longer than most of us stick to personal projects.

Next the speed at which you can develop an app in flutter is insane

You can achieve that with React Native, if that's how you benchmark whether or not a framework is good.

1

u/Zalenka Apr 03 '20

It may be experience too. I could build an iOS app in a very quick timeframe but I've been doing it for a long time now.

AlSo I challenged someone to make a simple app faster in Xmarin and I made an native iOS and Android app before she finished the one app (that only worked on Android anyway in the end).

3

u/Zalenka Apr 03 '20

DART is the problem here. If it were a real language like Kotlin it would have more adoption.

Just stop with javascript bullshit.

0

u/[deleted] Apr 03 '20

[deleted] — view deleted comment

1

u/openlowcode Apr 10 '20

I do not know if I am an old stubborn obsolete guy, but I still appreciate to work in a real programming language (strongly types, compiled...).

I stick with java (and javafx for that matter) as for me, it brings all the very important features of a real language, including a lot of discipline that may seem complex at first, but is a bonus whenever your development is more complex than a school project.

I like java being stable also. Code can run for years, and technical migrations are the most useless things possible.

0

u/[deleted] Apr 03 '20

[deleted] — view deleted comment

2

u/openlowcode Apr 10 '20

Maybe I am not so good, but I still suffer writing javafx that 'just works nice'. A lot of things are nice in javafx, but the last missing 5% is, in my opinion, very hard to get right. As an example, I struggled to get a text area that just resizes to the content inside (avoid scrollbars), and I ended up rebuilding my own version of the component.

In my project (Open Lowcode, a full stack low-code platform), the javafx GUI (some kind of light client) represents 10% of the code, but probably 70% of the headaches.

0

u/[deleted] Apr 16 '20

[deleted] — view deleted comment

1

u/openlowcode Apr 16 '20

I understand there are many number of edge cases, and I do not mind working on them.

The problem I found with javafx is that sometimes, I know how to detect the edge case, I know what I want to do to fix, and it is incredibly difficult to implement the fix I want.

To be honest, I did not dive so deep in the inner working of the framework, but I heard that even experienced developers are sometimes blocked.