Under the hood we run WSL.exe and provide the whole path to the Python interpreter and to this script and so on. And so users can now launch the WSL processes directly. And connect to each and they connect to any other remote server.Īnd I believe a couple of years ago, we switched to a new approach. Ilya: So user had to run open SSH server inside of WSL. He’s one of the people who works on the remote interpreter team, which supports WSL in P圜harm, along with Vladimir as well as, Alex. Ilya: Well, we started to support WSL as a remote interpreter via SSHīecause at the time it was the only way to support it. Today I sit down with three people behind our WSL support and ask them some tough questions because a lot of people really want better support for WSL on P圜harm. This is Early Access P圜harm with your host Nafiul Islam. Nafiul: Hello, all you beautiful P圜harmers. It will implement some basic things such as docker support and remote interpreters, as the year progresses, we hope to add further support for WSL and bring it on part with all other remote targets. Our plan is to implement the Targets API in 2021 although we’re still working through a few issues that arise from the implementation.
This also means that when complete, cloud providers will have an easier way of adding all kinds of functionality, and editing should become as fluid as editing on the filesystem itself (or so we hope). Through this approach, we can indeed pave a way for all future remote targets, but it means that the transition to this API will be gradual, as a lot of the current functionality will need to be re-written in order to take advantage of this. So, for example, if you wish to add direct support for Docker or WSL, you will need to fill out the entire matrix of behaviours that can be done from the IDE. If you want to support a new remote, then you need to start filling out that matrix, and you need to provide answers to how the IDE will handle different scenarios. This means that the way to support interpreters will also change fundamentally it also means that there is a lot of refactoring involved. Now, we use the term “remote” loosely here, because to us, a remote is anything that is not the file system or the operating system that P圜harm is running on. This new system provides a layer of abstraction over all remote hosts, whether it is WSL, an AWS, GCP or any other machine for that matter. This is why, we began working on a project called “Targets”. This means WSL, but also includes any host on a remote machine and that we would not have to build custom implementations for things like WSL from scratch. However, taking a deeper look at this, we begin to see the core of the issue, and that is we need to have a way to support remote development in a better way. This means that whenever you make changes, there will be delays before you can immediately run it. This is why, we have a copy of the files on your local machine, which is then uploaded via SFTP. IntelliJ expects that it is working with a real file system, and in the case of remote machines, you don’t have a real file system. However, the biggest problem stems from a limitation of the IntelliJ platform at the time.
At the same time, we were dealing with technology that was not our own, and we needed to be careful about building support that would need to be re-done. However, we needed to make sure that we could adapt to changes in WSL. WSL showed tremendous promise for people who wanted to develop on open source technologies. We needed to do this because this was the only way in which we could support WSL at the time. We initially used SSH and SFTP to run commands and transfer files. WSL is currently supported directly via wsl.exe. However, the issue is not with the support itself, but rather how it is supported. So, the question is, why is this taking so long to implement?Īs things stand right now, WSL and WSL2 are both supported on P圜harm. When I say it’s “the one”, it’s because this is the probably the most famous ticket with regards to WSL in our tracker. It’s the one about WSL support in P圜harm, and by extension, the rest of the JetBrains IDEs. Over the course of two years, the ticket has accrued over 130 votes. Over the past few months, I’ve been monitoring a ticket closely.
0 kommentar(er)
