3 ms·
> Pushing these into an IDE is the Windows way of doing things. I used to think in this idealistic way - if I can't reasonably use the language in VIM (without
by uticus 1y ago
> Pushing these into an IDE is the Windows way of doing things.
I used to think in this idealistic way - if I can't reasonably use the language in VIM (without plugins of course!) the language is flawed, etc.
Lately I've come to embrace the viewpoint that a mixture of language features and great editor support are what enable productivity and creativity.
- fsloth 1y agoGreat tooling is 50% of what makes C# and F# so damn good. For the love of god don’t write C# in a text-editor. The live debugger gives you over 80% of what people gush about in lisp-interactivity - a live program environment you can poke and introspect. Being able to observe a live program in a debugger is so much more powerfull technique. I know there are people out there who can architect anyhting from first principles and deduction - but unless you are really strong it that way live IDE wins.
- lenkite 1y agoYou can do debugging in a console-based text editor nowadays. Neovim has a DAP client for example. https://github.com/mfussenegger/nvim-dap https://github.com/mfussenegger/nvim-dap. Works reasonably well for quick debugging even if you don't get all the bells and whistles of a sophisticated IDE. Though folks have made IDE-like debugging UI's too: https://github.com/rcarriga/nvim-dap-ui https://github.com/rcarriga/nvim-dap-ui