I work for a big pharma company, as a sysadmin. I don't know much about the science though.

Any company finding a cure for HIV or cancer or the common cold would have its stock skyrocket, turning the board instant billionaires.
Somehow I have trouble believing that they would suppress a cure, just for the purpose of being evil at their own expense.

And it isn't a cure, in case you missed that. It is a vaccine. Like the vaccine against smallpox. Once you get smallpox or ebola, your chances still suck.

Seeing them daily would be a great help I imagine.
I practice traditional Japanese jujutsu, and my currciculum has the Japanese names printed next to them.
The kanji which I have an external link to (like names of techniques etc) stick much better in my mind than the ones I only see in the kanji list.
The least I can say is that Japanese is an interesting language.

And sometimes not without a sense of humor. When I learned the kanji for 'target' I thought to myself 'hey, that sounds familiar. And kin means 'gold' but that would mean... :)
You probably know this so I don't need to explain the joke, but for those who don't speak the language: kinteki is the (a) Japanese word for testicles, which can be literally translated as 'golden target' or 'bulls eye'

2 years ago I started learning Japanese. Last year I started learning kanji.
So I force myself to learn something new every single day, or I'll never know even the grade school kanji list.
Learning 3 to 4 new kanji every day, and repeating them lots of times is the only way to learn the grade school kanji within 1 year.
Even then I'll probably need another year of repeating things every day to really 'know' them.

You forgot raping their women and enslaving their children.
Then the pillaging and the burning.
And at the end, you sow the ground with salt so that nothing will ever grow there again in our lifetimes.

That'll teach them.

Only if he was legally entitled to release that code.
Because if he released it and it wasn't his to do so, the GPL license itself is null and void for that project, and standard copyright would apply to that project.

If it was not his right to release that code, not only should he STFU, but he may well bring legal problems on himself, and burn his career in the process.

Windows XP is used for visualization of graphics, opening and closing valves etc.
The actual control logic as well as all safety monitoring and all the actual dangerous things are handled by dedicated controllers.
Windows XP is at no point in charge of anything important. Keeping that in mind, it does not matter if you're running MacOS, linux or Windows for the client part.
No need to get emotional about it.

The DCS system that I use, and those I know of, give you specific version of Windows, service packs, and hotfixes that you must install. Deviate from that list and if you need support or are trying to get something done because they screwed up or had a bad bug, they'll just tell you that it's not their problem because you did not run the recommended configuration. I have seen a vendor argue over the 4th digit of a bios revision number because they could not find a cause for the bug we reported. And the only way we got away with that in the end was that they had documented a valid upgrade path, coming from an earlier software version, in which case that version was allowed.

My servers run
Windows 2003 because they say I have to
Standard edition because they say I have to
Service pack 2 because they say I have to
And a handful of hotfixes that come with the software installation disks. Because they say I have to.

And I will keep running that particular set up until we upgrade to the next version, when we will switch to windows 2008, standard edition, SP whatever, which some hotfixes.

That is why our network is disconnected from the outside world, all equipment is in locked cabinets, and all computers are in a locked serverroom with kwm going out to the field terminals.

Many banks in Belgium (and the Netherlands) at least don't have this set-up anymore. Some do, most don't, in my experience.
It is not customer friendly to be speaking from behind a fortress wall, and as you say, if a robber starts shooting customers, the bank is off worse than before.

+1.

I'm sure that helping slaves escape was wrong at one time or another. That didn't make morally wrong though.
And lynching a black man who could have been near the scene of a crime was fine too at one point. That didn't make it right either.

Perhaps if you read the post in its entirety, you wouldn't have made yourself look foolish twice.

that 120,000kg to LEO cost $(2011)1.11billion ($(1969)185billion).

Not really. The process control is done on real-time controllers, but visualization is usually on windows machines. Data historians, configuration databases, OPC servers, etc are often Windows servers. Add to that that hotfixes and service packs have to be vendor approved before putting them on the live system. This means that those systems often run whatever was approved at the time of installation, which can be years out of date.

Many SCADA and DCS systems are also horribly insecure, have default or hard coded administrative passwords, etc. What doesn't help is that they are often managed by people who are good at the actual process stuff, but not necessarily at security or system administration.

And then erect a great bonfire with everything they've bought; Perhaps even driving a wooden stake through a boxed copy of whatever SCO was still selling, after sprinkling it with holy water first. And at the end, the ashes could be scattered in the wind or buried underneath a crossroads...

IBM already made an example of them. This would be a nice way to end the saga.

I've been a LabVIEW programmer for close to 10 years. I have also been a C and C++ programmer for quite a long time now. I did large projects using both, sometimes using both in the same project. I can call myself a qualified programmer using both languages.

It is perfectly possible to create very large applications, using multi threading and proper design patterns. However, just like you had to spend years learning to write powerful and correct C++, you need quite some time to learn to program LabVIEW correctly.

Once you can do that, writing test and measurement applications can be as efficient or even better than with text based languages. I have the confidence to say that I wrote large data acquisition systems that performed well with very large datasets and high acquisition speeds.

But you have to understand data flow programming, and that is not something you acquire easily, just like you probably sucked at your first text based language projects.

Don't blame the tools for your failure to use them properly.

Then again, mangled names have their place to resolve overloaded method names.

I've replied in a different place in this thread as well, but since you ask...

Initially, there was an adjustment period of a couple of weeks where the consistency was different (more watery). This lasted a couple of weeks, and I assume it has to do with the body readjusting for the lack of actual sperm cells. After a month or so (no more than 2 months definitely) everything was back to normal. There were no changes whatsoever to anything except fertility.

A friend of mine had the same treatment done (different hospital) and told me it was just like I said.

The treatment itself is also nothing to be afraid of. Sure the general scrotum area is a bit sensitive the first couple of days, but a week after the surgery everything was OK. The surgery itself lasted about 20 minutes and was completely painless, involving nothing more than local anesthetic.