4 ms·

> I’d have to give up my editor, my SCM, my code review practises, my deployment strategies, my whole way of working This is bad? Everything (besides maybe rev

> I’d have to give up my editor, my SCM, my code review practises, my deployment strategies, my whole way of working This is bad? Everything (besides maybe reviews) is horribly broken for most (modern) dev, so not sure it's a negative to just nuke it from orbit.

ReactiveJelly 6y ago
Every other language works fine with Kate and Git, my favorite editor and SCM. Having fewer options is not inherently good.
- tluyben2 6y ago
  No, but some people have to try. You are not mainstream, but the amount of people who think vscode is a lightweight and stable editor is slightly painful. Working every day with 100s of people seeing them killing/restarting is some sign we generally just gave up. Taking the current low bar as 'good enough' (or even great as some people seem to think it is) is definitely not a good think imho.
  - waheoo 6y ago
    When I ask why something isn't working with typescript in vscode at work people recommend restarting the language server with a keybind. I'd send them a table flip emoji but im pretty sure they wouldn't get it, they legitimately think they're giving me good helpful advice. They simply don't understand that if you need to restart something, said something is fucking broken.
    - im3w1l 6y ago
      Having to restart the language server is surely a disadvantage, but why make it be a dealbreaker? Maybe they see it as a cost worth paying?
      - throwaway_pdp09 6y ago
        Obviously it's a price worth paying but it should not be needed. MS could trivially collect these issues and fix them but they don't, people tolerate crappy software, the cost of bad software gets externalised not on the producer but amortised over many, many users, they tolerate it,the temperature goes up and the frog boils. If you put up with shit software, guess what you're going to get.
        waheoo 6y ago
        Doesn't help a common fix for node is `rm -rf node_modules`. Yikes, your fix for your software is just delete it and start over? What is so leaky about the build process.
      - waheoo 6y ago
        Its crap software, I can use the vim version just fine, no restarts, no problem. Aside from that, I don't need typescript, its being forced on me. I do want typescript, because it has advantages. A frustratingly broken workflow is far too high of a cost to pay though.
mcguire 6y ago
Smalltalk's editor...wasn't great. And I was a vi user at the time. (Not vim, vi.) SCM? Hah! The image was path-dependent. I seem to recall getting into a position where the code you filed out of one image couldn't be filed into a new image---you had to get a previous version and then upgrade. Deployment strategy? Ship 'em the image. Maybe you should disable the editor first, though. No matter how bad you think "modern" dev is, Smalltalk was worse.

ReactiveJelly 6y ago

Every other language works fine with Kate and Git, my favorite editor and SCM. Having fewer options is not inherently good.

tluyben2 6y ago
No, but some people have to try. You are not mainstream, but the amount of people who think vscode is a lightweight and stable editor is slightly painful. Working every day with 100s of people seeing them killing/restarting is some sign we generally just gave up. Taking the current low bar as 'good enough' (or even great as some people seem to think it is) is definitely not a good think imho.
- waheoo 6y ago
  When I ask why something isn't working with typescript in vscode at work people recommend restarting the language server with a keybind. I'd send them a table flip emoji but im pretty sure they wouldn't get it, they legitimately think they're giving me good helpful advice. They simply don't understand that if you need to restart something, said something is fucking broken.
  - im3w1l 6y ago
    Having to restart the language server is surely a disadvantage, but why make it be a dealbreaker? Maybe they see it as a cost worth paying?
    - throwaway_pdp09 6y ago
      Obviously it's a price worth paying but it should not be needed. MS could trivially collect these issues and fix them but they don't, people tolerate crappy software, the cost of bad software gets externalised not on the producer but amortised over many, many users, they tolerate it,the temperature goes up and the frog boils. If you put up with shit software, guess what you're going to get.
      - waheoo 6y ago
        Doesn't help a common fix for node is `rm -rf node_modules`. Yikes, your fix for your software is just delete it and start over? What is so leaky about the build process.
    - waheoo 6y ago
      Its crap software, I can use the vim version just fine, no restarts, no problem. Aside from that, I don't need typescript, its being forced on me. I do want typescript, because it has advantages. A frustratingly broken workflow is far too high of a cost to pay though.

mcguire 6y ago

Smalltalk's editor...wasn't great. And I was a vi user at the time. (Not vim, vi.) SCM? Hah! The image was path-dependent. I seem to recall getting into a position where the code you filed out of one image couldn't be filed into a new image---you had to get a previous version and then upgrade. Deployment strategy? Ship 'em the image. Maybe you should disable the editor first, though. No matter how bad you think "modern" dev is, Smalltalk was worse.