7
redman
68d

Okay ... we made it through the week, before the weekend starts, time for a friday-poll ...

What do you prefer using for development (and why): bare metal or a virtualised system?

Comments
  • 4
    I am guessing you're asking for what our development environment looks like?

    I am using Docker with a custom Dockerfile

    Why? I work in a team and this way we know that everyone has the same development setup (versions, tools etc.)
  • 2
    Depends on what I'm doing, usually Docker containers but simple node or python scripts can be done on my local system 😁
  • 1
    @incognito The question is what do you use: bare metal or a virtualised system?

    In other words, do you have real hardware/server/pc/whatever or do you use a virtualised system.

    And why go for real or virtual?
  • 3
    @redman virtual to so that a server can create multiple different env, it’s stull bare metal but with virtuals underlying
  • 1
    @devTea true, there is always bare metal under it.

    I have an actual server present that I only use for the dev game. But I also know people who use virtual systems like openshift.io that are not on premisis.
  • 2
    @redman it’s cheaper for a small company or startups
  • 4
    Bare fucking metal.
  • 1
    For work: Bare metal, because I have one system that has to do one job.

    At home I used to use virtualised systems (VirtualBox), because I use the computer for a lot of non-dev things, too (day-to-day use, gaming, media, internet, experimenting etc.). And I had a lot of very different environments, with different compilers, IDEs/editors, tools and different OSs needed.
    At the time I try to shift to a less virtualised system, with the graphical applications installed by a build script (preferably with snap) and the non graphical parts with Docker and a custom Dockerfile.
    At this point I have to think a lot of things ahead, but I it will make development a lot easier in the long run, starting with performance/start time up to "How do I get hardware accelerated OpenGL to work inside a virtual machine? Hmpf..."
  • 2
    Depends on the use case..
  • 4
    Am I the only one who understands “bare metal” as without an operating system (or with a minimal RTOS), taking full and direct control of the hardware?
  • 2
    @7400 bare metal is just a box with no hypervisor running
  • 3
    @xalys: Hm, it does seem to have a different meaning with servers than what I'm used to.
  • 1
    Over here, bare metal means physical hardware
  • 2
    At work, we can't store any client data on our physical machines so we use EC2 instances. They are deployed using Cloudformation so everyone has the same setup and everything they should need is installed on creation.
  • 3
    @7400 These days, there are people who babble of "bare metal" and refer to using vanilla JS. They have no fucking idea what "metal" even means.
  • 2
    Dockerized environment makes me happy and sane.
  • 3
    Container. Definitely container. An environment shouldn't be more than a config file
  • 1
    I'll add my two cents as well...

    I prefer real hardware over virtualised hardware. It might be a emotional thing, but if it works on real hardware, it will work on virtualised as well, other way around doesn't feel real to me.
Your Job Suck?
Get a Better Job
Add Comment