You can write a regex to replace a string in a matter of seconds. And so can I. What neither of us can do is write it such that the replacement is limited to the identifier we want to rename (because pumping lemma), that needs syntax if not semantics-aware editing and that's exactly what LSP is for.

You're using a screwdriver as a hammer. Does it work, sure, is it advisable? Even if you don't have a hammer it might be easier and quicker to drive to the hardware store and buy one, depending on the particular nail you're dealing with.

Meanwhile in IntelliJ or VSCode I just find the menu and if I want to be super quick, next to the menu item is the keyboard shortcut

Helix: ? opens function search, enter "rename", "rename symbol" will be the first hit and it'll also tell you that it's bound to r.

Blender: F3 instead of r. Get out of here with clicking through menus. I have no idea where to find recalculate normals in the menus and I don't care. "face" in edit mode, probably. Nope, just checked: Edit mode, mesh->normals->recalculate [inside, outside]. Kinda makes sense while normals are a property of faces you can't calculate them without reference to a mesh as you wouldn't be able to tell outside from inside, only stuff like "face camera".

This isn't so much about gui or not gui thing, both IntelliJ and VSCode come from the windows school of GUI design which says "discoverable without a manual, hotkeys are available for power users". Blender, OTOH, follows the UNIX philosophy of "RTFM, start working like a pro from the beginning it's worth it, the interface is just a suggestion, adjust it to your workflow".

Maybe I could eventually even get faster, but could I ever recoup that time investment?

How would you know without giving them an honest spin? Personally I wouldn't recommend vim, btw, lots of hysterical raisins and inconsistencies to be found there and configuration is a PITA which wouldn't even be that bad if the out of the box experience was good. Helix cleans up both the command language and the whole configuration shebang (just make sure that LSP servers are installed and you're good to go) while definitely sticking to the vi/blender style of interface design.

[–] MagicShel 2 points 7 months ago* (last edited 7 months ago) (1 children)

First I want to say this is a great comment overall. I appreciate it. But a couple notes:

What neither of us can do is write it such that the replacement is limited to the identifier we want to rename

\Widentifier\W - harder to navigate markdown than write the pattern. This would also catch references to the identifier in comments as well, though if the identifier isn't a unique word it might take a little repair, but that's rarely the case in Java where the convention is expressive identifiers.

UNIX philosophy of "RTFM, start working like a pro from the beginning [...]

That only works for small manuals. Take Git for example, because that's something I often use the CLI for. There are a huge number of things to learn out of the gate and you can't just RTFM and you're good to go. And it's really not particularly big or complex. Something as simple as cherrypicking - well first I need to log to see the commit ids. Oh not just log but --pretty-something so I can just see the commit ids. Off to Google shit to remind me how to do another thing I only do every few weeks. Compare that to a GUI where I can just right-click cherry-pick. This absolutely kills my productivity because I do so much different shit, I can't possibly remember everything that I barely use.

How would you know without giving them an honest spin?

I only have so many hours in the day to experiment. And I do, but the "cost" here is pretty high and the opportunity for return is low. We're talking about things I might do a couple of times a month.

Now it's possible I'm an idiot and I'm just slower or dumber than folks who like vim. It's also possible my roles have been really fucked up and I don't get to focus enough to get good at stuff that ought to be its own niche. All I can say is I've stuck my toe into the water and it's fucking cold. Currently I'm probably 85% GUI and 15% CLI and other keyboard-centric tools. I just use whichever is the most expedient.

I wrote a one line bash script to start my vpn because I couldn't remember each little keystroke but I can remember start-vpn.

Once again, I appreciate your comment. Upvoted. I don't know what helix is. Blender I know but isn't really a business software writing tool so I have maybe 20 hours playing around with it total. I'll look into LSP on my PC, but I might just forget I have it by the time I try to figure out what to do with it.

[–] [email protected] 2 points 7 months ago (1 children)

Take Git for example,

Git is simple in its operations, but utterly complex in the stuff you might need to do because the operations aren't mathematically clean. Things like git rerere should plainly not exist because states which require using it should be impossible to reach. And the likes of vim, or pre-2.8 blender, kinda ended up there as they grew organically, the more you tack on the more likely it is that different things don't work well with each other. Which is why I recommended helix: It's a clean-slate redesign. E.g. helix' command language is consistently while vim is all over the place, you end up learning things by rote instead of really exploiting the combinatorics. On the VCS side darcs is sane in principle but it's patch theory didn't really have efficiency in mind and there's a very nasty complexity explosion you can run into, pijul fixes all that: It has both a vastly superior interface without surprises (such as patches not being associative) and it's fast.

We’re talking about things I might do a couple of times a month.

The most striking difference between the likes of VSCode and Helix are not things that you do once a month, but stuff that you do all the times: Navigating and basic editing. Within the first couple of pages of going through the tutorial you'll know if navigating with hjklwWbB etc. is a thing that would save you time, whether it's worth making the interface modal, having to type i (or various other options) before actually writing text. I certainly still haven't really gotten my head around Helix' multiple cursors because I don't need it that often but VSCode wouldn't be any faster at those kind of things, either.

I’ll look into LSP on my PC, but I might just forget I have it by the time I try to figure out what to do with it.

Language Server Protocol. Actually started out on VSCode, it's how language integration works: The compiler writers (or whoever) provide functionality such as "give me docs for a certain identifier", "rename this identifier" etc. and the editor/IDE simply offers those options, display the docs in-line, etc. It quickly caught on everywhere, 20 years ago you certainly wouldn't have seen me advocate writing Java in vim because the likes of Eclipse were just way better at wrangling the language, but the times of those language-specific functions not being available in good ole code editors are over.

[–] MagicShel 3 points 7 months ago (1 children)

Tell you what. As I've just ended a contract and have some time to work on my side project while I job hunt, I'll give it a shot for the rest of this month and report back.

[–] [email protected] 2 points 7 months ago (1 children)

Blog post! Blog post!

[–] MagicShel 1 points 7 months ago* (last edited 7 months ago) (1 children)

Probably no one but you will find this there. Which is good because this is just an extremely raw first draft. I'm not asking for answers from you here. If part of my experience is "go find random people on Lemmy to help" that doesn't seem useful. But I want to share this experience which was about 90 minutes of my day, and also see how compatible the markdown here is with Joplin, which is my note-taking tool of choice. I don't know if I can stick with this man. I haven't even opened Vim yet.

I took on a challenge in a Lemmy comment to use Vim for a month. To give some context for this experience, let's start off with the relevant details of who I am.

I'm a Java developer with 25 years of experience
I use Ubuntu as my daily driver. I no longer have a windows computer (except as an old SSD I could swap to in an emergency), not even as a VM.
While this might make me sound like a seasoned Linux pro, it's more the case that everything I need to do on a computer is now performed in a browser or a handful of applications. Maven, Tomcat, and Git are probably the only CLI applications I use, and Tomcat only rarely because I don't often do that kind of development for my side projects.
I know basic linux navigation. Most everything else requires a little googling.
I know how to exit Vim, go into insert mode, and I know how to delete 1 (dd) line or mulitple lines (dn). I know nothing else. Not even how to copy/paste.
I like learning new things, but self-directed learning is frequently aggravating. Fortunately I also enjoy ranting about frustrations and bizarre rituals that must be performed without understanding.

So one of the first things it was suggested I would need is LSP. I don't recall what it stands for (I mean I could google it, but I might as well be honest about my ignorance, right?), but anyway I searched for "ubuntu install LSP". As one does. The top result is a thread on Reddit in r/neovim. The fuck is Neovim?

So more googling tells me Neovim is a fork of Vim 7 that some folks like and other folks aren't bothered about. There are plugins for both (why the fuck do you need a plugin for a text editor?) and some plugins work with both while others work on one or the other. Just like everything else in the Linux world, there are no fucking answers, just opinions and most of them are totally irrelvant to your environment or use case. I just want to edit some fucking code. So I'm sticking with Vim - that's the point, right?

So back to the original question, how do I install LSP and whatever plugin is needed? For anyone keeping score, I started with one question and now I have three with one... well less answered than just decided. I think I'll google "getting started with Vim and LSP"

Top result is very promising. "End goal: get working LSP in Vim for Python. Constraints: please no neovim suggestions." Other than Python instead of Java, this is perfect! This is my thread!

Check out the LSP clients heading in https://langserver.org/ There are a number of vim plugins that provide LSP integrations:

https://github.com/natebosch/vim-lsc
https://github.com/prabirshrestha/vim-lsp
https://github.com/autozimu/LanguageClient-neovim (supports vim & neovim)
https://github.com/w0rp/ale (what I currently use b/c it integrates linters as well as Language Servers & it is the best zero-config LSP plugin for vim)
https://github.com/neoclide/coc.nvim

Most plugins will require you to do add some configuration to wire up the Language Server client (i.e. the plugin) with the language server (e.g. pyright, pylsp, ...etc). Other than that, I recommend reading plugin docs to learn how to use/configure the plugin with the language server and ask for help on the github repo if you have specific questions or run into issues/errors.

First, fuck me. It's just a bunch of random fucking repos. Who the fuck are these people? I guess this guy is endorsing ALE. Is w0rp a person? Organization? Grad student? Seasoned professional? A guy one hamburger away from a heart attack?

So anyway it looks like I also need a language server (that's the LS in LSP, 'twould seem - nice when questions answer themselves). Wait a second... That was my original question! They didn't answer how to do the thing I wanted to do, they answered how to do the other thing I didn't know I wanted to know how to do. I'm going to file this bookmark away because it's not relevant to me just now, but it looks like this will be my next question.

For now, back to google: "ubuntu install lsp java"

Okay a bunch of shit about emacs and people having or overcoming difficulties in installing it. That's not promising - seems just installing fucking LSP is about to be an ordeal. Oh! Here's a github by George W Fraser. I don't know who that is, but he uses his middle initial, so clearly someone of import and sophistication. Important side note: If he went by his full middle name, that would be a serial killer. A subtle but critical distinction.

Actually that may not be entirely true. I feel like I've seen his name before. Let's see what he has to say.

Fuck me again! He says to use vim-lsc. Wait a god damn minute... This is the same fucking question I just had non-answered by some random redditor! How do I install the god damned language server, motherfucker!?

To be continued...

[–] [email protected] 1 points 7 months ago* (last edited 7 months ago) (1 children)

Remember what I said about the vim out of the box experience and configuration nightmare? Yep that's why.

If you want to stick with (n)vim over helix head over here, which is going to take away like 90% of the pain. You'll still need to go "yep I want this and this and this" but it's much more like browsing through the VSCode store and hitting "install". Quick start guide, general IDE, Java IDE should do it. There's actually more end-user type documentation for spacevim as compared to vim (which is a giant heap of hysterical raisins noone writes beginner intros for) or helix (which is too young to have actually good docs). Both are more opinionated than plain vim+whatever plugins but at least as far as I'm concerned I don't care which of the fifty available fuzzy file finder plugins I'm using: I just want one that works. Spacevim makes a default choice for you, helix has one built-in. Same goes for LSP integration.

Also you don't necessarily need to dive in at the deep end. As said most of the difference vs. your usual IDE isn't in feature set but how you interact with the thing, editing markdown should suffice to get a good idea, with or without LSP support in the case of markdown it's really optional, I think it's mostly about helping you to not have broken links.

[–] MagicShel 1 points 7 months ago

I have no problem with opinionated software. I need a starting point from which to disagree. Thanks for the links. I'll read up this afternoon or tomorrow.