If I had to explain a failure in production I would much rather say "due to availability of old hardware, we ran this on a different version of Windows/inside a VM/inside a Windows compatibility layer/Wine/ReactOS" than "we vibecoded the entire driver stack from scratch, go ask Claude why the plant blew up lol".
Running the same software in a different environment is unlikely to cause issues. But with vibe coding, you're throwing away the code the manufacturer certified as working, and the best possible outcome is it bricks your hardware in dev before things escalate to a post-mortem.
Comments
If I had to explain a failure in production I would much rather say "due to availability of old hardware, we ran this on a different version of Windows/inside a VM/inside a Windows compatibility layer/Wine/ReactOS" than "we vibecoded the entire driver stack from scratch, go ask Claude why the plant blew up lol".
Running the same software in a different environment is unlikely to cause issues. But with vibe coding, you're throwing away the code the manufacturer certified as working, and the best possible outcome is it bricks your hardware in dev before things escalate to a post-mortem.