Amongst the many traditional features of an IDE, Visual Studio also offers a bevy of options specific to the Microsoft ecosystem by its selection of Azure specific plugins. Although other stacks can make use of the IDE, the proprietary stack options of Microsoft are more heavily concentrated on this platform. NET developers, and for years now it has served that user base well. Microsoft’s IDE, Visual Studio, is produced for the community of C# and. While Visual Studio, the IDE, offers many of the robust features we know and love, Visual Studio Code is not a platform to discount without trial.
Beloved by many, the two offer different texture and features by which a developer writes code. This is why I support this feature request.Īs an industry could stand to move away from having opinions about how other developers format their source code, in favor of expressiveness, ease and inclusiveness.Microsoft offers the Visual Studio platform to developers in the form of a full-bodied integrated development environment (IDE), along with its text editor counterpart. Each developer can then individually format code according to how each thinks best. Do not impose whitespace and indentation formatting constraints for source code if the language itself does not.
Opinionated formatters impose a cognitive load on everyone, making individual coders work harder to read their own code Expressiveness and facility is important when coding and reading code, and I would argue this is top priority.This reduces errors and cognitive load when reviewing code and when troubleshooting. The problem that formatters solve: whitespace and indentation is consistent across developers and time, so that changes between commits are obvious. I suspect that opinionated formatters such as Prettier solve one problem but at high cost. As with everything, I have Thoughts On This.
0 kommentar(er)
