▲ 342 ▼ What are your programming hot takes? (lemmy.ml) submitted 2 years ago by 257m@lemmy.ml to c/programming@programming.dev 886 comments fedilink hide all child comments
[–] tatterdemalion@programming.dev 15 points 2 years ago (2 children) The only thing a GUI text editor can be better at than a terminal editor is making it easier to use the mouse. permalink fedilink source hideshow 4 child comments replies: [–] exi@feddit.de 7 points 2 years ago* (last edited 2 years ago) (2 children) That really is one hell of a hot take 😀 I for one really love the zoomed out preview on the right that has become popular in recent years. https://jason-williams.co.uk/assets/img/2020/debugging_screenshot.png Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is. Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates. Another example: inline preview of latex or Template fragments. permalink fedilink source parent hideshow 4 child comments replies: [–] tatterdemalion@programming.dev 3 points 2 years ago* (last edited 2 years ago) (1 child) That really is one hell of a hot take Yea well most of the comments in here are lukewarm takes so... there you go. I for one really love the zoomed out preview on the right that has become popular in recent years. I almost never navigate code based on its order or "shape" in the file. LSP-based symbol tagging or searching is way faster than scrolling. I guess you can click the spot on the preview that you need, but I refuse to reach for my mouse while editing text. Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is. I use LSP integration to see a complete list of errors/warnings and jump to them. Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates. That's for design, not text editing ;) inline preview of latex or Template fragments. I will use a latex or markdown language server that renders to a browser tab. To be fair, I don't do HTML/JS/CSS, so I bet VSCode or other GUI editors are great for that. But that's specifically because you want to see something rendered. Most of the time you can just see it in an actual browser next to your text editor though. permalink fedilink source parent hideshow 2 child comments replies: [–] stinodes@lemmy.world 3 points 2 years ago I almost exclusively do front end, in exclusively nvim. Exactly like you say, just have a browser window (or 2) permanently open. permalink fedilink source parent [–] xigoi@lemmy.sdf.org 1 point 2 years ago* (last edited 2 years ago) the zoomed out preview on the right https://github.com/gorbit99/codewindow.nvim GUI color picker directly in my editor https://github.com/uga-rosa/ccc.nvim inline preview of latex https://github.com/jbyuki/nabla.nvim permalink fedilink source parent [–] morrowind@lemmy.ml 1 point 2 years ago (1 child) Conversly, I see nothing a TUI editor can do better than a GUI, including use of the keyboard permalink fedilink source parent hideshow 2 child comments replies: [–] tatterdemalion@programming.dev 1 point 2 years ago* Yea I think I agree with you there, at least theoretically. In practice I've found that it's easier to use a TUI editor over SSH, and they require less resources, but that usually isn't noticeable on my PC. TUI editors can also run inside tmux, which is very nice if you are a tmux user. permalink fedilink source parent
[–] exi@feddit.de 7 points 2 years ago* (last edited 2 years ago) (2 children) That really is one hell of a hot take 😀 I for one really love the zoomed out preview on the right that has become popular in recent years. https://jason-williams.co.uk/assets/img/2020/debugging_screenshot.png Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is. Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates. Another example: inline preview of latex or Template fragments. permalink fedilink source parent hideshow 4 child comments replies: [–] tatterdemalion@programming.dev 3 points 2 years ago* (last edited 2 years ago) (1 child) That really is one hell of a hot take Yea well most of the comments in here are lukewarm takes so... there you go. I for one really love the zoomed out preview on the right that has become popular in recent years. I almost never navigate code based on its order or "shape" in the file. LSP-based symbol tagging or searching is way faster than scrolling. I guess you can click the spot on the preview that you need, but I refuse to reach for my mouse while editing text. Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is. I use LSP integration to see a complete list of errors/warnings and jump to them. Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates. That's for design, not text editing ;) inline preview of latex or Template fragments. I will use a latex or markdown language server that renders to a browser tab. To be fair, I don't do HTML/JS/CSS, so I bet VSCode or other GUI editors are great for that. But that's specifically because you want to see something rendered. Most of the time you can just see it in an actual browser next to your text editor though. permalink fedilink source parent hideshow 2 child comments replies: [–] stinodes@lemmy.world 3 points 2 years ago I almost exclusively do front end, in exclusively nvim. Exactly like you say, just have a browser window (or 2) permanently open. permalink fedilink source parent [–] xigoi@lemmy.sdf.org 1 point 2 years ago* (last edited 2 years ago) the zoomed out preview on the right https://github.com/gorbit99/codewindow.nvim GUI color picker directly in my editor https://github.com/uga-rosa/ccc.nvim inline preview of latex https://github.com/jbyuki/nabla.nvim permalink fedilink source parent
[–] tatterdemalion@programming.dev 3 points 2 years ago* (last edited 2 years ago) (1 child) That really is one hell of a hot take Yea well most of the comments in here are lukewarm takes so... there you go. I for one really love the zoomed out preview on the right that has become popular in recent years. I almost never navigate code based on its order or "shape" in the file. LSP-based symbol tagging or searching is way faster than scrolling. I guess you can click the spot on the preview that you need, but I refuse to reach for my mouse while editing text. Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is. I use LSP integration to see a complete list of errors/warnings and jump to them. Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates. That's for design, not text editing ;) inline preview of latex or Template fragments. I will use a latex or markdown language server that renders to a browser tab. To be fair, I don't do HTML/JS/CSS, so I bet VSCode or other GUI editors are great for that. But that's specifically because you want to see something rendered. Most of the time you can just see it in an actual browser next to your text editor though. permalink fedilink source parent hideshow 2 child comments replies: [–] stinodes@lemmy.world 3 points 2 years ago I almost exclusively do front end, in exclusively nvim. Exactly like you say, just have a browser window (or 2) permanently open. permalink fedilink source parent
[–] stinodes@lemmy.world 3 points 2 years ago I almost exclusively do front end, in exclusively nvim. Exactly like you say, just have a browser window (or 2) permanently open. permalink fedilink source parent
[–] xigoi@lemmy.sdf.org 1 point 2 years ago* (last edited 2 years ago) the zoomed out preview on the right https://github.com/gorbit99/codewindow.nvim GUI color picker directly in my editor https://github.com/uga-rosa/ccc.nvim inline preview of latex https://github.com/jbyuki/nabla.nvim permalink fedilink source parent
[–] morrowind@lemmy.ml 1 point 2 years ago (1 child) Conversly, I see nothing a TUI editor can do better than a GUI, including use of the keyboard permalink fedilink source parent hideshow 2 child comments replies: [–] tatterdemalion@programming.dev 1 point 2 years ago* Yea I think I agree with you there, at least theoretically. In practice I've found that it's easier to use a TUI editor over SSH, and they require less resources, but that usually isn't noticeable on my PC. TUI editors can also run inside tmux, which is very nice if you are a tmux user. permalink fedilink source parent
[–] tatterdemalion@programming.dev 1 point 2 years ago* Yea I think I agree with you there, at least theoretically. In practice I've found that it's easier to use a TUI editor over SSH, and they require less resources, but that usually isn't noticeable on my PC. TUI editors can also run inside tmux, which is very nice if you are a tmux user. permalink fedilink source parent