{"comment":{"url":"https://api.github.com/repos/benbaptist/minecraft-wrapper/comments/12075341","html_url":"https://github.com/benbaptist/minecraft-wrapper/commit/a662be8e8d2cee4c2e9b22aabc33b87303dbefeb#commitcomment-12075341","id":12075341,"user":{"login":"benbaptist","id":353809,"avatar_url":"https://avatars.githubusercontent.com/u/353809?v=3","gravatar_id":"","url":"https://api.github.com/users/benbaptist","html_url":"https://github.com/benbaptist","followers_url":"https://api.github.com/users/benbaptist/followers","following_url":"https://api.github.com/users/benbaptist/following{/other_user}","gists_url":"https://api.github.com/users/benbaptist/gists{/gist_id}","starred_url":"https://api.github.com/users/benbaptist/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benbaptist/subscriptions","organizations_url":"https://api.github.com/users/benbaptist/orgs","repos_url":"https://api.github.com/users/benbaptist/repos","events_url":"https://api.github.com/users/benbaptist/events{/privacy}","received_events_url":"https://api.github.com/users/benbaptist/received_events","type":"User","site_admin":false},"position":null,"line":null,"path":"","commit_id":"a662be8e8d2cee4c2e9b22aabc33b87303dbefeb","created_at":"2015-07-09T01:54:57Z","updated_at":"2015-07-09T01:54:57Z","body":"You don't need a system pre-installed with Linux. It's easy to install yourself. That being said, no, VMs are plenty efficient. Many Intel and AMD processors feature virtualization acceleration to help make VMs as fast as possible. More often than not, it's more than enough, especially for Minecraft servers. Factor in the fact that Java 1.8 tends to be a bit faster under Linux, and also that a light distro such as Ubuntu Server (not the lightest, but pretty good) has very little overhead, it'll be fine. I guarantee you it'll be 50 times better than dealing with Windows bugs all the time.\r\n\r\nAs for plug-and-play, it 100% depends on the hardware (computer itself, peripherals, etc.) you're using. In my own experience, I actually find Windows to be quite the opposite - almost everything requires me to install some sort of silly driver. Hell, I just installed Windows 7 on a laptop recently and I couldn't even use the ethernet port let alone wifi or even USB disks. I would have no clue how to get drivers on there if it weren't for the fact that I had a Linux partition (that I had just freshly installed and had wifi, ethernet, and USB drives working out-of-box), and I had used that to copy the files over. Once I got that going, I couldn't even use my USB audio card with it without more drivers. All of this worked out-of-box on Linux. Obviously this varies between hardware, but I certainly wouldn't say that one or the other is more plug-and-play. Just depends on stuff. :P \r\n\r\nAs for the last paragraph, this is *far* from a flaw in Linux. Having file locks like this cause severe issues with servers. It's a *serious* hindrance, especially in a server environment, and is MOST CERTAINLY NOT something you want for one. It's an exploit vector (if software in a controlled environments manages to simply open one file read-only, it's locked forever and other important processes can't handle it). It is likely to cause instability and random issues and can take forever to resolve, such as these issues. It's *never* been an issue in Linux, and there's no such thing as having issues with this sort of stuff. If a file is indeed being read when it is deleted, it is physically kept on disk until the file is closed in which the free space is regained. In crucial scenarios where there's not enough space, I believe the kernel will just force close it and .read()/.write() operations on it will cause it to throw a perfectly reasonable error which programs can easily catch (and should catch). "}}