|
|
|
|
|
|
by Azeralthefallen
2725 days ago
|
|
|
Honestly we told them our requirements well over a year ago. Which wasn't an issue apparently, even when we did a pilot in their internal labs which they were running Ubuntu. It only came up after we started the rollout, when someone from their side who was asked to write documentation about how our app would work into their workflow, realized our app didn't work at all on his station. Which lead to oh no their requirements are horribly wrong. To me it was a communication breakdown on both sides, but i doubt i can get them to change. I am going to give getting electron built in Virtual Box and see if i have any luck with it. |
|
|
For many contractors, Windows 2000 as a requirement would be a red flag--decline the contract and run the other way, because that's just where it starts. Chances are you're looking at the tip of the iceberg.
Since you're already committed, though, your focus should probably be on pushing them to upgrade whatever they can. It's a lot easier to run old software on new platforms than the other way around. Whatever ancient programs they want to run, they can do it on newer versions of Windows--there's guaranteed to be a way, and it'll be a lot easier than getting a modern application running on Windows 2000. Lots of people want to run old programs on new computers. Nobody wants to run new programs on old computers.
Edit: To clarify, there are great programs like DOSBox that will let you run old programs you wouldn't normally be able to run on new versions of Windows. DOSBox targets a specific niche, but it works well, and the concept is quite prevalent: people want a way to run their old programs, even if it's just for nostalgia. I would bet my life on it being significantly easier to run their specialized software on a newer version of Windows, even if it's in a VM. (Or, heck, what about WINE, since they have Ubuntu?)