I really had problems going this route (Ubuntu host with Windows guest). While the guest ran in VB reasonably well, trying to snapshot a baseline image and generally use VBox differencing disks quickly ran me out of space on the host SSD.
Even with a 256GB drive and a number of tweaks like hosting the Windows pagefile and temp from a passthrough disk, disabling Windows automatic updates, and using an immutable disk containing the OS install/multi-attach for copy-on-write behavior, VBox still used a ton of space to track the differences from my baseline snapshots. Even starting the VM quickly consumed 10-20GB in the new disk image. Was hard to conclude anything other than it wasn't a viable "dual workstation" setup and I capitulated and moved to Windows 10.
Sucks, because it was really quite nice to have a unix under the hood, though WSL makes this a bit more tolerable in Win 10 AU.
It's inappropriate to target space saving when it comes virtualization, as it's not what hypervisors are designed for - if so, a hypervisor would have to interpret the underlying FS calls, and optimize them space-wise.
Besides, I think pretty much all the formats behave the same; qcow2 for example, does not optimize on the fly the writing of zeros.
All in all though, if you ultimately moved to a native Windows 10, therefore allocated X space of native disk, the space requirement is not different from having only a virtualized one with X space of virtualized disk (heck, you could even pass a partition).
Having said that, if 10-20 GB of space are taken so quickly on boot, it may be worth investigating (you could even vim the diff disk), but I find your claim somewhat misleading, as you're likely experiencing this on the first absolute boot after taking then snapshot, but not on the subsequent ones; therefore, if your system steadily takes 20+20 GB of space, that's a perfectly reasonable requirement.
A 512GB SSD is minimum for multi-VM dev. I have Ubuntu host and ran out of space after a few VM's on 256GB. I wasted a lot of time(money) trying to slim down the Windows installs, a few hours&dollars to upgrade SSD was good investment ...
It's worth pointing out that this style rule itself is optional, which is to say they're not making a recommendation here, just providing an example of what applying the rule would look like. It carries the same weight as, say, the optional rule about grouping CSS sections and including a section comment[1].
My experience has been the auto-upgrade works without requiring reinstall (and indeed just did so to GA last night). I don't think there's any specific fresh install requirement.
> They are conspiring to replace an existing employee. That says enough. If the organization were "healthy" they would be upfront with the existing manager and allow him/her to gracefully exit.
You seem to start from this very distrustful premise and never look back.
Would you say the same of someone who gives significant notice of their departure (say, a retirement or medical situation) to the relevant supervisors but doesn't inform subordinates until a replacement is on board? What if that person were a fairly high ranking one in the organizational structure, as it sounds this one is?
Confidential replacement is pretty typical when the outgoing leader has no apparent (temporary) replacement and transitioning duties twice would be difficult/disruptive. It's not broken culture to ensure the wheels keep turning despite a pending high-profile departure.
Not to mention, if a manager and two tech leads are involved, it's pretty likely the outgoing manager is at least peripherally aware of the situation. You could very well be right about this employer, but the presumption that the nature of the search is somehow underhanded or deceitful is pretty one-sided.
> You seem to start from this very distrustful premise and never look back.
The OP writes "they want to replace the existing manager". Chances are this would have been phrased "the existing manager is moving on" if no deceit was involved.
> Would you say the same of someone who gives significant notice of their departure
When to make the information known to the rest of the team should be a management team decision. I don't think there is a one-size-fits-all answer.
> What if that person were a fairly high ranking one in the organizational structure
Finding a replacement before announcing the departure to the team makes sense. It sounds like in the OP's situation the outgoing manager is not aware of his/her status.
> Confidential replacement is pretty typical when the outgoing leader has no apparent (temporary) replacement and transitioning duties twice would be difficult/disruptive. It's not broken culture to ensure the wheels keep turning despite a pending high-profile departure.
Not sure if you are referring to keeping it confidential from the employee being replaced or from the rest of the team.
> ...the presumption that the nature of the search is somehow underhanded or deceitful is pretty one-sided
I think you are suggesting that it is appropriate (not deceitful) to attempt to hire the replacement before informing the current manager. Ideally in situations where something isn't working out, both parties can collaborate to phase things out in a mutually respectful way, especially in a startup.
Yes, in big companies there is an HR department and all sorts of reasons why "typical" HR practices make sense. But a person joining a startup should feel that the team he/she is joining is not typical and has the sort of integrity to act cooperative (in a game theoretic sense) in these sorts of scenarios.
FWIW these sorts of scenarios are inevitable. Sometimes employment arrangements don't work out. How they are handled offers an indication of the character of the management team.
Yes. If the existing manager were retiring or moving on, then they would be one of the people interviewing their potential replacements. They know the particular role's needs and issues better than anyone else.
I use it daily (running both Visual Studio 2015 and Visual Studio Code). For me, it's a Sublime Text killer.
We have some small node apps, endless python scripts and I routinely deal with configuration files, XML, JSON, even just machine-formatted flat files. It's very good at doing that when I need it to, and being a lightweight IDE when I drop into node or python. Anything that doesn't require me spinning up the full IDE but comes with good editing and search (what I was using Notepad++ and Sublime for in the past) is a win for me.
There are some really nice features in there too, the extension ecosystem is very active and it does what I need it to. Pleasure to use.
> Because tfs is dying. Why port over tooling for a source management system that is on it's deathbed?
[citation needed]
Visual Studio Online (which is pretty much TFS in the cloud) is alive and well. And improvements made to VSO have been shipping regularly as updates to accompanying TFS on-prem.
Are you confusing TFS with Team Foundation Version Control (TFVC)? TFVC is also pretty popular as a Visual SourceSafe replacement and has been very stable for us, though the recent support of Git in Visual Studio and TFS has us considering it as an alternate workflow for some smaller projects. I think the support of Git is great, but knowing MS (and what they've said through their usual surrogates) I don't think TFVC is going anywhere anytime soon.
> Visual Studio Online (which is pretty much TFS in the cloud) is alive and well.
Visual Studio Online supports Git. So, no, it is not "TFS in the cloud." TFS and Visual Studio Online are very loosely coupled.
> Are you confusing TFS with Team Foundation Version Control (TFVC)?
I'm not confusing anything, I just picked one of Microsoft's many acronyms they use for it. Even Microsoft's own consultants call it "TFS" when talking about Visual Studio Team Services in Visual Studio Online. So if Microsoft's own consultants are "wrong" then I am in good company.
> I don't think TFVC is going anywhere anytime soon.
I do.
It doesn't work very well: it sends way WAY too many files up and down constantly, it has no concept of a pull request, offline mode sucks, branching/merging is expensive as all heck (inc. disk space, bandwidth, time, any metric), and even Microsoft's internal teams are utilising Git and Github.
I've used both on VS Online, no comparison, and Microsoft's own staff seem to agree. It is only a matter of "when" not "if" TFS will die and Git will take its place (although I suspect Perforce will survive on the Windows team within Microsoft).
Again, you're citing the source control system as the primary feature. TFS is an entire application lifecycle management suite, not just version control. You seem to (continue to) ignore this. Its closest analogue is probably the entire Atlassian family of products.
On TFVC:
> it sends way WAY too many files up and down constantly
It sends literally zero files anywhere until you interact with the server, as any sane server-based version control system would do. I don't know about your workflow but I don't know what you consider a reasonable amount of I/O to sync a workspace. You can elect "Local" workspaces since around TFS 2012 which can work completely disconnected if you choose.
> branching/merging is expensive as all heck
It's folder-based branching and can be done very quickly/cheaply if you don't store your entire company in source control. And how well does Git handle large files? Git is opinionated on branches and creates them cheaply/quickly; TFVC evolved from CVS-type systems where this was not the prevailing mindset, but again I don't know what you're considering "expensive." Maybe where you work?
> even Microsoft's internal teams are utilising Git and Github
Which isn't evidence of anything other than it's their current tool of choice. That has a lot less to do with future direction of their enterprise products than you're assuming here.
> Microsoft's own consultants
> Microsoft's internal teams
> the Windows team within Microsoft
Do you have insider info or are you just trying to sound like you do?
> "Most of our customers still use TFVC and we value this tremendously. Most people in Microsoft still use TFVC. Most new projects created today on VS Online choose TFVC."
Etc. It's quick and to the point, go read it. And again, has there been some sea-change at MS over the last year on source control? Quite possibly. But so far you've offered nothing but your opinion.
I think you're confused about what TFS is. I use tfs daily, but I don't use it for source control. I use git for that. Source control isn't even the main thing tfs does. TFSVC (the version control part) may be dying, but the rest of it seems pretty solid.
The bigger crime is that there's a perfectly good permalink for every FB post, but nobody seems to use it to reference content, when @-ing a friend is easier, quicker, and supported on every client.
There's no requirement that you use your home address for registrars (or the IRS, for that matter). It's also not terribly expensive to get a PO Box/virtual office address, and if you're concerned about privacy then it sounds like it'd be worth it to you.
https://www.coursera.org/specializations/algorithms
Can't recommend enough. The material and instruction are top-notch.