Skip to content

Comment on Microsoft is putting Windows on the back burnerparent

Comments

I think you mean conhost (cmd is the shell program, not the terminal). It does have it's rough edges but it's much improved from where it was only a few years ago and its far from the only way to host a WSL session. This includes support for ANSI escape codes (TERM=xterm works fine) and better colors (though you may need to reset the defaults if you're upgrading from an old system). Lastly, there are plenty of other terminal apps which make this much more familiar for folks who prefer things like tabbed windows, or theming.

A second point, WSL programs don't rely on an active conhost shell to keep running. You can kick them off and run them in the background just fine. On one of my machines, I have a full i3 session running with no conhost window in sight. Everything works seamlessly, I can talk to my editor running as a Windows app, cut & paste back and forth, see file change notifications, hook up my docker command with my docker for windows VM, and so on. It's nice enough that I miss it when on my Mac and get annoyed with some of the fussy application alternatives on the typical Linux desktop.

I use a native linux box for most things, but I do have a windows PC for time wasting stuff. WSL is very close to being a good enough for most of my uses. It is an impressive product.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.