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:
I said continuous vertical lines and literally posted a screenshot of it not being able to do it.
But it’s literally doing that in your image. When a horizontal and vertical line cross the horizontal line breaks.
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.
Oh, did you mean the points that represent actual commits? You’re arguing it’s trash because there’s no line between two adjacent commits? Really?
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’ve brought it up multiple times now so I think it’s time you also source that claim. Cmon, source the claim where the code editor with better visual fidelity increases productivity.
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:
Not only is this a stupid argument but it’s one that I’ve already addressed. Yes, terminal can’t do everything, but I don’t think anyone is using VS code to look at a cube either. Actually, I’m not even sure if there is a VS code extension that draws cubes? So you wouldn’t use VS code for that either. Just like someone using terminal for development would use a different tool to visualize a cube you’d do the same thing if you were using VS code for development. What the fuck are you even arguing here?
But it’s literally doing that in your image. When a horizontal and vertical line cross the horizontal line breaks.
Yes, as an intentional graphical choice to illustrate the crossing of two paths.
In lazyvim a vertical line, with no crossings, is still broken, as it is two pipes separated by the line space height.
Oh, did you mean the points that represent actual commits? You’re arguing it’s trash because there’s no line between two adjacent commits? Really?
No, I’m saying it’s trash because it CANNOT do something basic like drawing a continuous vertical line, because it is hamstrung by using the interface of a typewriter. A git branch is just one readily available example of a situation where something extremely basic like drawing a continuous line would make sense.
You’ve brought it up multiple times now so I think it’s time you also source that claim. Cmon, source the claim where the code editor with better visual fidelity increases productivity.
I can’t cite internal market research that is under NDA. I can point you to basic courses on design and UX, point you to information on concepts like cognitive overload, and point out to you the multiple trillion dollar software companies that got to where they are entirely through paying attention to little UX details that backend nerds previously claimed didn’t matter and were user skill issues.
Yes, terminal can’t do everything, but I don’t think anyone is using VS code to look at a cube either. Actually, I’m not even sure if there is a VS code extension that draws cubes? So you wouldn’t use VS code for that either.
Bruh, why would you even try and talk out of your ass like this? I am literally using jsCad and VsCode to do my personal 3d printing modelling, and I literally got my start programming using first VS, then VSCode, to build 3d modelling software for Autodesk. Not sure if you’re aware of this but modern websites have this little thing called WebGL that lets them display these little things called jraphics.
Again, VsCode can do everything VIM can do, but not vice versa.
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])
But it’s literally doing that in your image. When a horizontal and vertical line cross the horizontal line breaks.
Oh, did you mean the points that represent actual commits? You’re arguing it’s trash because there’s no line between two adjacent commits? Really?
You’ve brought it up multiple times now so I think it’s time you also source that claim. Cmon, source the claim where the code editor with better visual fidelity increases productivity.
Not only is this a stupid argument but it’s one that I’ve already addressed. Yes, terminal can’t do everything, but I don’t think anyone is using VS code to look at a cube either. Actually, I’m not even sure if there is a VS code extension that draws cubes? So you wouldn’t use VS code for that either. Just like someone using terminal for development would use a different tool to visualize a cube you’d do the same thing if you were using VS code for development. What the fuck are you even arguing here?
Yes, as an intentional graphical choice to illustrate the crossing of two paths.
In lazyvim a vertical line, with no crossings, is still broken, as it is two pipes separated by the line space height.
No, I’m saying it’s trash because it CANNOT do something basic like drawing a continuous vertical line, because it is hamstrung by using the interface of a typewriter. A git branch is just one readily available example of a situation where something extremely basic like drawing a continuous line would make sense.
I can’t cite internal market research that is under NDA. I can point you to basic courses on design and UX, point you to information on concepts like cognitive overload, and point out to you the multiple trillion dollar software companies that got to where they are entirely through paying attention to little UX details that backend nerds previously claimed didn’t matter and were user skill issues.
Bruh, why would you even try and talk out of your ass like this? I am literally using jsCad and VsCode to do my personal 3d printing modelling, and I literally got my start programming using first VS, then VSCode, to build 3d modelling software for Autodesk. Not sure if you’re aware of this but modern websites have this little thing called WebGL that lets them display these little things called jraphics.
Again, VsCode can do everything VIM can do, but not vice versa.