4 ms·
The article starts with a correct problem statement and concludes with a weird claim, because nowadays IDEs like Visual Studio Code do support the best of both
by lifthrasiir 2y ago
The article starts with a correct problem statement and concludes with a weird claim, because nowadays IDEs like Visual Studio Code do support the best of both worlds: inlay hints. I turn them off by default on VSCode (because it messes with columns, unfortunately) but configured them to `offUnlessPressed` so that I can quickly check inlay hints by pressing Ctrl+Alt/Option.
- ReleaseCandidat 2y ago> inlay hints They are a feature of (and configured in) the LSP Server, so every editor that has LSP integration can display them. Still doesn't help when there is no LSP around.
- giomasce 2y agoI wish clangd let me configure the inlay hint elision length...
- lifthrasiir 2y agoYeah, I hope I didn't annoy anyone using editors that have IDE supports via LSP :-p
- ReleaseCandidat 2y agoWell, you never know if vim users are upset because you are calling their editor an IDE or because you are calling it "not an IDE". I'd say "vim user" is already an insult in itself, so that doesn't matter at all ;)
- falcor84 2y ago> I'd say "vim user" is already an insult in itself, so that doesn't matter at all ;) I believe that the proper term is "vim disciple"
- Ferret7446 2y agoWhere do you draw the line between what the IDE is able to show and what is saved in the file? We could remove all indentation and spaces around all operators/symbols and newlines let the IDE inlay that too.
- viraptor 2y agoYes, please? I can't wait until we stop saving code as text. It's silly. Kill the formatting, let everyone see the level they prefer, stop limiting everyone to file-level granularity. Show the types that are relevant in context and allow switching the views.