quilc VS skiko

Yes, they use it for their quantum compiler, at RHL Laboratories (it was maybe initiated even at Rigetti). https://github.com/quil-lang/quilc

QUILC is probably the most interesting project. It is an open-source automatic, retargetable, optimizing compiler for Quil. It can take nearly any quantum computer architecture description and compile+optimize a Quil program for that architecture.

The QVM does all manner of quantum computer simulations. It specifically simulates a Quil program, with both classical and quantum operators. The QVM has lots of different modes of operation:

You can do this with a compiler like quilc. A program like

This is a new physical implementation of a particular mathematical operation, on a specific modality of qubit. The same mathematical operation can be computed on any other quantum computer in production today; very easily so if you use a compiler like QUILC [0].

[0] https://github.com/quil-lang/quilc

For people who maybe already have a job, just want to dip their toes in, or some other life thing that prohibits them from being employed, I’ve done pro bono mentorship sessions to interested individuals, helping them contribute to open source software around this stack, like the quantum compiler. Always happy to discuss that for serious applicants.

compiler code

Yes, simulator, compiler, paper is some of it.

Speaking about Common Lisp, the only commercial-level compiler implementation that I know of is https://github.com/rigetti/quilc by /u/stylewarning et al.

All I know is that they use skiko.

It built on a render framework named skia, JetBrains create a kotlin mapping which named skiko for it.

I was curious to give it a go but unusable on Gnome 42.5; the window lags so much that simply trying to drag to reposition it on the screen is impossible seems related an issue with Skiko and OpenGL reported here: https://github.com/JetBrains/skiko/issues/494

Fleet does not use Compose, but it does use Skiko[1], which also provides binding for Skia[2] (the native graphics library also used by Chrome & Flutter).

The main difference between the libraries is that Skija provides Java/JVM bindings for Skia, whereas Skiko provides Kotlin bindings for Kotlin/JVM, Kotlin/JS, and Kotlin/Native targets. Of course Skiko's Kotlin/JVM bindings can be used with other JVM languages, not just with Kotlin.

[1] https://github.com/JetBrains/skiko

[2] https://skia.org/

How about skiko?

JetBrains is moving from skija to skiko, but it could be interesting either way!

They Merged today the functions that will be usaged on Compose for opening, closing and handling text inputs https://github.com/JetBrains/skiko/pull/455 (if I understand correctly). Currently, the examples rely on xcodegen file, based on the currently plugin that Compose has for Desktop, it provide alot of things including packaging for desktop, I think they will provide a xcodegen file automatically and use xcodegen behind the scenes to generate everything needed.

https://github.com/JetBrains/skiko (a Kotlin MPP binding for Skia). Skiko Does not contain build for iOS. Now Skiko contains build for iOS, MAC arm processor via Kotlin/Native. So we can use Skiko for pure canvas rendering in all platform. It is matter of time they release compose for iOS. So UI also goes multiplatform.

But it does seem like the solution they're using for Fleet is different. Skia is the same graphics library used by Chromium and Flutter. I'll remain cautiously optimistic for now, but the quality of the text rendering and customization options will make or break it for me personally.