3 ms·

If it's so painful for you, maybe try dropping the IDEs and web editors? To be clear I know that there's nothing wrong with liking IDEs, I'm not that much of a

by simias 6y ago

If it's so painful for you, maybe try dropping the IDEs and web editors? To be clear I know that there's nothing wrong with liking IDEs, I'm not that much of a purist, but there's also nothing wrong with not using them. Over the past decade I've worked with all kinds of technologies, from the web to bootloaders, from Perl to Rust and I've done it all without using any IDE. Again, I'm not advocating against IDEs out of principle, it's just that if your current setup is so frustrating for you at the moment I really think you should consider something a bit radical to improve it. When something in my code workflow feels "sticky" I always find that it's worth taking the time to find a solution, after all we spend so much time using these tools...

sumtechguy 6y ago
I personalty use both types. IDEs have their place. So do the 'minimal' editors. The biggest gripe I have with modal editors like vim is they seem to adhere to the path of most surprise instead of least. With most IDEs they try to get you into moving text into a file quickly. A modal editor you first have to learn how to just change modes. I can not number the amount of times I started typing and had the conclusion 'I have no idea what I just did to my document and what state the editor is in now'. Which is maximum surprise :) I get why they were made in the first place. They are a thing of teletype machines. Yet we keep this mode style editor around. It is interesting. I personally am kind of stuck with this right now due to the way my work manages machines. So I am stuck with whatever the box has on it. So minimal customization is allowed.
- simias 6y ago
  There's definitely a steeper learning curve to modal editor, that's for sure. And vim is pretty bad at communicating what state it's on, especially with the default config. But my point is not so much about modality (I used emacs for a very long time before switching to vim) it's more that the parent seems to really like this kakoune editor, so why wouldn't he just use it full time instead of switching constantly?

by simias 6y ago

sumtechguy 6y ago

I personalty use both types. IDEs have their place. So do the 'minimal' editors. The biggest gripe I have with modal editors like vim is they seem to adhere to the path of most surprise instead of least. With most IDEs they try to get you into moving text into a file quickly. A modal editor you first have to learn how to just change modes. I can not number the amount of times I started typing and had the conclusion 'I have no idea what I just did to my document and what state the editor is in now'. Which is maximum surprise :) I get why they were made in the first place. They are a thing of teletype machines. Yet we keep this mode style editor around. It is interesting. I personally am kind of stuck with this right now due to the way my work manages machines. So I am stuck with whatever the box has on it. So minimal customization is allowed.

simias 6y ago
There's definitely a steeper learning curve to modal editor, that's for sure. And vim is pretty bad at communicating what state it's on, especially with the default config. But my point is not so much about modality (I used emacs for a very long time before switching to vim) it's more that the parent seems to really like this kakoune editor, so why wouldn't he just use it full time instead of switching constantly?