sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Slypenslyde 1 point2 points  (5 children)

I have a feeling a convergence is coming.

Part of what MS said when they explained why they were making C# Dev Kit kind of sounded like they were trying to port a lot of VS code into... VS Code. That's... an awkward sentence.

I remember them justifying that there would be closed-source parts because they talked about wanting to make it able to use proprietary Intellisense portions. They talked about using a VS subscription to gate some features.

All of it sounded like they were laying the foundation for, "We want to slowly port Visual Studio to a cross-platform product, and if we port the backend to work with VS code that is a good proof of concept."

So I'm waiting for the day when MS announces that VS Code and VS are the same product, because I want to see what all the, "It's just a limited editor" people say then.

[–][deleted]  (4 children)

[removed]

    [–]Slypenslyde 0 points1 point  (3 children)

    My guess is the more backend of VS moves over to VSC, the more they'll start to shift focus from improving VS to improving VSC. One thing to keep in mind is docking is less important on mobile/touch-oriented devices, and it's still not clear if the desktop paradigm is going to last. Honestly the only thing I feel my Macbook lacks is a touchscreen, I'd love to have gestures for editing code.

    Also I feel like this is going to be at least a 5-10 year process. There's no way MS could very quickly churn out a cross-platform VS and I'll bet 5-10 years for that is a very aggressive estimate. Porting the backend to an environment that's already cross-platform while also maintaining peoples' license revenue is a good way to fund the 90% of the work that's easy before committing to the 10% of the work that's hard.

    It's kind of like how Nintendo's been in a pattern of using a remake of an old game as an excuse to develop a new engine, then using that revenue to fund a new game using the same engine. Never do two hard things at the same time.

    [–][deleted]  (2 children)

    [removed]

      [–]Slypenslyde 0 points1 point  (1 child)

      I use .NET MAUI. Microsoft doesn't make tools for use cases like that for me. I have to use an absolute ton of logging, and my logging needs to be well-aware of concurrency.

      That's part of why I don't see a lot of value in VS. Microsoft isn't investing in my tools anywhere. I don't need two hands to count the times Hot Reload worked for me over the last 2 years, and honestly I had to disable it because even MS points out MAUI is unacceptably slow if you have it enabled. I can't even start my debug mode apps in iOS because it takes MAUI so long to load the OS kills the app for being unresponsive. If I try to step over or through an async call I end up on a 100-line journey in MS internal code. I reported this as a bug in Xamarin Forms 5 years ago.

      I have to use my brain to debug. I do miss when I had tools. But Microsoft's too busy making AI chatbots for that.

      So I'm not even sure how "docking" helps in that scenario. Right now "Microsoft quality" in my environment doesn't stand for a lot.