3 ms·

> 99.9% of the time the answer will be "Well, I haven't set that up yet...but look at this multiple cursor trick!" Ah yes, the classic "takedown" with the inve

> 99.9% of the time the answer will be "Well, I haven't set that up yet...but look at this multiple cursor trick!" Ah yes, the classic "takedown" with the invented statistic about what people "probably" haven't done while "probably" focusing on something less important. Bravo. Side note: most Vimmers don't use multiple cursors... it's 99.9% of them, I believe!

29athrowaway 2y ago
Still better than the circular arguments like vim is faster because vim is faster.
- sodapopcan 2y ago
  It’a not better, they are both worse. The best editor is the one you know. I also know lots of people who use IDEs and don’t use most of their features.
  - 29athrowaway 2y ago
    If we have a test or a linter that prevents a problem, that runs in a couple of milliseconds, and you didn't run it because you are too cool to run it, then we are no longer talking about subjective preferences about tools. We are talking about responsibility. If your code caused data loss on production because you are LARPing about being a hotshot instead of adopting the processes that keep the code running I don't care how fast your editor is.
    - sodapopcan 2y ago
      Lol, you're exactly who I'm complaining about. I do agree with you: I also dislike people who don't learn their tools and don't do the things you're talking about. But just because you're using an IDE doesn't mean you're going to use all of its features. Conversely, if you're going to use a text editor, you absolutely have to ensure you have that stuff.
    - 12345hn6789 2y ago
      Does your team have required code reviews? This might help reduce production incidents - sent from my terminal
      - 29athrowaway 2y ago
        Checks running on continuous integration is the mitigation for not having used a linter during development in this case. The linter feedback would take longer to get back to the developer though, increasing the "cost of change".
    - xigoi 2y ago
      What does the choice of editor have to do with whether you run tests?

29athrowaway 2y ago

Still better than the circular arguments like vim is faster because vim is faster.

sodapopcan 2y ago
It’a not better, they are both worse. The best editor is the one you know. I also know lots of people who use IDEs and don’t use most of their features.
- 29athrowaway 2y ago
  If we have a test or a linter that prevents a problem, that runs in a couple of milliseconds, and you didn't run it because you are too cool to run it, then we are no longer talking about subjective preferences about tools. We are talking about responsibility. If your code caused data loss on production because you are LARPing about being a hotshot instead of adopting the processes that keep the code running I don't care how fast your editor is.
  - sodapopcan 2y ago
    Lol, you're exactly who I'm complaining about. I do agree with you: I also dislike people who don't learn their tools and don't do the things you're talking about. But just because you're using an IDE doesn't mean you're going to use all of its features. Conversely, if you're going to use a text editor, you absolutely have to ensure you have that stuff.
  - 12345hn6789 2y ago
    Does your team have required code reviews? This might help reduce production incidents - sent from my terminal
    - 29athrowaway 2y ago
      Checks running on continuous integration is the mitigation for not having used a linter during development in this case. The linter feedback would take longer to get back to the developer though, increasing the "cost of change".
  - xigoi 2y ago
    What does the choice of editor have to do with whether you run tests?