this post was submitted on 28 Jan 2024
2033 points (98.2% liked)

linuxmemes

21047 readers
1672 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] [email protected] 17 points 8 months ago (1 children)

    This is why I like Docker. It's basically "works on my machine" as a service.

    Similarly, I'm starting to really like dev containers. They're Docker containers with all the required dev tools already installed inside, and a config so that VS Code knows how to spin up a new container when you want to do dev work on the project. They use VS Code remoting - a VS Code server runs in the container and the regular VS Code desktop app connects to it.

    I was recently dealing with a project that has some Ruby dev tools and it was 100x easier to deal with since they were using dev containers.

    [โ€“] [email protected] 2 points 8 months ago

    Well now I need to learn all about this.