4 ms·
Nushell is part of the ongoing Visual Studio-ification of software engineering. TypeScript and Powershell are preferences, not standards. If you want to use th
by fergie 3y ago
Nushell is part of the ongoing Visual Studio-ification of software engineering.
TypeScript and Powershell are preferences, not standards. If you want to use them, great, but its wrong to say that these have evolved into defacto ways of doing things.
Also- that everything is text in Bash is one of its great strengths, just as Powershell's reliance on Objects was generally understood to be a weakness.
Also- I don't get the need for IDE support? Surely the point of a shell language is that it is designed to be used for a terminal?
As others have said here- this feels like a better case for nushell as a scripting language than nushell as a shell.
- pm90 3y agoIDE support is required if you’re building up complex scripts/custom functions.
- pindab0ter 3y agoCould you expand on the "Visual Studio-ification" of software engineering, and why that would be a bad thing?
- fergie 3y ago"Visual Studio-ification": Any technology that requires Visual Studio to be productive. The classic example would be TypeScript, but you can clearly see nushell's overtures to VS in the linked article. A de facto requirement on VS to make a webpage is bad enough, a de facto requirement on VS to write a shell script is even worse.
- fortunateregard 3y agoHover/go-to-definition seems more like a nice-to-have than a requirement. Either way, neovim support can be found here: https://github.com/LhKipp/nvim-nu https://github.com/LhKipp/nvim-nu
- DangitBobby 3y agoIt has nice error messages so you definitely don't need an IDE to edit scripts.
- kzrdude 3y agoDo you mean VS Code or actual Visual Studio? As someone who has unfortunately used both.