Getting an automatic terminal window when you start up vs code is no different having two panes in tmux, one for VIM and once for terminal. You can get a visual project tree representation in VIM by using neotree plugin. Your git doesn’t need to look like that, you can use lazygit. The only things you can’t do within a terminal are reading the pdf or checking assets etc (but I personally wouldn’t look at those things within vs code either), everything else you can do just as easily within the terminal without it looking like the image you gave.
I gave you the benefit of doubt by stating you don’t know how to set up a terminal environment. But if you’re going to be adamant about knowing what you’re talking about then you should also know you’re deliberately misrepresenting the alternative to make your arguments seem more valid.
Getting an automatic terminal window when you start up vs code is no different having two panes in tmux, one for VIM and once for terminal.
Yes it is, and I honestly cannot fathom how you cannot seem to comprehend the difference between text, and an actual pleasant to use and look at graphical interface.
Lazygit looks exactly as trash as the OOTB command line git. How do you not understand that the human brain processes a smooth connected line more easily than a pseudo line broken up by the line space height, made out of pipes and slashes? This is like product design and UX 101.
Again, VSCode does everything VIM does. Not vice versa, one is a superset of the other.
Literally not, since I’m advocating for a superset of what they are.
I use command line tooling perfectly happy within VSCode, they don’t use graphical tooling within VIM.
I’m literally just advocating for a toolset that lets you use graphics or a cli, depending on what makes most sense for the task at hand, they’re advocating to only use the cli.
You’re literally refusing to acknowledge the graphical difference between the standard git tree and Lazygit git tree, and you call it trash because it doesn’t look like you want it to look. It’s dogmatic.
No, I’m not. I’m just pointing out how lazygit is still limited by being a line by line, text based, CLI interface, and thus cannot draw a continuous vertical line, even if drawing a continuous vertical line would make sense in that situation:
I think you meant horizontal line because lazygit is drawing vertical lines. And if we were to get pedantic when to lines cross in vs code then one of them also breaks which means vs code also doesn’t have continuous lines. It’s functionally the same visual representation of data so you’re literally arguing over it not looking like you want it to look.
I said continuous vertical lines and literally posted a screenshot of it not being able to do it.
It’s functionally the same visual representation of data so you’re literally arguing over it not looking like you want it to look.
No, it’s not. The human brain does not process dashed lines as easily as it does continuous lines. A whole bunch of dashed lines are objectively harder to follow than continuous ones.
You can think that’s not important, but the literal decades of UX research and attention to fine grained user interaction, can prove that you’re just flat out wrong.
You look at the above and think they’re the same, but they’re fundamentally not. Literally just go ahead and try and visualize a basuc cube with this base point and dimensions through a CLI and watch that wow, maybe a fucking typewriter interface isn’t the best for absolutely everything:
No, the conclusion I’ve been saying is that CLI developers are smart people who have spent a long time memorizing commands to get fast at things that can be done quickly and intuitively through basic 2d graphical interfaces.
They’re now either in a situation where the gains from learning the new process aren’t going to outweigh the costs (though still doesn’t mean anyone else should follow their path), or they would, but they’re just stuck in their ways because of sunk cost fallacy.
In what way? That you can have multiple terminal panes open to accomplish a small portion of the above?
Getting an automatic terminal window when you start up vs code is no different having two panes in tmux, one for VIM and once for terminal. You can get a visual project tree representation in VIM by using neotree plugin. Your git doesn’t need to look like that, you can use lazygit. The only things you can’t do within a terminal are reading the pdf or checking assets etc (but I personally wouldn’t look at those things within vs code either), everything else you can do just as easily within the terminal without it looking like the image you gave.
I gave you the benefit of doubt by stating you don’t know how to set up a terminal environment. But if you’re going to be adamant about knowing what you’re talking about then you should also know you’re deliberately misrepresenting the alternative to make your arguments seem more valid.
Yes it is, and I honestly cannot fathom how you cannot seem to comprehend the difference between text, and an actual pleasant to use and look at graphical interface.
Lazygit looks exactly as trash as the OOTB command line git. How do you not understand that the human brain processes a smooth connected line more easily than a pseudo line broken up by the line space height, made out of pipes and slashes? This is like product design and UX 101.
Again, VSCode does everything VIM does. Not vice versa, one is a superset of the other.
Just as dogmatic as the people you complain about.
Literally not, since I’m advocating for a superset of what they are.
I use command line tooling perfectly happy within VSCode, they don’t use graphical tooling within VIM.
I’m literally just advocating for a toolset that lets you use graphics or a cli, depending on what makes most sense for the task at hand, they’re advocating to only use the cli.
You’re literally refusing to acknowledge the graphical difference between the standard git tree and Lazygit git tree, and you call it trash because it doesn’t look like you want it to look. It’s dogmatic.
No, I’m not. I’m just pointing out how lazygit is still limited by being a line by line, text based, CLI interface, and thus cannot draw a continuous vertical line, even if drawing a continuous vertical line would make sense in that situation:
I think you meant horizontal line because lazygit is drawing vertical lines. And if we were to get pedantic when to lines cross in vs code then one of them also breaks which means vs code also doesn’t have continuous lines. It’s functionally the same visual representation of data so you’re literally arguing over it not looking like you want it to look.
I said continuous vertical lines and literally posted a screenshot of it not being able to do it.
No, it’s not. The human brain does not process dashed lines as easily as it does continuous lines. A whole bunch of dashed lines are objectively harder to follow than continuous ones.
You can think that’s not important, but the literal decades of UX research and attention to fine grained user interaction, can prove that you’re just flat out wrong.
You look at the above and think they’re the same, but they’re fundamentally not. Literally just go ahead and try and visualize a basuc cube with this base point and dimensions through a CLI and watch that wow, maybe a fucking typewriter interface isn’t the best for absolutely everything:
Cube([0.37, -300, 45], [37,-98,-100])
Yes. Obviously. Two conclusions available to you are, either CLI developers are idiots, or they have tools you are unaware of.
The answer to “how can anyone work this way?” is out there, if you’re really interested.
No, the conclusion I’ve been saying is that CLI developers are smart people who have spent a long time memorizing commands to get fast at things that can be done quickly and intuitively through basic 2d graphical interfaces.
They’re now either in a situation where the gains from learning the new process aren’t going to outweigh the costs (though still doesn’t mean anyone else should follow their path), or they would, but they’re just stuck in their ways because of sunk cost fallacy.