immozuloo.blogg.se

1. ALACRITTY WSL2 INSTALL
2. ALACRITTY WSL2 UPDATE
3. ALACRITTY WSL2 MANUAL
4. ALACRITTY WSL2 WINDOWS 10
5. ALACRITTY WSL2 SOFTWARE

On OS X / Linux there's a great choice between the built in defaults, iTerm 2 (Mac) or others such as Alacritty (cross platform). One of my major sticking points for Windows was the lack of a good terminal application.

ALACRITTY WSL2 MANUAL

This process is a bit manual and takes a few minutes as some of the steps require a restart of your machine, but it's just a case of following the instructions carefully and you'll be up and running. The docs mention that if you're on the Windows Insiders build, you can use the experimental wsl -install command.

ALACRITTY WSL2 UPDATE

It's got a fair few steps - you first have to enable WSL 1, then upgrade to WSL 2 (I'm not sure if in time this will change), then download a kernel update (far less scary than it sounds), before setting the default version to WSL 2, and finally then installing Ubuntu.

I followed this guide on the Microsoft site. I run the Ubuntu distro on WSL 2, but these steps should be the same regardless of which distro you'd like to run. I'm a big fan of 1Password for storing all my passwords and the main way I access it is via the Google Chrome extension, so my first port of call is to download Chrome and sign in so all my extensions, including 1Password, get synced.

ALACRITTY WSL2 WINDOWS 10

Many downloads and restarts later, I had a fresh, up to date Windows 10 all ready to go.

ALACRITTY WSL2 SOFTWARE

That was a super smooth process, but left me with a Windows that was over a year out of date, so the first thing I did was let the software updater do its thing. That let me do a factory reset of the machine and left me with it running the same version that it was when it first shipped to me.

ALACRITTY WSL2 INSTALL

You can install Windows however you like my XPS came with a recovery disk, which I got at via "Reset this PC" in System Settings. Spoiler: there actually aren't that many! Reinstalling Windows 10 Given all the experimenting I'd done when I first got the laptop to get WSL 1 installed (I had to install a Windows Insider build to get it, whereas now WSL is available on the regular build), and the fact that the laptop was a bit bogged down with various bits of software and accumulated "stuff", I decided last week to completely reformat the machine and start a fresh.įor my future reference, for when I do it again or get a new machine, and for others who may be interested in doing software development on Windows 10, I decided to document the steps I took. Additionally, WSL 2's architectural changes enable it to run many, many more apps, so using tools like Docker is now possible.Īnd, you could upgrade a WSL 1 install to WSL 2, so the upgrade path was super smooth! Starting fresh I haven't benchmarked, but running WSL 2 feels so much snappier and I don't feel a noticable delay when running a large npm install. This comparsion on the MS site shows all the differences, but the highlight for me was that file IO performance was drastically improved - the docs quote 2-5x faster for running tools such as git or npm. I can't go into the details of the implementation, because frankly it's way over my head, but from the learnings of the successes and failures of WSl 1 Microsoft were able to make amazing improvements in WSL 2. WSL 2 (see an intro video here) promised major improvements over WSL 1. Not much, and not often, but everything wasn't quite as smooth as it would be on the MacBook I usually worked on.

WSL 1 also had some holes in terms of application support, you couldn't use Docker - not something I do regularly, but something that's useful to be able to reach for - and at times I found the VSCode WSL integration to be slightly laggy. You might think this isn't a huge deal - but if you're running a package manager like npm and installing a bunch of dependencies, those reads and writes add up to the point where it's noticably slow (and I'm running on a fairly beefy XPS laptop). The main one was that WSL 1 was known to be much slower at file reads and writes. That said, there were some minor issues and frustrations with WSL and this workflow. By using the Windows Subsystem for Linux (WSL), I was able to run most of my tools effectively in Linux, something I'm familiar with, and with VSCode's WSL Remote plugin, I could run VSCode in Windows connected to the Linux environment provided by WSL, and things felt very familiar. DecemSoftware Development on Windows 10 with WSL2īack in October 2019 I'd taken the plunge and tried Windows for my development work.