Sorry, I didn’t log into this account for a while.

Anyways, I guess in an ideal world the window management could be done fully via the window manager. In practice this doesn’t work too well, because that would require a more complex protocol than currently exists. For VSCode for instance, that would require disabling the native tabbing feature (but keeping the native splitting because otherwise I’ll end up with duplicated panes such as the file list) and implementing something custom to translate tab operations to sway-wm operations (in my case).

I guess it could work but it’s not supported OOTB, and after a lot of work is probably going to end up being a lot more clunkier than what I have going on in vim.

You mean a whole different window at the OS level? That’s just a way inferior hack to the way vim does it by default.

I’ve found an issue from 2017 about it and this related one that focuses more specifically on supporting vim-like behavior. This is just, fundamentally, something that VSCode doesn’t implement simply because of technical limitations. The extensions that attempt to recreate this behavior are apparently all quite janky.

I mean I don’t care, I’m very happy with vim now. But the terribly naive tab support is the reason I left vscode for vim initially. People who have only known “vscode-like” tabs don’t know what they are missing out on.

No, literally have one tab with multiple windows inside it (the default for vim).

  tab 1  |   tab 2   
w1 | w2  | w1 | w2
w3 | w4  |    w3   

Electron has other drawbacks than performance as well.

The big one for me is that my workflow is based on vim, where you split tabs into buffers. There is no way to split a tab into windows in VSCode. Only windows into tabs, which is super dumb and annoying because related files are never shown together unless you click a bunch of tabs. Apparently the reasoning for this insane behavior is “yeah well electron is based on chromium so tough luck we can’t do shit”.

Yep, it’s basically the best environment for them. Presumably relatively few writes compared to the uptime, in a case with few vibrations (!), very few power cycles (!!!). Basically all it does is spin on a highly precise bearing.

Anyway drive lisepans only matter for cost projections, when it comes to data integrity you should ALWAYS assume that a drive ia about to fail. Because sometimes it fails after 2 years and sometimes it runs for 20, that’s just the luck of the draw.

Reddit has had extremely spotty reliability forever. It got better in recent years, but still came down every few weeks, or would just randomly say “you broke reddit!”. Circa 2015 every evening it would just randomly return 50x errors a good chunk of the time because it was always overloaded.

Backend reliability mustn’t be very high up their priority list. Well, neither is UX (old OR new reddit), and let’s not pretend that they’ve been masterminds when it comes to ad placement either, so the real question is what do the higher ups want, and why can’t they achieve it?