Also, systemd is still pretty sketchy. It takes over 2 minutes for systemd services to start and if you close a WSL 2 terminal for just a few minutes systemd will delay a new terminal from opening for quite some time. This basically means disabling systemd to use WSL 2 in your day to day.
That doesn't sound good. I was planning to set up a Windows/WSL2 box, but this gives me second thoughts. Where can I read more about this?
It's still ok even without systemd. Technically systemd is disabled by default, you have to turn it on with systemd=true in /etc/wsl.conf.
I can't find a definitive source with an open ticket but if you Google around for "WSL 2 systemd delay startup" you'll find assorted folks talking it about with a number of different reasons.
I just went by my end results of there is a delay with systemd enabled and no delay with it disabled.
True, I use the web version of Office when it makes sense. I only reserve an actual desktop for things like Word because it doesn't work as well in the browser. I'm not a heavy Office user though, so YMMV.
I'd say that depends on the complexity of the page but yeah, it is a real possibility. What tools like Astro (and also the recent Vue 3.5) provide here is an escape hatch in the form of opportunistic/lazy hydration and rendering. Just yesterday I shaved 200ms off of my hydration time by converting a Vue component to an async component that gets hydrated upon interaction.
I couldn’t help but notice that he was working with two extremes, ruby and rust. A nice middle ground could have been nodejs with TS, with the advantage of using a single language throughout the project. While nodejs doesn’t have something like rails, its ecosystem is largely centered around building web applications.
It was several years ago I’ve read it, but GNUCash’s documentation does actually start with some generic accounting knowledge, which I have found quite useful at the time.
No sync issues, no freezes. Your code editor/tools/coding happens in a single computer.
VScode remote extensions are really good though, the best of any GUI editor. But that BLOB it installs on remotes can take a good chunk of scarce VM RAM.
Besides persistence, terminal multiplexing is one of the greats things of tmux. If I'm programming on a remote machine I don't want to open a new ssh connection from each of the five terminals that I need. Seems tedious when I can just create a new window inside tmux. Even locally, I don't want to have 10 terminals opened (or tabs), tmux lets you have multiple terminal windows/panes from a single physical terminal and lets you easily group and switch between them into what they call sessions.
The problem is that because I use tmux so heavily locally, using it remotely is a pain in the ass.
My normal workflow is either to be sitting in front of my Linux machine, or SSH'd to it (from a Windows laptop). Tmux makes the transition between those two seamless. But nesting tmux doesn't work.
Peak HN comment
reply