Do you develop on GitHub? You can keep using GitHub but automatically sync your GitHub releases to SourceForge quickly and easily with this tool so your projects have a backup location, and get your project in front of SourceForge's nearly 20 million monthly users. It takes less than a minute. Get new users downloading your project releases today!
OS History Roughly MS/DOS 3, MacOS 6, CP/M -> MS Xenix (On a TRS/80 Model 2 modded to 16b specs) -> Minix -> SLS -> MCC (IIRC) -> Slackware -> Red Hat -> Mandrake -> Debian -> Gentoo -> Ubuntu -> Windows Xp, Windows 7, MacOS X
With occasional excursions to BSD/386, NetBSD, OpenBSD, FreeBSD choking due to unsupported or fussy hardware, and later discarded due to a userspace that made Linux feel full featured and easy. And probably a few other visits to Debian along the way.
Yes, but what OS on the TRS 80? For that matter what TRS 80? 'Cause you got TRS DOS (IIRC), CP/M, Xenix, and maybe a couple other OSish options, on hardware that at times was barely related.
True. And also true that I don't do or say anything much that would be substantially offensive. But keeping my private life apart from my work life is something that I do value. And even if I didn't value it, the problem isn't nearly so much the employer as the employer's customers. I've quite deliberately not friended even my friends at work, because that's a social network that could easily expand to a lot of people in front of whom I have an obligation to behave with a modicum of professionalism.
Why would I have any problem working for a company that forced me to join a social network? I wouldn't join with the same profile that I used personally. I would keep my business activities with the site strictly segregated from my personal persona (if any). But if the cost of losing your privacy as an employee to a google or a Facebook accrues almost entirely to your employer, not to you.
What could cause the corruption: Cosmic rays, Bad sectors, Weird bugs
Why is this a problem: "Unless it is very carefully done, this kind of format could lose a lot of logging data as the result of a relatively small corruption"
(http://lwn.net/Articles/467892/)
You can script mysql databases, assuming the data files are intact, mysql is intact and runs on the server, and you have functioning tools and the skill to use them. ASCII logfiles will be readable in spite of spot corruption and can be processed with grep / head / tail -- if these primitives don't work it probably doesn't matter what's in the log.
The wise professional is intensely mistrustful of innovation. Innovation introduces new failure modes and deprecates tested methods and experience. Innovation is always born half baked, unreliable and unsupported. By the time all the problems are solved with a given innovation, it's design will typically prove to be just as compromised and unsexy as its predecessor - and then the cycle of "innovation" repeats. Some innovations have sufficient value to overcome their costs - many don't.