To my surprise with minimal effort it sprung to life. Next I grabbed the IntelliJ tarball and unzipped it and launched it with this command: export DISPLAY=$(cat /etc/nf | grep nameserver | awk ''):0.0 It loaded fine, with no major changes to the default installation so that was a good start. So I got X410 installed and tried running what everyone should run on an X server, xeyes. I'd been told X410 was worth the £5 or whatever it cost in the Marketplace so I figured it was worth getting. I use Ubuntu for nearly all my cloud and desktop work, so having an Ubuntu distro which gives me what I'm used to on native Linux but in WSL was great, even with a few tweaks to get Snaps and Juju running. So, how can I make development smooth again? How can I get back to where I was when I was doing this on a native Linux box or OSX? How do I get IntelliJ running in WSL2?įirst up I needed a Linux distribution and X server, there are a few of both available. It wasn't a good use of my time for project stuff, its not my day job, where I might be getting paid to fix stuff, I'm doing these projects because I enjoy coding, not fixing IDE's. I mean it wasn't like the worst experience ever, but things took time for me to figure out, fix, stop errors, restart and so on. It felt like I'd just downgraded from a Porsche to a Ford Focus. Code completion for different languages failed, plugins were clunky. So for 2 weeks I tested VS Code, but stuff just didn't work. But WSL obviously has some Windows native vs WSL app tradeoffs and I wanted to test Microsoft's VS Code as it had WSL support on the Windows side to run stuff inside the WSL container, which I thought was pretty cool. A Porsche vs a Ford Focusįor years I've been an IntelliJ user, on Mac and Linux its generally just works. Knowing I could run stuff, the networking was pretty sane and now WSL had some support for GUI apps I figured I could at least give it an extended run as a multimedia editing machine coupled with a development box for hobby and part time projects. I was impressed, I had Ubuntu, Windows Terminal and my software all setup and running in nearly no time. Of course my benchmark was compiling my software, so I checked out some code and compiled it. So with the new laptop in hand I gave it a shot. I've been tracking the WSL work done by Canonical and Microsoft over the last year or two Hayden does a great job of advocacy, but hadn't tested it again, and not only was there WSL 1 there was now WSL 2 which offers far more native integration and support, rather than the terrible Linux -> Windows system call API shim that happened in WSL 1. So with that in mind, I didn't want to deal with dual booting Windows to Linux and back again for the Adobe suite, and I didn't want to deal with tradition VMs, none of it appealed. The problem wasn't the WSL experience itself, it was the disk I/O, it was the worst.įast forward a few years and I had a new laptop in my office as a way to do home projects, non NASA work projects and also deal with video and photo editing for my Youtube channels and photo sites. So we went back to a stock Windows Java toolchain and gave up on WSL within about an hour of starting. We then checked out the source code we were developing on and run a test maven compile. We installed a Linux distro, OpenJDK, Maven all the usual Java development tooling. A few years ago I had an intern working with me, and we decided to give WSL a go because I was doing development on Linux and Mac laptops and he rocked up with the latest Windows 10 laptops from Argos.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |