So I'm currently reinstalling AvP2 for some good old Monolith action, and I noticed that the default install folder is something like "C:\Program Files\Fox\Aliens vs Predator 2"


WHY DOES IT FEEL THE NEED TO HAVE A "FOX" FOLDER?????

because, just because. JUST BECAUSE!!!

Because that's the publisher.

It's extremely common to include publishers in the install hierarchy.

It makes things a bit neater when you're looking for something. The main thing though is that there isn't much consistency about it. Some publishers will and others won't.

Yeah, but it's a common Windows mess in general, and has been for a decade, I don't see why one would get up in arms about it at this point, over one instance.

As much as I like consistency too, Windows has always been the wild west for application developers.

Yeah, lots of games do that, unfortunately. I find it very annoying, especially when they force you to use the publisher subdirectory.

And if they would have taken some time to design the architecture many of those problems would never have shown up.

The best install systems I've ever seen are on PC-BSD and OSX. Self contained PBIs and just dragging and dropping a single file in each case respectively.

Because foxes are so incredibly awesome they eat aliens AND predators for breakfast. Duh.

I don't disagree. At the very least they could have offered style guides and encouraged developer participation at a much earlier opportunity.

IMHO they tend to be unreasonably lenient about poor coding practices. Sometimes it's hard to imagine that it's not an incredibly shrewd way of harming the competition like with their lax DSDT validation for ACPI.

BECAUSE FOXES ARE AWESOME THAT'S WHY

The problem is that they were using a non-standard implementation and providing workarounds for common faults. At that time the standard implementation that people were supposed to be using was from Intel, IIRC they were the driving force behind ACPI at that time, but anyways, the Intel tools were available to everybody to validate against.

Unfortunately, you'd come into cases where you couldn't boot anything other than Windows because the parties writing the DSDTs were validating against the slightly non-standard MS implementation rather than the freely available Intel implementation that the opensource developers had access to.

Suggesting that it's an antitrust violation or purposeful sabotage of the opensource community is probably a stretch. But by the same token it's inline with the MS embrace, extend and extinguish protocol that caused so much trouble in the '90s.

Rename the folder. That'll show them.