Running a Research Lab on Free Software?
"[Hardware Manufacturers] seem to get very upset when somebody asks them what the register-level interface to their card is. Who could blame them? Their Windows DLL is the perfect solution under [most] circumstances.
I'm not the only one around here getting frustrated, but all before me have been defeated. It seems I am to be as well, for today I have started to learn Visual Basic.
Has anyone had any *positive* experiences trying to move a lab from proprietary to free software? Surely the government-funded researchers of the world have a responsibility to ensure that their work is free, as in freedom. However, I have found out the hard way that it's usually just not worth the effort, following such ideals. You just get frustrated by apathetic colleagues, useless product support, and the conventional wisdom that it's OK to ignore your ideals, so long as you get the experiment working. Additionally, my ordeals convince my peers that free software isn't worth the trouble."
To whoever modded me 'troll' - read the story - you'll notice the first sentence is the original author's exact words. I was just pointing out that it didn't seem to make any sense to me.
imagine a beowulf cluster of clusterfucks of beowulf clusters of free research labs!
Repeal the DMCA!
How do you check for a buffer overflow on a quantum computer?
ASP.NET is nearly finished, and there's already an alpha (?) ASP.NET server available for Linux here. Code new apps in as web-based services or in C#/Windows .NET Forms and port to GTK# or Qt# when ready.
That's the way we're doing it.
"It's not your information. It's information about you" - John Ford, Vice President, Equifax