In the current environment I am in, the choices I have are something like this:
[this is in order of priority, primary corporate database is DB2/MVS]
Websites:
VB.Net/C#: in-house development or purchase products
Java/J2EE: purchase products
Backend development:
Mainframe:
Cobol/CICS/JCL
Windows:
C#/VB.Net
Purchased products written in whatever
VB6
Unix:
ksh scripts
perl
C (less than 2%)
Almost 100% of these things are distinct - as in NO ENTERPRISE SERVICES/NO
DISTRIBUTED TRANSACTIONS. This is how it has been done
and because the people in high places want it to stay the same because so much
intellectual property is in Cobol/DB2/MVS this is
likely to not change for some time.
When I saw a *chance* to *possibly* use Linux [on IBM z-series hardware] for a
project - I thought that I could push to do that. At
least I fallback on kornshell scripts if Mono wasn't an option. I thought that
using Mono on zLinux would be an excellent
opportunity to be able to keep existing skillsets, be able to scale CPU
vertically and be able to be relatively flexible on
operating system. The ultimate direction - Cobol/DB2/MVS because that is
comfortable. Let's just say that I won't be doing any
Cobol in the any foreseeable future in my life.
Talk of the "right" way to do something in my corporate experience almost never lines up
with "how" it is done in reality. What
Mono does is open up doors for flexibility for many aspects of programming that
were not there before. It isn't about 'cool' or
'linux' or whatever 1-3 word snip someone comes up with. Technology or
direction is rarely ever summed up like that. If one person
wants to close their mind to this aspect of opportunity, fine - likely their
mind is open to other aspects of opportunity.
No skin off my back.
Happy POETS Day!
- dave
Frans Bouma wrote:
Frans Bouma wrote:
Mono is nice, but ... I can't understand how people want to
develop on/for mono other than 'it's cool'.
J. Merrill wrote:
So that the work we do can be deployed on either Linux or Windows?
Frans Bouma wrote:
If that's a requirement, why not use Java? Seriously:
first look at the job, then pick the right tool which fits the job.
It's not as if Java lacks any tooling or functionality or anything.
Perhaps because C#/CLI is the right tool. You are incorrectly
assuming that Java is the "right tool" for systems that must
be deployed on Windows and Linux (or even Oses other than Windows?).
Quick example:
A) App already develop in C# running on Windows. Need to
extend to Linux.
Would you recommend first rewriting in Java?
No, though this situation would IMHO be rare.
<snipped />
FB
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
