I concur. MSBuild is shit. sources and dirs forever. I like to know what I'm linking into my binaries - if they would just fix manifest generation and c# build stuff in the public version, I'd have a very hard time even sympathizing for msbuild folks.

The compiler at least through and after Windows 7 was most definitely a msft compiler. I'm actually really surprised at this claim. Why do you think all the MSFT devs are stuck in C89?

The executive is pretty much unrestricted in how it chooses to deal with classified information, since that's where the ability to classify stuff comes from.

Watch the entire video. They attacked people attempting to help the wounded, as well.

Huh - sure enough they now leverage the compiler from outside the WDK.

I sure as shit wouldn't pay for Visual Studio. I guess it's time for some other compilers to step up!

It's worth noting that Visual Studio wasn't always free.

More to the point, though, I doubt they're going to stop shipping the WDK, and that DOES include a C compiler. I hope you like nmake, though!

Yeah. You definitely gotta shop around in order to find good deals, but they are out there. I've had had particularly good experience in Canada, actually, for stuff that will normally get you chucked out of a datacenter in the US.

She'll be held in contempt until the judge understands how fucked up this situation is. Could be years.

This situation is the precise reason we have the 5th Amendment - so that people can't be compelled to make testimony against themselves and then be jailed indefinitely on a whim when they 'refuse' to comply (or, when someone has apprehended the wrong person, or ...).

Out of an entire page of comments, you are the only one to get it right.

The legalese here has to do with code from ibooks being exported into the file, so that even if they have fixes for css bugs, etc, in the future, the formatting preferences can be preserved.

RE: Bison. Even after bison's licensing, some software companies are nervous about it - not that bison community is going to come after them - but that they might not completely own the binaries they produce. It's a really tough legal conundrum (code generated from a recipe), but luckily virtually everybody seems to be on the same page, insofar as useful tools like these should be used judiciously and without restriction.

In theory, Apple is being defensive, which is a little sad, but it is understandable Nominally, they pick the wrong side of this issue in order to protect their CSS.

Additionally, though, they create a headache for their users, which is something of a mortal sin in my book, and require many hours of additional labor to prepare books for other vending platforms. I very much wish that Apple would get off of their anti-competitive high horse and focus on building good tools without noxious restrictions. They have come pretty far by being very agressive about building a software silo. But at this point Apple needs to begin to transition to a softer sell on its platforms, or it will become another Bad Era Microsoft.

Ever used ithreads? Ever?

Great! Now maybe the perl folks can afford to fix their epic memory leaks that have been their bug list for the better part of a decade.

"The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized."

Throwing tents into dumpsters, without issuing a 'vacate or your property is forfeit' order seems like a clear violation to a non-lawyer.

Lawyers? Or have I simply missed something requiring the demonstrators to disperse?

No new code (except in the rare case where you are writing a tool to migrate stuff out of the VirtualStore into a new unprivileged user data directory) should reference the VirtualStore. That was created because ignorant devs couldn't wrap their heads around ACLs and didn't listen when MS told them that there's things out there that aren't admins.

This will absolutely not make its way downstream into an existing RHEL release. Maybe future releases.

I agree the wow64 fs and registry direction is confusing as hell. With the benefit of hindsight, I suspect they would have designed that differently (I will just assume it was fundamentally possible, if a bit more work in the short term.)

c:\winnt vs c:\windows vs c:\win vs e:\foo are all theoretically valid windows directories, though. That's why windows has an API for finding the Windows directory.

Red Hat jumped the shark in 1997. Once you go slack, you never look back. You do continue to look forward, though.