Since the initial announcement of Fleet, we have had an overwhelming amount of interest from all of you, with over 137,000 people signing up for the private preview. Our reason for starting with a clo
We are considering open sourcing parts of the product or the technology behind it. Stay tuned for details in the coming months.
open core non-commercial use… I would only use it if I had to… GNU Emacs still is the best.
Fleet is mainly written in Kotlin, which means it runs on the JVM. The UI framework is a home-grown solution using Skia (via Skiko). For those of you wondering why we didn’t use Compose Multiplatform: we started working on Fleet when Compose Multiplatform wasn’t available yet.
Furthermore, Fleet uses Rust for the Fleet System Agent, which is a process that runs on the target machine. It is used to build the project, run code, execute terminal commands, and perform other actions in the target environment on behalf of Fleet.
They are too invested on the JVM already… Webasembly ftw
Webassembly isn’t always the most efficient solution, e.g. when manipulating the Dom, JavaScript is usually faster.
If you take Webassembly as a replacement for the JVM on the server side, well, I can understand everybody who would like to wait for that piece of technology to mature a bit more. ;)
open core non-commercial use… I would only use it if I had to… GNU Emacs still is the best.
They are too invested on the JVM already… Webasembly ftw
Webassembly isn’t always the most efficient solution, e.g. when manipulating the Dom, JavaScript is usually faster.
If you take Webassembly as a replacement for the JVM on the server side, well, I can understand everybody who would like to wait for that piece of technology to mature a bit more. ;)