Microsoft previews Visual Studio 2022 for Mac, but why bother when VS Code runs just fine on Apple hardware? Microsoft has pushed out another preview of Visual Studio 2022 for Mac, stating that it provides a "truly native macOS experience." The Mac version, like its Windows cousin, is needed for developing with the new .NET 6.0 SDK with C# 10, F# 6.0, and so on. As such, it is late. "We plan to release the GA version of Visual …
"Microsoft previews Visual Studio 2022 for Mac, but why bother when VS Code runs just fine on Apple hardware?"
Something about a full fat IDE being the *only* solution for a developer rather than a lighter text editor? Or at least that is the nonsense I used to hear before Microsoft also made their own lighter(???!) text editor.
If you stick a Microsoft brand on it; the consumers will flock!
Please Microsoft, make a flavour of n(vi) or Vim. I wan't to see people suddenly do a 180 on their opinions of what is "user-friendly".
Just tried it: ed is alive and, er, there by default on this Mint installation. And ex too.
I actually agree about vi, but you have to have at least a minimal familiarity with it -- like knowing the sequence [Esc]:q! -- to be sure of being able to edit config files on any random Unix-like system, possibly over ssh.
-A.
vi is the Marmite of the computing world.
I've worked at places where the devs are in vi(m) all day long. It was their editor of choice for C/C++ development and editing scripts...
I never really got on with it, but knowing how to use it is critical, when you have to re-configure some random Linux box that does have your favourite tools installed.
I use vim a lot -- and it is very powerful if you know how to use it.
Years ago I made a deliberate choice to use it as my default text editor.
This was because I knew that when I got a call to fix some security hardened server stuck behind numerous firewalls so the only option was to go to the machine room and access a green screen.
The only editor on the system would be plain old "vi" and the only shell would be "ksh".
"ksh" operates like a one line window into a text editor. You had the choice of "vi" or "emacs" coomands. As no one would ever contemplate allowing "emacs" on a secured machine (its basically a front end for a LISP interpreter and would be like installing a whole dev environment on your production machine).
So learn vi and use it often so you know how to move up and down the command history in "ksh" and edit commands without the aid of the O'Reilly mini manual.
I actually largely agree with this comment.
The primary purpose of an IDE is source-level debugging, ideally with in-place code editing and continuation. Although you *can* work with a seperate debugger and editor pair, it isn't as powerful due to the lack of in-place editing.
You can often correct minor errors in code as you're stepping through the execution, and get a lot further in a given debug cycle than you might otherwise. The more fixes you can get into a build-debug-fix-rebuild cycle, the more productive you are.
A *good* IDE is also a very good editor in its own right, even if there are things ed/ex/vi/vim can do that an IDE editor can't. There are also things IDE editors can do that vim and emacs struggle with, like chasing down references to a method or member every which way in Netbeans.
But *technically* all you need is a good byte-file editor, some graph paper marked off in binary addresses, and a lot of scrap paper for calculating the hex codes of the machine you're "compiling" to (in my case, a TRS-80 Model 1 Level 1 with a Z-80 and a 14 year old's attempt to write a version of 'Space Invaders' at the local Radio Shack. I got an intro screen with spinning saucers done before they told me to buy one or bugger off. :) )
I use VSCode at work a lot, although it is very bloated for what it is, being an Electron application - this is not a criticism of VSCode itself, but the platform on which it was developed. It takes up huge chunks of memory that aren't needed.
I have the same file open in Notepad++ (1.5MB) and VSCode (150MB) - actually a lot slimmer than I remember it from a year ago, but still a huge footprint for what it is.
I use both. I prefer VS Code, so try and use it where possible but there are places where VSCode inexplicably isn't as good as VS (or Jetbrains Rider). For example, attaching to debug running processes (such as Unity) is reliable in VS but not VSCode, even running most up to date versions and supported plugins etc. Particularly galling when working with Unity because Unity is doing the compilation, not the IDE, so you don't need a lot of the clever bulk of VS.
Secondly, I find Jetbrains Resharper tools invaluable and there just isn't viable replacements in VSCode. Finally, if you're hiring .NET devs then (for now) they'll be more familiar with VS and productivity is king, no matter which editor you use. I don't think that's long term as VSCode improves by the day and Rider is getting more popular.
For non-C# stuff, VSCode is king!
I find, after a period of significant improvement, Visual Studio is now becoming rapidly more cumbersome and more unreliable as it integrates ever more stuff into its increasingly cluttered UI. For my taste, it's become an overly-integrated development environment and I would find it less confusing if chunks of functionality were broken out into separate tools. It might also then be easier to maintain.
VS Code currently seems nimbler, but I suspect it will, over time, accrete much of the bloat that plagues its elder sibling.
However, the one big takeaway from all this is that Microsoft still don't have a real solution to the cross-platform UI problem. Having three separate development platforms seems like a huge waste of effort.
It has problems but IS a proper version of VS. It is worlds apart from VSCode, asking the question seems to imply a lack of experience to me.
For .Net 5 C# dev, VS Mac is very solid except for quirks and bugs which make it annoying (docking windows is virtually impossible), and differences to the Windows version. If '22 can bring the two to be consistent I would be a huge fan.
The title seems a bit of a click-bait to me really.
Full VS - Developers with some serious project work that needs to be done, with all the necessary tools.
VSCode - IDE for the rest of we part time coders and scripters, small, versatile enough for the task but can't compete with the features a full dev would need on a serious project.
I do Golang, Rust, C, Python and a lot of automation scripting in various scripted languages, VSCode is good enough for all I need as I'm not a full on developer, I simply need to write basic code in 10-15 different languages at any given time, having one common IDE does the trick for me to get through my day. On the rare occasions I do C# coding I always use full VS, but it's very rare these days.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
