JetBrains Compose • Hacker News Board

Re: JetBrains Compose

#51

Post by vips7L » Fri, Nov 06, 2020, 4:16 AM UTC

api wrote: post #44

vips7L wrote: post #40

Earlier quoted context omitted.

> 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…

Sure. My point is that you should be able to have yours in Kotlin and I should be able to use Go or Rust.

Then bind to Skia like both compose and flutter are doing? I don't understand the problem here.

Re: JetBrains Compose

#52

Post by remify » Fri, Nov 06, 2020, 12:46 PM UTC

donmcronald wrote: post #16

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.

This has become my way of knowing if a UI framework is garbage or not.

Re: JetBrains Compose

#53

Post by api » Fri, Nov 06, 2020, 6:33 PM UTC

vips7L wrote: post #51

api wrote: post #44

Earlier quoted context omitted.

Sure. My point is that you should be able to have yours in Kotlin and I should be able to use Go or Rust.

Then bind to Skia like both compose and flutter are doing? I don't understand the problem here.

Skia is a drawing library, not a UI library. That's like saying you can substitute DirectX or Metal for a full 3D modeling engine.