3 ms·

This kind of response is supremely unhelpful. I work at a company with a large team, I'm not just going to tell all 300+ people to drop everything and rewrite t

by notJim 6y ago

This kind of response is supremely unhelpful. I work at a company with a large team, I'm not just going to tell all 300+ people to drop everything and rewrite the entire dev stack. Docker has become the de facto standard for dev environments.

rowanG077 6y ago
My comment was flippant because your comment was useless. Of course if you decide to use something like docker you will force yourself into a performance corner. This would happen with literally any piece of software. It's not then valid to use that as a way of requiring a better cpu. No what you need is to get your development environment in order. Btw docker is only standard for CI systems. Never would I advise anyone to actually use docker for local development let alone 10 docker instances at once. It's just pure insanity.
- notJim 6y ago
  Why is it not valid to buy a better cpu to have a better dev environment? What does validity even mean here? I was never told I had to check in with you when making decisions. Before docker I remember spending tons of time setting up dependencies locally on machines when starting a new job, or maintaining puppet scripts to do so. And then since machines change over time, and run a different OS, your dev environment never quite matches prod. A $500 CPU is drastically cheaper than the bugs, headache, and time suck of maintaining a dev env.
  - rowanG077 6y ago
    Of course you can buy a better Cpu. It's not a valid argument in this context. The OP was talking about needing a better CPU because his large C++ project takes a lot of time to compile. That's something inherent to C++ programming. You then make the argument that js devs also require better CPUs because your js project use 10 docker instances. That's not valid logic since docker and js have nothing to do with eachother. There are many alternatives to docker which don't cripple your computer. Nix is the best one.
    - hombre_fatal 6y ago
      FYI, your objections here don't make sense. Developers of any kind can benefit from better horsepower. Whether it's having to run a lot of Docker containers, a large C++ project, or a large Webpack project. Nitpicking and criticizing someone's dev environment is irrelevant. If you don't like their example, I'm working on a JS project where I run a lot of local VMs to locally test the web client in different configurations. It would continue to be a bizarre response if you thought it was time to tell me to "just use browserstack.com" or something. Software isn't as easy as we think.
      - rowanG077 6y ago
        You misunderstand what I said. I didn't say any developers won't benefit from having a better CPU. What I disagree with is the statement that JS developmant is comparable in this way to C++ dev. In C++ dev the required horsepower is INHERENT because of the language. This is simply not the case for JS development. If you require high horsepower for JS dev it's because you work in a dev environment that results in requiring that horsepower. It is a CHOICE someone made when setting up the dev environment. That same choice could be made for any dev environment and doesn't have much to with JS.

by notJim 6y ago

rowanG077 6y ago

My comment was flippant because your comment was useless. Of course if you decide to use something like docker you will force yourself into a performance corner. This would happen with literally any piece of software. It's not then valid to use that as a way of requiring a better cpu. No what you need is to get your development environment in order. Btw docker is only standard for CI systems. Never would I advise anyone to actually use docker for local development let alone 10 docker instances at once. It's just pure insanity.

notJim 6y ago
Why is it not valid to buy a better cpu to have a better dev environment? What does validity even mean here? I was never told I had to check in with you when making decisions. Before docker I remember spending tons of time setting up dependencies locally on machines when starting a new job, or maintaining puppet scripts to do so. And then since machines change over time, and run a different OS, your dev environment never quite matches prod. A $500 CPU is drastically cheaper than the bugs, headache, and time suck of maintaining a dev env.
- rowanG077 6y ago
  Of course you can buy a better Cpu. It's not a valid argument in this context. The OP was talking about needing a better CPU because his large C++ project takes a lot of time to compile. That's something inherent to C++ programming. You then make the argument that js devs also require better CPUs because your js project use 10 docker instances. That's not valid logic since docker and js have nothing to do with eachother. There are many alternatives to docker which don't cripple your computer. Nix is the best one.
  - hombre_fatal 6y ago
    FYI, your objections here don't make sense. Developers of any kind can benefit from better horsepower. Whether it's having to run a lot of Docker containers, a large C++ project, or a large Webpack project. Nitpicking and criticizing someone's dev environment is irrelevant. If you don't like their example, I'm working on a JS project where I run a lot of local VMs to locally test the web client in different configurations. It would continue to be a bizarre response if you thought it was time to tell me to "just use browserstack.com" or something. Software isn't as easy as we think.
    - rowanG077 6y ago
      You misunderstand what I said. I didn't say any developers won't benefit from having a better CPU. What I disagree with is the statement that JS developmant is comparable in this way to C++ dev. In C++ dev the required horsepower is INHERENT because of the language. This is simply not the case for JS development. If you require high horsepower for JS dev it's because you work in a dev environment that results in requiring that horsepower. It is a CHOICE someone made when setting up the dev environment. That same choice could be made for any dev environment and doesn't have much to with JS.