It has been around for a long time, way before WSL came onto the scene. CygwinĬygwin is currently my number one choice when it comes to setting up a *nix environment on Windows. I have used vagrant before, but I abandoned it because I more-or-less transitioned to focusing my development efforts on an actual Linux machine. While WSL is gaining a lot of traction and appears to be popular, I haven't really explored it, and I am not quite ready for it at the moment. I am one of those developers, and I think Microsoft has realized this, otherwise they wouldn't have introduced WSL. It has often been said that many developers prefer and recommend UNIX-like systems. □ *nix Environment and Console Emulator □️ For example, I use inkscape for vector graphics – It is cross-platform and is licensed under the GNU General Public License, v2. With most of the software that runs on Linux being Free and Open Source (FOSS), I have naturally become inclined towards FOSS, and this has also influenced my typical Windows setup. If I was doing something on my Linux notebook and needed to continue on a Windows workstation (and vice-versa), I should be able to hit the ground running without having to jump through hoops just to get things working as expected. I therefore ensure that my BASH scripts will also run on Windows, and that I am able to use the same set of CLI tools that I'm accustomed to (e.g. I often write custom BASH scripts, and use the CLI a lot.This is the same for pyenv, which also has a windows port. Fortunately, someone ported it to Windows, and the windows port provides the same functionality. However, virtualenvwrapper isn't supported on Windows. I use virtualenvwrapper for managing my Python virtual environments.setting up similar (dev) environments, including tools and toolchains, etc.using similar software (which means choosing cross-platform applications that run on Win/Linux/Mac OS X, for example, VS Code, LibreOffice, VLC media player, etc.).My approach towards achieving this involves Therefore, it becomes imperative for me to ensure that there is a certain level of uniformity / similarity across the different computers that I use, despite differences in OSes and hardware. For example, I am so accustomed to the "hot corners" in the GNOME shell, to the extent that I sometimes move my mouse to the left corner of the screen when I am on a Windows Computer, and expect to see the Activities overview! The challenge of working on different machines at different times means that one has to adjust his/her workflow depending on the constraints and limitations imposed by a machine. General Approach and Underlying Principles □ So, in this post, I'll give an overview of my typical Windows setup from a developer and Linux enthusiast's perspective. In fact, my custom-built PC runs Windows 10. However, I have been using Microsoft Windows for a long time, and I still use it everyday, particularly at work (which has nothing to do with writing code!). In my previous post, I focused on my personal journey and experience with Linux, which has become my default OS on my personal laptop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |