41–50 of 53 posts
Stripping copyrights is a great way to start a project: https://github.com/JetBrains/compose-jb/commit/6009cdd6cbdcf...
Quite great. I never understood why you'd want that copy-pasted everywhere: it's just noise. Isn't a `LICENSE` file at the repo root enough? https://github.com/JetBrains/compose-jb/blob/master/LICENSE
I wish there was a screenshot of a demo app. How do you market a UI toolkit without any screenshots of what I can do? I'm not going to build a demo project to see what the UI looks like.
My biggest gripe with virtually every UI is that it forces you to learn yet another language just to code with it. Why can't there be UI APIs that work across languages like there is with loads of other stuff? We have this for networking, disk I/O, common OS operations, and even 3D graphics , but for some reason 2D user interfaces just can't be presented in this way. Why can't there be an OpenGL-like thing for deskto…
> Back to the topic at hand. It's not that Kotlin is a bad language. I've heard it's quite nice. The problem is that it's yet another language which means more cognitive load, more build complexity, and so on. If my project is in Go or C++ or Rust, I want my UI in Go or C++ or Rust. Can we not pretend that go and rust are the only languages people use? What if my project is in Kotlin? Maybe I want my UI in Kotlin too…
Earlier quoted context omitted.
I agree as a developer, but I think the economics favour having many incompatible UI libraries: A. It’s expensive to standardise and agree on what the UI primitives would be, and a standard would force the lowest common denominator of features. If you want a new whizz bang button now you have to create an RFC and cajole agreement. B. It’s profitable to own the platform, which includes the UI, because then you can cha…
There's actually an advantage for users. Because you have to enter a new mindset for each platform (or have different devs for each) it pushes you to think about designing the UI to fit the platform. It's nice when the UI and UX feel like they belong with everything else on the system.
Can't JavaFX already do a good job here?
This looks interesting, having skia as the drawing foundation and reactive as a core element sounds like they’re rewriting a flutter like framework but on the jvm instead of dartvm. Jetbrains sometimes dogfoods their products so I hope to see this technology exercised into utility
This looks interesting, having skia as the drawing foundation and reactive as a core element sounds like they’re rewriting a flutter like framework but on the jvm instead of dartvm. Jetbrains sometimes dogfoods their products so I hope to see this technology exercised into utility
This is interesting, in theory it could open a path for their IDEs to go native. This coupled with Kotlin native of course.