91–100 of 132 posts
Was using vim for quick edits on files instead of vscode a significant pain point?
Reading the page and encountering "web standards" got me thinking (red flag #1), why would I care for web standards in a terminal ? Another red flag is bashing vim. Final - looking at the code and seeing "electron".
But like…why? At the risk of being “HN talks about rsync on the Dropbox thread” what’s this offering that can’t already do, for free, without a EULA, and inevitable VC-enshittification risk? > ditch vim for quick updates Bruh, have you seen the average vim user? They’re about the fastest people on a computer I’ve seen in my life. This is not exactly a convincing argument. > Render code, images, markdown, and CSV file…
Something about this design make it seem more like a chat interface to the terminal, and after using ChatGPT the idea of chatting to a raw computer terminal instead of one way commands seems so obvious... the future interface for everything looks more and more like it's just going to be chat based, or like a Jupyter notebook, and that seems amazing to me... because it's getting us ready for voice-based computing like…
Reading the page and encountering "web standards" got me thinking (red flag #1), why would I care for web standards in a terminal ? Another red flag is bashing vim. Final - looking at the code and seeing "electron".
"Another red flag is bashing vim." The website in context of discussing their inline editor says, "Ditch vim for quick updates.". You seem to have a very low threshold for what is considered bashing.
Earlier quoted context omitted.
"Another red flag is bashing vim." The website in context of discussing their inline editor says, "Ditch vim for quick updates.". You seem to have a very low threshold for what is considered bashing.
Agree, but I think the usage of “ditch” is a bit snarky.
Reading the page and encountering "web standards" got me thinking (red flag #1), why would I care for web standards in a terminal ? Another red flag is bashing vim. Final - looking at the code and seeing "electron".
"Another red flag is bashing vim." The website in context of discussing their inline editor says, "Ditch vim for quick updates.". You seem to have a very low threshold for what is considered bashing.
Earlier quoted context omitted.
Actually - VSCode comes with a built-in Terminal that's also built using Electron and TS. Never had any issues with it while using it as built-in Terminal from time to time.
The VSCode terminal is the first time I've felt input lag in a terminal emulator before. When a program shits out thousands of lines of text (like catting a long log file), it takes forever to catch up compared to any other terminal (except the JetBrains builtin terminal, which is almost as slow but still noticeably faster).
Earlier quoted context omitted.
Two main reasons: 1. It has a ridiculous learning curve to get to the same editing proficiency as just having multiple cursors. All Vim users imagine themselves to be editing text at the speed of light while users of "lesser" editors struggle with scalar editing. I have seen zero evidence of that. Anyone of my colleagues that use Vim struggle to do basic tasks because remembering the gazillions of mnemonics is too on…
Vim isn’t for you, and that’s fine. Statements like “all Vim users…” aren’t really a great contribution to the discussion. I’ve used Vim for 20+ years. I like it, you don’t have to. I don’t try to shove it down anyone’s throat - nor do I try to tell you why your favorite tool sucks. Because it probably doesn’t suck - for you. Tell me what you like or what doesn’t work for you and leave the middle school attitude wher…
See point 2. Vim isn't for 99% of people but it's somehow the default editor? Most people do not like Vim. That's why this project advertises not having to use Vim, because to 99% of people Vim is something that they don't want or like and can't even quit.