251–260 of 680 posts
With this much revenue... can they eventually divert some to providing a 'live share' service like vscode offers? I would think it would be a service they could possibly even uncharge for - I would pay a few $ more for a 'plus' version which offers 'share my project with other jetbrains users for pairing'.
Earlier quoted context omitted.
The vim emulation for the IntelliJ tools worked very well for me. Used to use only vim with a complex setup. Have been using Goland, and IntelliJ for about a year now.
I actually haven't tried it (just started using PyCharm again very recently). But I gave it a go right after posting my comment. And like almost every other emulation I've ever tried, within 1 minute, I found 5 things that didn't work correctly. And I'm not exaggerating here - I literally spent 1, maybe 2 minutes and found 5 things. I'll have to use it for a while to find out whether it's just a few minor annoyances,…
Earlier quoted context omitted.
I mainly use vim and occasionally use Jetbrains. My setup in vim is super complex. I can tell you exactly how I feel about it: Vim is a better text editor than anything else. By far. Unfortunately, vim is terrible at basically everything else. The problem is, once you learn to use vim's text editing capabilities, then editing code using anything else feels like a pain. I'm not talking about variable lookups / etc. I'…
> "move the cursor to a certain place and enter some text" In vscode, I'm usually already looking at the call site of a function I want to edit. So I move the cursor into the function call and hit F12 which takes me to the function definition to edit it. Once I'm done, I hit Alt+LEFT to navigate back to where I was to continue on... If I didn't start from a call site but I know the file I want to edit - I hit Ctrl+P,…
The part about moving the cursor. Vim users typically don't move the cursor with the mouse but rather with the keyboard. Having to move your hands off the keyboard to reach for the mouse then back is the part that starts to feel sluggish if you get used to not doing it.
No apologies, no compensation for building a commercial product on something I had spent a decent amount of time on. Very disappointing of them.
Earlier quoted context omitted.
The vim emulation for the IntelliJ tools worked very well for me. Used to use only vim with a complex setup. Have been using Goland, and IntelliJ for about a year now.
I actually haven't tried it (just started using PyCharm again very recently). But I gave it a go right after posting my comment. And like almost every other emulation I've ever tried, within 1 minute, I found 5 things that didn't work correctly. And I'm not exaggerating here - I literally spent 1, maybe 2 minutes and found 5 things. I'll have to use it for a while to find out whether it's just a few minor annoyances,…
It would be useful to say what these 5 things are.
Earlier quoted context omitted.
I mainly use vim and occasionally use Jetbrains. My setup in vim is super complex. I can tell you exactly how I feel about it: Vim is a better text editor than anything else. By far. Unfortunately, vim is terrible at basically everything else. The problem is, once you learn to use vim's text editing capabilities, then editing code using anything else feels like a pain. I'm not talking about variable lookups / etc. I'…
> "move the cursor to a certain place and enter some text" In vscode, I'm usually already looking at the call site of a function I want to edit. So I move the cursor into the function call and hit F12 which takes me to the function definition to edit it. Once I'm done, I hit Alt+LEFT to navigate back to where I was to continue on... If I didn't start from a call site but I know the file I want to edit - I hit Ctrl+P,…
E.g., say you somehow got to a file, and it now has a bunch of functions in it, and you're literally looking at the line you want to edit. To get to that line, there's a bunch of different ways, but you can do this in like 3 key presses. Then, within the line, you can change anything in it really easily.
This sounds weird, so I'll try to give an example. Let's assume you have something like:
Func(self._something, self.something_else).validate, 'Validate exam foundation table')
And let's say you want to change the string that says 'Validate [...]' to say 'Change is good!!'.
To do that, once you've gotten to the line, I'd probably hit two key presses that mean "go to the first open quote in the line", then I'd hit the keys that mean "delete everything inside of the quote character", then I'd type what I want. All in all, I'd be typing these characters before actually writing what I want to write: f'ci' (so, 5 characters).
That probably looks either idiotic or daunting - but the idea of vim is that it's a language - you are literally thinking in your head "go to that quotation mark", then tell vim to do that and it does. Then you're thinking "delete everything inside of these quotations", and it does it. The distance between thinking what you want to do and doing it is almost zero - it's as close as you can get to literally telling someone exactly what to do.
If you're using a non-vim editor, you'd probably have your cursos in the begining of the line, and have to do "cmd+right" several times to skip over words in order to get to the first word of the string, then have to "shift+cmd+right" to get to the end of the string, then write what you want.
There might also be some small annoyances - the last shift+cmd+right might take you over the last quotation mark, and you'd end up selecting the closing paren as well. In vim - that doesn't happen, you're saying exactly what you want to have happen.
Or you might want to undo this change - in vim, it's always hitting "u" once, because in vim, changing the string to something else is an atomic motion. In another editor, you might have to undo a few words at a time, or maybe not - it's not always predictable. And since it's atomic in vim, it's also easy to re-apply the same action to another string - so changing another string to the same thing is a simple matter of hitting "." on it.
And of course, this is just a tiny example. It's easy to dismiss as trivial or unimportant - these are tiny savings of time, after all, and even if you add it up, I doubt the "time saved" in doing things more efficiently is worth much.
But once you know this language for telling an editor exactly what to do, then using an editor that doesn't speak that language just feels super slow - it feels like you are not able to communicate properly, and suddenly, what used to be zero gap between thinking and doing, takes a long time.
Earlier quoted context omitted.
I mainly use vim and occasionally use Jetbrains. My setup in vim is super complex. I can tell you exactly how I feel about it: Vim is a better text editor than anything else. By far. Unfortunately, vim is terrible at basically everything else. The problem is, once you learn to use vim's text editing capabilities, then editing code using anything else feels like a pain. I'm not talking about variable lookups / etc. I'…
> "move the cursor to a certain place and enter some text" In vscode, I'm usually already looking at the call site of a function I want to edit. So I move the cursor into the function call and hit F12 which takes me to the function definition to edit it. Once I'm done, I hit Alt+LEFT to navigate back to where I was to continue on... If I didn't start from a call site but I know the file I want to edit - I hit Ctrl+P,…
For example: say I jump to this function and want to fix a bug (the `search` should strip off the first two characters here, not just one). So I need to change `regex.search(s[1:], ...)` to `regex.search(s[2:], ...)`:
def compile_hg_glob(line):
pat = glob_to_re(line)
# Mercurial ignore globs are quasi-rooted at directory boundaries or the
# beginning of the pattern.
pat = '(^|/)' + pat
# Mercurial globs also have to match to the end of the pattern.
pat = pat + '$'
try:
regex = re.compile(pat)
return lambda s: regex.search(s[1:] if s.startswith('./') else s)
except:
warn("could not parse hgignore pattern '%s'" % line)
return lambda s: True
Or suppose I'm looking at this and want to add a `,` character to the end of each of the type entries, because I forgot Python likes its commas:
result = result | {
'a': TYPES_ALL
'e': TYPES_FILE_REAL
'x': TYPES_FILE_SYMLINK
'c': TYPES_DIR_REAL
'y': TYPES_DIR_SYMLINK
'f': TYPES_FILE
'd': TYPES_DIR
'r': TYPES_REAL
's': TYPES_SYMLINK
}[c.lower()]
These kinds of things happen constantly, and when you've got Vim burned into your fingers trying to edit text without it (actually edit text, not just jumping to something) feels like typing with oven mitts on.
Earlier quoted context omitted.
OP is litereally ranting about people using text editors for tasks that IDEs excell at, and you are suggesting another text editor.
VSCode is way closer to IDE than text editor on that spectrum
Earlier quoted context omitted.
I'd been a Visual Studio user for I think over a decade, and was really, really sick of listening to my laptop fans whining the whole time, and frequent freeze-ups. Every new version promised better performance, and never delivered - VS's poor (and unreliable) performance is the main thing that made me try Rider, and what performance revelation it was!
> VS's poor (and unreliable) performance is the main thing that made me try Rider, and what performance revelation it was! VS 2019 is actually as fast or faster than Rider for me. But that is without Resharper, and without it, I miss way too much functionality.
That said, before I pulled the trigger and purchased a Rider license, I tried running VS without ReSharper. While it certainly was definitely faster, more responsive and used less memory, I still didn't find it as snappy as Rider. It also still had my laptop fans whining, and occasionaly became completely unresponsive.
It's a real shame - Visual Studio is without doubt an excellent IDE, but performance and reliability issues have plagued it since forever. I really wish a serious effort would be made to address these.
Earlier quoted context omitted.
True; that's the only subscription model I find acceptable for software that hardly changes in meaningful ways. For example, I refuse to upgrade Git Tower to version 3 as a protest against fournova's new licensing. Up to that point, I was a loyal customer and product advocate, basically buying every upgrade anyway, but by my own choice. Instead, I'll be on version 2 "forever", despite all its flaws. It was even worse…
Same here for Adobe Creative Suite; still on version 6 (perpetual license), which I run in a Virtual Machine due to support end-of-life.
(obdisclaimer: I worked for Adobe several years ago, but have no current stake other than being on the CC photography plan)