Earlier quoted context omitted.
I don’t know what you’re looking at, but time-to-start is a huge factor for me. If I’m using a program as a text editor (as opposed to an IDE), I want to be able to open a file, edit it, and then close it. When I heard JetBrains was working on a lightweight text editor, I was hoping for something I could use in this way, but Fleet takes 5 seconds to launch and auto-closes after closing all files. So I’m a little disa…
Fleet is not a text editor, it's a full fledged web-based IDE. I don't know what your workflow is, but my IDE generally stays open all day long and so startup is irrelevant. And if that web UI was to actually run remotely on some cloud server (gasp), the I assume that fresh instances of it could at least be pre-pooled for an even quicker "startup". If all I needed was a quick text editor, obviously I would stick with…
One entire core just for typing text and moving your mouse
If you use a laptop to code, it'll eat your battery in no time
If you compile programs, it'll slow down your builds
That's why i don't want no java on my computer or any other JIT based BS or slow tech stack like the JVM, wich was made for servers not for latency SENSITIVE programs such as a TEXT editor where i TYPE text and where i need my cores to BUILD or to do STATIC ANALYSIS