4 ms·
The number of us that run vscode is very high. Vscode is exceedingly performant & efficient. I doubt I lose 20 minutes of my 8+ hour runtime on those days I swi
by jauntywundrkind 3y ago
The number of us that run vscode is very high. Vscode is exceedingly performant & efficient. I doubt I lose 20 minutes of my 8+ hour runtime on those days I switch from Neovim to Vscode fulltime. It's just not a factor, and hemming & hawing is a waste of emotion. Being a fidgety worry-wort here is a waste of my vital life energy, would make my life worse.
Like any application, enough bad code can ruin a good thing. If you install a couple dozen extensions in vscode, there's some odds one or two will have a real impact on resource usage. And I think all codebases are like this: performance is fragile. It has to be cared for, ongoingly. Projects tend to become slower over time. It doesn't matter your stack, your technology: vigilance is required. Caring is required.
When people think of Electron, they think of Slack. (Or maybe Discord, but honestly it's way down on my list of cpu used versus other things, and it's <200MB RSS across dozens of servers & hundreds of rooms is tiny.) These form very strong preconceptions. I wont tell you you're wrong, but you need to think very clearly about what could possibly change your mind. There's a lot of people not open to the possibility that they're wrong, that Electron has no problem and is fine, or even worse of a locking-yourself-in tragedy, could ever possibly become fine. And that's a problem.
(I do wish we had a shared-library alternative to Electron, which would lower effective memory use heavily. Alas, alternatives like the well known Tauri use a woefully inferior Webkit2 engine, which is a cure far worse than the disease.)
- jemmyw 3y agoVscode does a ton of stuff though and it can perhaps justify it's electron with a broad set of features, the performance work they've put in to it and that being based on electron really helped their extension ecosystem. I don't quite see the same justifications for a terminal.
- jauntywundrkind 3y agoIf vscode can do so much and have such a slim profile, it's hard for me to grapple with the idea that we need to justify using the same technologies for a terminal. The impact is negligible, for a massive incredibly capable & superbly complex app. Many of us spend enormous times in our terminal. If we are going to likewise have a nearly negligible impact on battery life and memory usage, it feels like such an effete elite overconcern to fret about the technology. If Tabby can create a much more malleable flexible terminal that lets us explore possibilities quickly, at such a minimal cost, I think it would be foolish to spend time weighing & "justify" that price. We should explore what possibilities this opens.
- jemmyw 3y agoVscode doesn't have a negligible impact on battery life though. Depending on the project I'm working on it can be the most battery draining program. That's the cost of the features. Can a terminal justify those kind of features for the same exchange? I've tried various and settled on kitty.
- jauntywundrkind 3y agoWhat's your impact? For me, vscode under 5% difference in battery life (as per the math on my original post, 20 minutes across an 8 hour work day). With an 8 hour battery, that just doesn't matter to me. If we kept having to add up 20 minute penalties maybe we'd get somewhere, but I doubt we'd see that kind of direct add. The simple logic is: it's unlikely that multiple apps are both being heavily used. I just can't see it making a real difference for even 1% of people even 10% of the time. It's just not a real problem. I'd say there's too much clutching at pearls, but people have a right to be sad about bad apps, and there are bad apps built in Electron. Just like there are bad native apps that suck battery & have to be left on for work too, but people never credit in that consideration.
- jemmyw 3y agoIf I look at the top 10 CPU used time items for me, with an uptime of 14 days, it's 6 vscode processes and 4 macos processes (I count 15 other vscode processes in the whole list which seems insane!) Calculating battery usage is pretty hard, I can only go by the observation that I have 2 vscode projects. One is a rails app and vscode doesn't do a heap of stuff for ruby code, battery drops very slowly. The other is a typescript project and when I work on that my laptop steams through the battery, and I know its vscode because I see its usage go up as I edit files. It's not insignificant. As I said, vscode gives me a lot in return for this. It has 2 windows open. I've got 10 terminal windows open and kitty has 1 process. That is a program with actually negligible impact on battery life, lag, memory usage etc. If every program is electron then the problem compounds.
- 3y ago