The UI has always felt slow and clunky to me, which may just be my perception, although when I read blog posts like this one from Bruce Dawson I feel a bit vindicated. Still, for me, I just don’t find Windows to my taste. (Keep in mind I was using WSL back in 2016-2018 though, and I’m told it’s improved since then.) npm install would take orders of magnitude more time on WSL compared to the equivalent Mac or Linux machine. For me, though, I don’t do much PC gaming, and my experience with WSL is that although compatibility was excellent, the performance was poor. This is definitely a viable option, and totally reasonable, especially if there’s that one Windows program you really need (or you’re a PC gamer). Since the command line is the main selling point of Linux (IMO), it’s tempting to just use Windows with the Windows Subsystem for Linux instead. I set my terminal to automatically open tmux on startup.Īh, the command line on Linux. As an added bonus, tmux also runs on Mac, so if you learn the keyboard shortcuts once, you can use them everywhere. I found the simplest solution was to use tmux instead. If you’re a Mac user, the hardest part about switching to the Linux terminal is probably just going to be the iTerm keyboard shortcuts you’ve memorized to open tabs and panes. incompatible versions of grep, tar, and sed with slightly different flags, so you have to brew install coreutils and use ggrep and gtar… ugh), then you know what I’m talking about. If you’ve ever run into headaches with subtle differences between the Mac and Linux shell (e.g. I know that my shell scripts will run exactly the same on all these environments. All my servers run Ubuntu, as do my Travis CI tests, as does my desktop. Using Linux as your desktop machine just makes things that much simpler. So eventually your code is going to have to run on Linux. Even if you’re not doing much sysadmin stuff, you’re probably using Linux to run your test and CI infrastructure. The main reason should be clear: if you’re writing code that’s going to run on a server somewhere, that server is probably going to run Linux. I tend to live and breathe on the command line, and for me the command line on Linux is second-to-none. OK so enough history, let’s talk about the good and the bad about Linux in 2020, from a web developer’s perspective. (At least, the ones I care about I’m sure you can find a counter-example!) The biggest gripe I have nowadays is with fonts, which is a far cry from fiddling with WiFi drivers. And since it seems everything is either an Electron app or a website these days, it’s rare to find a consumer app that doesn’t support Linux. On my Dell XPS 13 (which comes with Ubuntu preinstalled), WiFi and multi-monitor work out-of-the-box. I’m happy to say that none of my old Linux headaches exist anymore in 2020. Then I became a dual Windows/Mac user when I joined Microsoft in 2016, and I didn’t consider Linux again until after I left Microsoft in 2018. ![]() I recall running Netflix on Firefox in Wine because this was the only way to get it to work.Īround 2012 I switched to Mac – mostly because I noticed that every web developer giving a conference talk was using one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |