Leroy,
I choose Windows (XP in this case) because that's what I have on
this laptop. I have to develop wherever I am to meet the deadlines on
this project, so my laptop defines my options. Also, I'm working with
Nucleus' GUI via Accuterm and Accuterm requires Windows. Without a
second system, that means everything has to be on Windows.
I've been working both sides of the street for so long that I don't
see the pitfalls anymore. Other than my deep, deep, deep loathing for
deploying printers under Linux (CUPS is one of the biggest reasons I
*love* SMIT in AIX), I find deployment in both places easy.
What I find is more critical than deployment is debugging. Once they
get to Windows, they need to think about how they will support their
customers going forward. They need some in-house expertise that can
quickly suss out which problems are o/s, which are database, and which
are application. I started out in tech support and I know how quickly a
design or deployment choice can turn into a major shift in tech support
demand.
I'd suggest they get someone who knows Linux and Windows, so they
can help bring the existing Linux people up to speed by 'speaking both
languages.' that preserves the maximum value each of their current
people can contribute in development and support.
- Chuck
Leroy Dreyfuss wrote:
What about porting an app from Linux, which you have been using for a long
time, to Windows, which you haven't used yet? That is the situation I am
asking about. Did you encounter any issues doing that? Why did you choose
Windows?
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
