2 ms·

> You're deploying via VS Code? If so, that's a weird pattern. I don't think it's a weird pattern, maybe a slightly legacy one but not out of the ordinary. I'v

> You're deploying via VS Code? If so, that's a weird pattern. I don't think it's a weird pattern, maybe a slightly legacy one but not out of the ordinary. I've seen this pattern used at multiple places (not implement by me). It makes sense if you have special use-cases where you need to use physical hardware and/or a local stack is too heavy or complicated to run.

presentation 4y ago
Though why does it need to be in your editor vs some command line tools or something else?
- danuker 4y ago
  So you can deploy at a moment's notice. Why run a command instead of hitting a key combo? Or even deploy as soon as tests pass? Software should allow that. Especially software for writing other software.
  - Drew_ 4y ago
    Or just run a command with a key combo. Or setup your test script to run a command afterwards. This is what every IDE is doing in the background.
    - 6510 4y ago
      Then we tell the new upcoming developer that the hard part is setting up your tools. How long will this take? He asks. Oh, you answer: This will take decades! It's a wild, every man for himself kind of ride. You build a battle-royal out of abandon-ware plugins that each almost do what you want until your powerlevel finally rises to the point you just delete everything and use the terminal. The terminal is an emulator that mimics a physical device from 1941 you see, as its a physical device, there are no ever-tinkering developers bloating or [indeed] sunsetting your tools. You will finally be left alone, still in the dark but you get a cursor that no one can take away from you.
goodoldneon 4y ago
Sorry, “weird pattern” was a poor choice of words. I just meant that it’s an approach that isn’t common so it’s understandable that VS Code can’t handle it well. VS Code is best when it’s just an IDE. I even have to drop into the terminal for some Git stuff

presentation 4y ago

Though why does it need to be in your editor vs some command line tools or something else?

danuker 4y ago
So you can deploy at a moment's notice. Why run a command instead of hitting a key combo? Or even deploy as soon as tests pass? Software should allow that. Especially software for writing other software.
- Drew_ 4y ago
  Or just run a command with a key combo. Or setup your test script to run a command afterwards. This is what every IDE is doing in the background.
  - 6510 4y ago
    Then we tell the new upcoming developer that the hard part is setting up your tools. How long will this take? He asks. Oh, you answer: This will take decades! It's a wild, every man for himself kind of ride. You build a battle-royal out of abandon-ware plugins that each almost do what you want until your powerlevel finally rises to the point you just delete everything and use the terminal. The terminal is an emulator that mimics a physical device from 1941 you see, as its a physical device, there are no ever-tinkering developers bloating or [indeed] sunsetting your tools. You will finally be left alone, still in the dark but you get a cursor that no one can take away from you.

goodoldneon 4y ago

Sorry, “weird pattern” was a poor choice of words. I just meant that it’s an approach that isn’t common so it’s understandable that VS Code can’t handle it well. VS Code is best when it’s just an IDE. I even have to drop into the terminal for some Git stuff