Long Live Visual Studio
-
VS has existed for a few decades now, you'd *hope* it would be pretty good by now. The problem with VS as I see it is that they keep throwing in new features, but long-standing bugs remain. Frankly I'd rather have MS spend a few months doing nothing but addressing known issues, with no new feature, to bring everything up to speed...and maybe then go back to adding new features.
-
VS has existed for a few decades now, you'd *hope* it would be pretty good by now. The problem with VS as I see it is that they keep throwing in new features, but long-standing bugs remain. Frankly I'd rather have MS spend a few months doing nothing but addressing known issues, with no new feature, to bring everything up to speed...and maybe then go back to adding new features.
It's all about marketability and trying to be seen as relevant. There's no marketing value in fixing problems that should have been fixed long ago, but there is in trumpeting "new features". Something I noted about C# -- each new release has 5% or 10% of the new features that are actually useful. The remainder is marketing and the C# dev team ensuring their next paycheck.
-
A few days ago, Code Witch expressed a rather low opinion of the Eclipse IDE. And someone commented that they think Visual Studio is very good. Well I can say that I'm liking Visual Studio because I just moved a file from one folder to another by dragging it, and upon dropping the file, it asked me if I wanted it to adjust the namespaces for the classes inside the file! Nothing could have been more appropriate or helpful at the time. Viva La Visual Studio!
The difficult we do right away... ...the impossible takes slightly longer.
I used the predecessor of Visual Studio, 16-bit Visual C++ 1.0 with MFC 2.0, back in 93. Before that it was MS C/C++ ver 7, and Turbo Pascal. IMHO, VC++ 6.0 which came later was such an excellent IDE to live and work in. These days, working in VS2017, having gone thru all those versions, I miss some things. VS2008 is still a fav, the way the child windows work is much more productive than later versions. Yes, I'm old.
-
A few days ago, Code Witch expressed a rather low opinion of the Eclipse IDE. And someone commented that they think Visual Studio is very good. Well I can say that I'm liking Visual Studio because I just moved a file from one folder to another by dragging it, and upon dropping the file, it asked me if I wanted it to adjust the namespaces for the classes inside the file! Nothing could have been more appropriate or helpful at the time. Viva La Visual Studio!
The difficult we do right away... ...the impossible takes slightly longer.
-
I used the predecessor of Visual Studio, 16-bit Visual C++ 1.0 with MFC 2.0, back in 93. Before that it was MS C/C++ ver 7, and Turbo Pascal. IMHO, VC++ 6.0 which came later was such an excellent IDE to live and work in. These days, working in VS2017, having gone thru all those versions, I miss some things. VS2008 is still a fav, the way the child windows work is much more productive than later versions. Yes, I'm old.
I remember using Turbo Pascal rev 1.0 on an Osborne "luggable." What a joy that everything fit on the double-density upgraded 180K (I think it was) floppy! Even better that I could open the floppy drive & remove the disk so that any bugs (yes, there were a few....) in the switch-the-memory-bank-to-access-some-hardware code had issues.
-
It's all about marketability and trying to be seen as relevant. There's no marketing value in fixing problems that should have been fixed long ago, but there is in trumpeting "new features". Something I noted about C# -- each new release has 5% or 10% of the new features that are actually useful. The remainder is marketing and the C# dev team ensuring their next paycheck.
BryanFazekas wrote:
There's no marketing value in fixing problems that should have been fixed long ago, but there is in trumpeting "new features".
I'm not entirely disagreeing - VS, despite its warts and all, is still the best at what it does. But imagine the amount of goodwill they'd get if only a group of people were assigned the menial task of fixing known issues.
-
I remember using Turbo Pascal rev 1.0 on an Osborne "luggable." What a joy that everything fit on the double-density upgraded 180K (I think it was) floppy! Even better that I could open the floppy drive & remove the disk so that any bugs (yes, there were a few....) in the switch-the-memory-bank-to-access-some-hardware code had issues.
Turbo Pascal was such a pleasure. Now I use C# and thank Anders Hejlsberg for both. Kinda funny I started my coding career and will be ending it with two of his inventions.
-
BryanFazekas wrote:
There's no marketing value in fixing problems that should have been fixed long ago, but there is in trumpeting "new features".
I'm not entirely disagreeing - VS, despite its warts and all, is still the best at what it does. But imagine the amount of goodwill they'd get if only a group of people were assigned the menial task of fixing known issues.
dandy72 wrote:
But imagine the amount of goodwill they'd get if only a group of people were assigned the menial task of fixing known issues.
You're preaching to the choir ... I've been on a few projects where similar decisions were made ... didn't understand it then, don't understand it now.
-
A few days ago, Code Witch expressed a rather low opinion of the Eclipse IDE. And someone commented that they think Visual Studio is very good. Well I can say that I'm liking Visual Studio because I just moved a file from one folder to another by dragging it, and upon dropping the file, it asked me if I wanted it to adjust the namespaces for the classes inside the file! Nothing could have been more appropriate or helpful at the time. Viva La Visual Studio!
The difficult we do right away... ...the impossible takes slightly longer.
I started with a Apple /// and basic not sure I had a IDE Moved to Microsoft and obtained a copy of Visual Basic 6 Professional new in the box for $50.00 all I knew was that was a great price So when support went away for VB 6 I wanted to write for Windows with JavaFX Only two IDE's were NetBeans and Eclipse. Had two computers so Eclipse on one and NetBeans on the other. Learning curve with Eclipse was steep compared to NetBeans JavaFX was abandoned by a company I despise Oracle Moved on to Visual Studio 2019 what a joy other than all the junk it puts in my Temp folder it has YES been a joy to use. Multiple platform support FREE on my OLD OS Windows 7 64bit
-
dandy72 wrote:
VS has existed for a few decades now, you'd hope it would be pretty good by now.
I like VS. Better than other IDEs that I have tried. But VI has existed since 1970. I keep hoping but it remains miserable.
-
A few days ago, Code Witch expressed a rather low opinion of the Eclipse IDE. And someone commented that they think Visual Studio is very good. Well I can say that I'm liking Visual Studio because I just moved a file from one folder to another by dragging it, and upon dropping the file, it asked me if I wanted it to adjust the namespaces for the classes inside the file! Nothing could have been more appropriate or helpful at the time. Viva La Visual Studio!
The difficult we do right away... ...the impossible takes slightly longer.
I agree 100%. I have used the MS development IDE since they introduced it in Visual Basic in 1991, then forward into Visual Studio for .NET around 2000. The main thing VS needs is a visual designer functionally on par with the existing one for WinForms (which dates back to VB in the 90s and updated well over the years) to bring that same rapid application development (i.e. drag and drop UI building) to MAUI, WinUI3, and Blazor. Components like "Hot Reload" don't even come close to improving the productivity and quality of the UI like a visual designer does. Without visual designers, just how "Visual" is Visual Studio?
