skiko VS fzf.vim

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.

Fuzzy Finder: fzf.vim (for its speed) along with telescope.nvim (for its ecosystem)

https://github.com/junegunn/fzf.vim

And added my keyboard shortcuts.

There are two plugins allowing us to use fzf in Vim: the native fzf plugin directly installed with fzf, and fzf.vim. The second plugin is built on the first one.

You might be interested in installing the fzf-vim plugin [0]. It has a user-defined command :Maps which can be used to search through all keybindings (you can also do this with just :nmap in vim, but the fzf interface is much nicer). It also provides :Commands. This behaves remarkably like VSCode's command palette.

[0] https://github.com/junegunn/fzf.vim

You'll also need https://github.com/junegunn/fzf.vim (which is imo the only vim plugin that's a must).

I do all my file operations from the command line. But to open and search files I use fzf

Regarding plugins , I am using https://github.com/Donaldttt/fuzzyy because it works in windows, unlike https://github.com/junegunn/fzf.vim

There's a :Buffers command in fzf.vim that I use extensively. It opens a fuzzy-find window with all open buffers in a MRU list.

Thanks to fzf.vim and fzf-lua, everything I learned and copied is from them.

they're likely referring to fzf.vim, the vimscript plugin from the original fzf author that wraps around fzf. there's also fzf-lua nowadays.