mosaic VS KEEP

One of favorite offshoots of compose is https://github.com/JakeWharton/mosaic, which is a tool to build TUI's. Is something that you plan for this library, basically making the targeted renderer plug-able?

There's also Mosaic, which is an experiment of sorts to build console UI using Kotlin and Jetpack Compose: https://github.com/JakeWharton/mosaic

Not sure if this is what you're looking for but it seems pretty cool: https://github.com/JakeWharton/mosaic

To see some non-Android examples of Compose, take a look at https://github.com/JakeWharton/mosaic

Have you tried either clikt or mosaic??

Mosaic

Would be really cool if one day this could be made to work with the compose compiler, kinda like compose for web, mosaic (compose for TUI apps), or another project that I can't find right now but it was basically compose with one of Apple's UI frameworks

Jetpack Compose (Google's alternative on Android, that also works pretty much anywhere you can run a JVM and others like the web [1], terminals[2], powerpoints[3], as well as pretty much anywhere you have an imperative API that you want to transform into a functional model[4]) is infinitely more polished and has better tools than anything Apple has put out in all of SwiftUI's existence. Apple is bringing this upon themselves with their "major updates" concept for SwiftUI coming every other year, where components aren't even available on old versions of iOS. A UI toolkit is a library like any other, version it like a library and match patch releases.

[1] https://compose-web.ui.pages.jetbrains.team/

[2] https://github.com/JakeWharton/mosaic

[3] https://github.com/fgiris/composePPT

[4] https://github.com/googlemaps/android-maps-compose

Compose itself can be used by pretty much anything then. There's Compose UI, there's Compose Multiplatform, that on the web targets the DOM, on Windows targets... WinUI or any component library ? and more. For example, you can have a terminal renderer with it: https://github.com/JakeWharton/mosaic. Or hell, even drive an iOS view (https://twitter.com/jakewharton/status/1399561083204026369). The way it works also allows transforming coroutines calls, which are asynchronous into basically synchronous components, without ever making use of the UI part (https://github.com/cashapp/molecule).

`Either foo()` and `Foo foo() throws MyError` and are pretty much isomorphic.

https://github.com/Kotlin/KEEP/blob/master/proposals/stdlib/...

Nice. So for example, it looks like Kotlin has a nearly identical feature at the language level which will be optimizable when Valhalla ships: https://github.com/Kotlin/KEEP/blob/master/notes/value-class...

> In the future, in a Valhalla-capable JVM, JVM primitive classes will enable efficient representation of Kotlin value classes with an arbitrary number of underlying fields on JVM.

Most other languages agree that checked exceptions are not good by not having them.

As for alternatives, Try/Result and similar monads have decent adoption even in Java, but personally I quite like the Kotlin philosophy [1] to not have generic error containers and either use runtime exceptions or make failures of the return type.

[1] https://github.com/Kotlin/KEEP/blob/master/proposals/stdlib/...

If you want to read more and don't want to google it: https://github.com/Kotlin/KEEP/blob/data-objects/proposals/data-objects.md

Under the hood: https://github.com/Kotlin/KEEP/blob/master/proposals/coroutines.md .

you can check more here

You can use explicit API mode, then everything needs explicit visibility