ernimrilYakov, I am one of a few here that have worked on big desktop apps for java, I have not seen any problem with it as such. Now, doing good UI is very hard, but it is the UI that is hard, not the platform you choose
YakovJambi in Indonesia?
Yakovwell, I want to make my own gui, starting from drawing dots in assembly, but for current task I want to switch from qt to java for some reason, it looks fine from a first glance, but I suspect it might not max efficient in comparison to some unknown yet vendor
dreamrealYakov: "max efficiency" is a will-o-the-wisp
Yakovhard to deploy, debug, resource heavy etc
ernimrilyou do not want to draw pixels for a modern gui, you want hardware support... but sure go for vulcan if you want
ParaWe're at "give datacenters all the drinking water" stage of max efficiency...
dreamrealmake it work well enough. Java's fine; plenty of people go "Java sucks for UI" while using IntelliJ for their IDE, completely forgetting that IDEA is written in 100% Java for the UI
ParaIs JavaFX vector based? Not that it really matters.
YakovQt written with Java?
dreamrealand Java can do images fine, too: you could write Minecraft in pure java now if you wanted to.
YakovI mean its IDE
Yakov23:50:36 <ernimril> you do not want to draw pixels for a modern gui, you want hardware support... but sure go for vulcan if you want
ParaJetBrains has their own LAFs they've built over time. It's still just Swing, I think?
dreamrealStill just Swing.
Yakov^ i want to go deeper and do my own kind of vulcan
dreamrealYakov: java can render pixels in the UI, you'd draw on a panel and let java render it
ernimrilswing, but with some patches
dreamrealjava2d is fine, so is javafx
dreamrealbut if you're trying to create your own tree/rendering pipeline, you may want to consider why
* Betal joined #java
* rvalue joined #java
* mindCrime joined #java
* monkeyPlus joined #java
* sponkz joined #java
* rvalue joined #java
* ferdna joined #java
* rorx joined #java
* rvalue joined #java
* mindCrime joined #java
* Nemu64 joined #java
* arthurvl joined #java
* geli joined #java
* gaxar joined #java
* jcirc joined #java
* lord4163 joined #java
* monkeyPlus joined #java
* fgarcia joined #java
* fgarcia joined #java
* fgarcia joined #java
NeXeNPara: ya ...uh yeah it is
NeXeNPara: but you might be confusing "vector based" with pixel pushing
NeXeNjavafx uses uh whats it called like retained scene graph or whatever
NeXeNthey're mathematically defined by their geometry not by pixel like pixel pushers
NeXeNor sorry didn't mean to imply you were confused, what i meant to say is most people assume that about javafx's canvas