Matthias Berndt

> Thinking about this some more, I think we should target version `2.0.0` for Scala 3 and Java 14+. I think bumping to a new major version might be the...

Hi Atry, Thanks for the response! I used `scalaJSUseMainModuleInitializer := true`, so I'm not invoking `main` manually at all, and I did put the `` element into the `` since...

Note that I'm not sure what the solution would be here. It's probably not possible to automatically generate subqueries in such cases because it's inherently ambiguous. Take this query: ```scala...

Hey @jpsacha, I suspect that this isn't just a Scala compiler bug that is going to be fixed. The type inference algorithm just works differently now, often better and sometimes...

Well, the issue is this definition in `Shape.scala`: ```scala def fill: ObjectProperty[jfxsp.Paint] ``` It’s defined as a JavaFX `Paint` property. If we want it to work with ScalaFX’s `Paint` type,...

> What I propose it to create our own representation of a JSON-like value and keep it as small and minimalistic as possible. Here's something the Scala community doesn't need:...

Right, so all of the stuff you describe seems to be HOCON-specific, which means that abstracting from HOCON would sort of defeat the purpose of the library, right?

> Right. I'm not an advocate for abstracting the config backend in the core module. I prefer to keep the core simple and, if need be, have modules that translate...

I agree with @zuiderkwast that WebAssembly (WASM) should be considered as it has many advantages. - many available implementations, such as [this fast, low-footprint one written in C](https://github.com/bytecodealliance/wasm-micro-runtime) - [many...

I would not recommend using a response ADT, because then you need to pattern match against the return value and have to deal with cases that you know can't happen...