GNU Emacs is described as a free extensible and customizable text editor for the Lisp programming language.
N/A
Visual Studio
Score 9.0 out of 10
N/A
Visual Studio (now in the 2022 edition) is a 64-bit IDE that makes it easier to work with bigger projects and complex workloads, boasting a fluid and responsive experience for users. The IDE features IntelliCode, its automatic code completion tools that understand code context and that can complete up to a whole line at once to drive accurate and confident coding.
I have used several different IDEs and editors, but I keep coming back to Emacs. I guess my fingers are wired for Emacs and I find that I can do pretty much anything in the tool that I can with other tools. Some other tools are more polished, but are specific to certain …
Emacs is best utilized on a Unix system where it can be easily installed and accessed. It allows for quick editing of files on a system whether you are accessing it locally through the console or remotely via an ssh connection. Once users familiarize themselves with the Emacs shortcuts, it becomes a pretty efficient text manipulation program. On a standard Windows computer, it is less likely to use Emacs for code editing, especially if you have a local repository on your host machine.
It's useful for app development, debugging, and testing. I've been using it for two years and have seen it grow into a fantastic tool. All of the features, NuGet packages, and settings that enable different types of projects are fantastic. It also has a connection to Azure DevOps and Git. It's a fantastic product that's simple to use.
GNU Emacs is a text editor that can do almost anything that you want to do with it. It is fairly easy to extend the functionality using Emacs Lisp with a large library available.
It can be easily customized using themes as well as custom code to change the look and feel as well as how everything works.
Since Microsoft offers a free Community Edition of the IDE many of our new developers have used it at home or school and are very familiar with the user interface, requiring little training to move up to the paid, enterprise-friendly editions we use.
The online community support for Visual Studio is outstanding, as solid or better than any other commercial or open-source project software.
Microsoft continuously keeps the product up to date and has maintained a history of doing so. They use it internally for their own development so there is little chance it will ever fall out of favor and become unsupported.
Emacs is old, so it's a little crufty and not too easy to pick up and start using. There is a community package called Spacemacs that simplifies a lot of things that you do with Emacs. It is probably better suited to beginners.
Sometimes, the choices that were made to integrate certain functionality change the basic models for that functionality. This is seen primarily in the version control system support, where multiple version control systems are supported and "unified" to a standard Emacs-y way of doing things. This can be confusing to the new user not familiar with the Emacs way.
Emacs has, as its foundation, a lisp interpreter. This means that the extension language for Emacs is emacs-lisp. Some people find lisp hard to understand and have difficulties writing Emacs extension code, or understanding existing code.
Certain settings and features can sometimes be challenging to locate. The interface isn't always intuitive.
Sometimes there are too many ways to do the same thing. For example, users can quickly add a new workspace in Source Control Explorer when a local path shows as "Not Mapped," but it doesn't indicate that the user might want to check the dropdown list of workspaces. The shortcut of creating a new workspace by clicking on the "Not Mapped" link can lead to developers creating too many workspaces and causing workspace management to become unwieldy. If the shortcut link were removed, the user would be forced to use the Workspace dropdown. While it can add an extra step to the process, workspaces would be managed more easily, and this would enforce consistency. At the very least, there should be a high-level administrative setting to hide the shortcut link.
VS is the best and is required for building Microsoft applications. The quality and usefulness of the product far out-weight the licensing costs associated with it.
The thing I like the most is Visual Studio doesn't suffer from Microsoft's over eager marketing department who feel they need to redesign the UI (think Office and windows) which forces users to loose large amounts of productivity having to learn software that they had previously known.
Everything that you need to know about Emacs can be found on the internet. There are many Emacs "cheat sheets" that list out all of the shortcuts for Emacs. There are videos on how to use Emacs. Emacs is easily installed using the standard Linux package managers and can also be easily updated through them as well. There are tutorials on how to customize Emacs to your liking.
Between online forums like StackOverflow, online documentation, MSDN forums, and the customer support options, I find it very easy to get support for Visual Studio IDE when I need it. If desired, one can also download the MSDN documentation about the IDE and have it readily available for any support needs.
Of course, Vim is a good contender for comparison as well, so I'll include it. I find Emacs much easier to learn, which will help speed up productivity for newer users. It seems much faster than VIM and VSCode, especially under load. It's highly highly customizable, in ways other editors don't stack up against. Its lack of bloat also is a nice addition to a great product.
I personally feel Visual Studio IDE has [a] better interface and [is more] user friendly than other IDEs. It has better code maintainability and intellisense. Its inbuilt team foundation server help coders to check on their code then and go. Better nugget package management, quality testing and gives features to extract TRX file as result of testing which includes all the summary of each test case.
We've had hundreds of hours saved by the rapid development that Visual Studio provides.
We've lost some time in the Xamarin updates. However, being cross platform, we ultimately saved tons of time not having to create separate apps for iOS and Android.
