Git vs Visual Studio Code

Visual Studio Code became famous over the past 3+ years I believe. The clean UI, easy to use UX and the plethora of integrations made it a very easy decision for us. Our gripe with Sublime was probably only the UX side. VSCode has not failed us till now, and still is able to support our development env without any significant effort.

Goland being paid, as well as built only for Go seemed like a significant limitation to not consider it.

I decided to choose VSCode over Sublime text for my Systems Programming class in C. What I love about VSCode is its awesome ability to add extensions. Intellisense is a beautiful debugger, and Remote SSH allows me to login and make real-time changes in VSCode to files on my university server. This is an awesome alternative to going back and forth on pushing/pulling code and logging into servers in the terminal. Great choice for anyone interested in C programming!

We will use the ubiquitous combination of Git for version control and GitHub for code hosting. They have all the functionality we require for this project and will fit perfectly into our development workflow with up to three developers working simultaneously on the codebase. We also plan on using GitHub Actions to set up our CI/CD workflows.

VS Code will be our primary code editor due to its combination of developer-friendly features, including a large extensions library, IntelliSense code completion, Git integration, and powerful debugging tools. Furthermore, it offers better performance and more simplicity than full-fledged IDEs while supporting a multitude of languages.

Selenium will be used to perform automated testing of our web application. It supports all major web browsers and operating systems and supports test scripts to be written in multiple languages, including Python which we are also planning to use for our back-end, helping us to consolidate the languages required for our project. In addition, Selenium is free and has support for most CI/CD tools.