The good, the bad and the ugly. Why I like and hate a few of the IDE's out there.
July 18, 2017
The good, the bad and the ugly. Why I like and hate a few of the IDE's out there.
Score 8 out of 10
Vetted Review
Verified User
Software Version
Enterprise
Overall Satisfaction with Visual Studio IDE
Currently, our .Net developers are using Visual Studio Enterprise, but developers programming with other languages are use other IDE's such as Eclipse and PyCharm. We have MSDN subscriptions already for various needs, so Visual Studio was available for no extra cost which is why I think it was being used at the start of the company.
- I liked how easy it was to install and use many different libraries. I found it fairly easy to find what I needed and to add into my projects.
- There is a lot of community support, so it's usually easy to find someone else who has run across the same problems and has possible solutions.
- Because of our MSDN subscription, we had support from Microsoft when we got into very tough situations that we could not figure out ourselves or from the general community.
- I would like to see better performance meaning faster start-ups and overall operation. We are using a version that is a few years old and I hear the newer version is much better.
- I find working with TFS for version control to be a little (ok, a lot) difficult at times. Our company is moving to Git and GitHub and I would like a better transition to use that. Again, from what I hear the newer version of Visual Studio is much better in this area.
- I've had intellisense stop working for who knows what reason. I've had to close my project/solution and restart to get it working again. There may be an easy fix, but this is how I get around it.
- I haven't had direct involvement with the cost of Visual Studio versus its' return value. What I can say is that our company needing to have MSDN subscriptions for other reasons made this a non-issue. Visual Studio was already included in our package for no extra cost.
- I could see a start-up may not want to go the Visual Studio route at first. There are too many good open source and free IDE's to use.
- To offer up a positive impact, if your company is a Microsoft shop and use Microsoft throughout then using Visual Studio is going to help your team. It's better to use tools that are well integrated with each other than to piece together different tools that may or may not play nicely with each other. With that said, integration is the name of the game these days and there are many choices in the free world that work great.
Eclipse: I did not have a good experience with Eclipse when I started to code in Python. I chose Eclipse because that's what the person doing my Python training was using and I used it to follow along better. I found it difficult to figure out how to get my environment setup and there wasn't much help with errors and intellisense. Maybe I got spoiled with Visual Studio, but that was my experience with it.
PyCharm: I have found PyCharm to be great! I don't have anything bad to say about it. It's been straightforward to setup and answers are easily found out in the community when I run into problems. I like using it with Python, but I would probably still want to go back to Visual Studio if I was coding in C# again.
PyCharm: I have found PyCharm to be great! I don't have anything bad to say about it. It's been straightforward to setup and answers are easily found out in the community when I run into problems. I like using it with Python, but I would probably still want to go back to Visual Studio if I was coding in C# again.