No problem. I deleted it because I realized that I did in fact misread things. :) You’re doing good here.
For me it’s less effort because everything that I want just works out of the box. The totally of my configuration is under 10 lines. I don’t want to have to mess with nested config files each dozens to hundred of lines long most of which I will not understand just to code.
Also helix is different in that it uses the selection then action workflow. Vim is action then selection which is less nice for me.
In helix if I want to delete a function I would do: ESC -> space -> f -> d
Which means: Normal mode then lsp menu then next function then delete.
In vim I would have to delete then select what to delete which I don’t like.
To get to the point where I could feel like not an idiot maybe 3 hours of actual programming time.
To get to the point where I was a slow yet productive programmer it took maybe 12 hours of actual programming time.
To get faster than I was at Jetbrains IDEs that took like maybe ~24 hours of actual programming time.
I strongly recommend:
- remapping caps lock to escape.
- disabling the arrow keys in all modes.
After I did these two things, I got better faster. It’s frustrating but totally worth it. Now when I’m on my laptop I just use helix and qutebrowser under the sway desktop environment. It’s a 100% mouse free experience and it’s just faster and better in every way.
I know exactly how you feel. I did eventually end up finding an open source solution that worked for me though. After trying a few things I ended up on the helix text editor + the Rust LSP.
It took me a while to get to the point where I could code as fast as I could in Jetbrains IDEs but I got there and am now even faster than I used to be.
It was hard but very worth it.
Ahh. Bone Apple Tea moment.
This reaks of chatgpt. All the way down to the milktoast ending.
You’re not wrong. NIV is very generic. Lol.
The thing that stands out to me in the translation you have is making idles to yourself. Instead of for yourself. That and using the term Jehovah. Those to me are major pointers to using the NWT, which among the Christian diaspora is seen as less reputable.
I’m a secular person now but as a formally very religious person I know a bad Bible translation when I see it.
Assuming you a referring to Leviticus 26:1 a better translation from the NIV is:
Do not make idols or set up an image or a sacred stone for yourselves, and do not place a carved stone in your land to bow down before it. I am the LORD your God.
Given this I can see how Catholics can justify having statues and art and the like.
In case you don’t like the NIV here is a meta comparison.
I’m sorry. I can see how someone with very thick fingers might struggle.
My father has a similar issue. I watched him write a message on his phone and I think I found the issue with him. He cared very much about the accuracy of each letter. Doing so made him slow and caused a lot of unhappiness.
My advice to him was to stop caring and just trust autocorrect. It will autocorrect away mistakes and enables people to write quickly. But if you try to get everything letter perfect as you go there is no point to it. It’s a different mindset.
As for programming yah I understand the discomfort here too. I slow down a bit when at the command line on my phone too. Particularly with the flags and such. I recommend the fish shell though. It has an amazing autocomplete set of features above and beyond even zsh. It’s not just looking at histories. It looks at man files and gives autocomplete recommendations. Just Ctrl-F to complete.
As for programming, I have to ask, do you program on your phone? I would use my laptop here.
My “raw” error rate is quite high. My actual output error rate is quite low. I can’t speak for swipe keyboards though. I just use the standard tap keyboard. For me the in context predictive autocorrect works wonders.
With my old keyboard phone things were slower because I had to press down on physical buttons. With a touch keyboard I just lightly touch type without the need for effort or rechecking. It all just works out.
As for me I could never go back to a slide out setup. It was very klutzy and thick. Like 2cm thick. Crazy.
I’m happy with touch keyboards because they are faster for me and enable things like folding phones. But to each their own.
Thanks for showing me how passionate you are here. :)
Edit: the ellipsis leads me to believe that you might have been into tech while the n900 was around. You write with the passion of a n900 user. Did you have one?
It’s a figure of speech. No need to get your knickers in a twist.