So maybe GoPro should make an iPad case?

Appeared on Fark a couple days ago, with the comment that the (unprotected) camera they used to document the flight and fall also survived. So...

This client is not keen on having executables increase in size by 125% (e.g. from 500k to 1125k). We have warned them that this will result in a program that is hard to maintain as the tools become superannuated, and they have agreed that if issues develop, they will cover our costs of rebuilding on a more modern platform to get assistance from MS, but that they will then want the fix back-propagated. It is something to do with the size of their distribution media, I believe. While CD-ROM has been pretty much superseded by DVD-ROM, there doesn't seem to be a lot on the pipeline larger than 4.7GB.

It's more "The client will pay for his decision."

No, they use SLM, which IMHO is only slightly better than VSS, and which seems, according to MS devs, to have as its sole advantage over VSS that it is CLI only and does not suffer the slowdowns of the visual windowed interface.

Not to say I am a rabid VSS supporter; I have considered switching. As with any system, of course, there is the cost of switching -- how much does it cost to import ten plus years of VSS data? If it could be done, I'd definitely be interested in switching to something better supported (read: FOSS)...

I won't argue about VSS' flakiness, but I will say that so far it has not failed us when we needed to revert. The flakiness starts when you want to do something less than straight-arrow, like split a project, and there a lot of the flakiness actually comes from the integration with the other VS tools. In my experience. Your mileage may vary.

We've found that going with the Latest and Greatest causes a lot of grief: M$ has elected to change a lot of the way version control works with their 2010 update to VSS, for instance, and as we still have clients who insist on the more compact executables produced by Visual Studio 6 (11 years old now), we cannot upgrade any further than VS2008. On my current build machine, for instance, I have every VS version between VS6 and VS2008, and I use every one of them for building some part of some product.

That said, some form of version control is critical. All it takes is one fumble-fingered tech erasing a project (which is what spurred our installation of a source control system) or one showstopper bug introduced into the shipping product with no record of how it got there, and you quickly learn the value of having backed-up old source versions.

Your shop shows all the hallmarks of the single-developer shop that grew without direction, as they all do initially. I'd strongly suggest that it would be in your interests to try and get at least minimal tools together... and to update to a recent Java before you start losing sales because of an outdated and now unsupported platform.

We're all living in the Matrix already, coppertop. The machines won, and are now using us as their power source. The movie got one big thing wrong, though: heat is of no use to the machines. They have us on the equivalent of treadmills, making their generators spin.

Ah, but the BB gun will not stop the interference unless you somehow manage to short out the bulb and pop the breaker. Instead you'll get a free-air arc...

It's much more likely to tell the tale if you ask the neighbor.