31–40 of 53 posts
Stripping copyrights is a great way to start a project: https://github.com/JetBrains/compose-jb/commit/6009cdd6cbdcf...
Isn't a `LICENSE` file at the repo root enough? https://github.com/JetBrains/compose-jb/blob/master/LICENSE
How does this interact with the Accessibility settings on Mac OS?
How is this better than Flutter? If the answer is Kotlin > Dart, then what if Google comes up with a Flutter version that supports multiple languages (Dark/Swift/Kotlin)? If I'm to pick Flutter vs Jetbrains/Jetpack Compose - I'd pick Flutter because it supports desktop, mobile & web. And Flutter's philosophy of rendering directly using Skia on all platforms seems to be a sound strategy.
The lower bound of an answer is this: when the core of your work is kotlin android dev and you are only occasionally required to dabble in desktop (perhaps for some internal tooling related to the backend of your app) skill transferability will be worth a lot. Everybody can throw together hello world and some buttons in any toolkit, but reaching any meaningful level of productivity requires a lot of experience in the toolkit.
Something designed from the beginning for multiplatform will very likely end up not productive overall of you have a 50:50 distribution, but if you have a clear first class platform for product / second class platform for the occasional supporting tool situation, then something designed specifically for the first class platform that also has some capability for the second class platform can easily be superior.
Stripping copyrights is a great way to start a project: https://github.com/JetBrains/compose-jb/commit/6009cdd6cbdcf...
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.
There is if you scroll just a little bit down the page
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…
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…
How does this interact with the Accessibility settings on Mac OS?
It's not here yet, but we are planning to add it soon
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…
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?