Developing for Healthcare - .NET vs J2EE?
Grok Headline matches for Developing for Healthcare - .NET vs J2EE?
What's Next for Healthcare Realty?
What's Next for Healthcare Realty?
06/24/2005 09:40 PMHealthcare Realty recently dumped its auditor and filed unaudited
results.
Healthcare IT spend on the up-and-up
Healthcare IT spend on the up-and-up
05/05/2004 06:56 AM2004 European budgets set to rise
Healthcare Desktop
Healthcare Desktop
12/02/2003 08:47 AMKick off
Healthcare Resources
Healthcare Resources
06/25/2004 05:44 AM
Healthcare Resourceshttp://www.HealthcareResour
ces.infoHealthcare Resources is a
Subject Tracer™
Information Blog developed and created by the
Virtual Private
Library™. It is designed to bring together the latest
resources and sources on an ongoing basis from the Internet on
healthcare. We always welcome suggestions of additional sites and
resources to be added to this comprehensive listing and please submit
by clicking
here. This site has been developed and
maintained by
Marcus P.
Zillman, M.S., A.M.H.A. . Additional links and resources by
Marcus are available by clicking
here.
Tech Rx for healthcare
Tech Rx for healthcare
05/05/2004 11:19 AMUSA Today May 5 2004 3:23PM GMT
Information Technology and Healthcare
Information Technology and Healthcare
08/29/2004 06:50 AMInformation Technology and Healthcare1) National Health Information Infrastructurehttp://aspe.hhs.gov/sp/nhii/2) PC World: Medical Records May Go Onlinehttp://
www.pcworld.com/news/article/0,aid,117479,00.asp3)
CNET News: Human Chips More Than Skin Deephttp://news.com.com/Human+chips+more+than+skin-deep/2009
-7337_3-5318076.html4) Medical Records Institute
Surveyhttp://ww
w.medrecinst.com/pages/latestNews.asp?id=1155)
Ariadne Magazine: Interoperabilityhttp://www.a
riadne.ac.uk/issue24/interoperability/6) Connecting
for Health Roadmaphttp://www.connectingforhea
lth.org/7) Electronic Record Development and
Implementation Programme (ERDIP)http://www.nhsi
a.nhs.uk/erdip/pages/default.aspIn July 2004, the U.S.
Department of Health and Human Services (HHS)launched its initiative
to develop a National Health Information Infrastructure. The ultimate
goal of this initiative is to create an electronic health record (EHR)
for every American so that health records can be securely shared among
health care providers. This Topic in Depth explores developments in
electronic health records and technology.
This first
website (1) is the official site for the National Health Information
Infrastructure 2004: Cornerstones for Electronic Healthcare. Some
current ideas for how to share medical records, such as secured online
postings or saving data on flash disks are discussed in this article
from PCWorld (2). This next article (3) discusses another development
in information technology, implantable electronic identification
chips. The fourth website (4) presents findings from a recent Medical
Records Institute survey of health providers on their current uses,
future hopes and perceived barriers to electronic health record
systems. One challenge for the initiative is interoperability, which
is explained generally on this website (5). The issue of
interoperability, as well as privacy and fragmentation in the health
industry are addressed in the Preliminary Roadmap for Achieving
Electronic Connectivity in Healthcare released by Connecting for
Health (6). For more on current research on technology supporting the
use of electronic records see this website from The Electronic Record
Development and Implementation Programme (ERDIP) (7).[From The NSDL
Scout Report for Math, Engineering, and Technology, Copyright Internet
Scout Project 1994-2003.
http://scout.wisc.edu/]
Child healthcare goals to be set
Child healthcare goals to be set
09/14/2004 08:49 PMThe government is set to unveil standards for the healthcare of
children and adolescents on Wednesday.
US leaders call for better use of IT in
healthcare
US leaders call for better use of IT in
healthcare
06/23/2004 11:01 AMComputer Weekly Jun 23 2004 3:16PM GMT
NHS & healthcare ICT needs much better
evaluation says think tank
NHS & healthcare ICT needs much better
evaluation says think tank
07/28/2004 02:36 AMPublicTechnology.net Jul 28 2004 7:06AM GMT
Application Engineer - Healthcare
Application Engineer - Healthcare
03/28/2005 08:18 PMMedical Software firm - United States, MD, Bethesda (2005-03-28)
The pulse of healthcare is wireless
The pulse of healthcare is wireless
02/13/2004 10:36 AMZDNet Feb 13 2004 2:22PM GMT
"Healthcare in France, Part 2"
"Healthcare in France, Part 2"
04/14/2005 04:00 PMCalifornians, the Internet, and
Healthcare
Californians, the Internet, and
Healthcare
12/15/2003 11:39 PMBeSpacific Dec 15 2003 10:09PM ET
Dot-Net vs. J2EE shootout.
Dot-Net vs. J2EE shootout.
03/12/2003 11:18 PMThe shootout was
a bit too long and a little too fluffy, but I enjoyed it. I took 20
pages of notes and I will probably write them up for you later but for
right now, I'll just give you some quotes from the J2EE team:
Mark Fleury:
The worst dog of them all is SOAP.
Sang Shin:
Security is not an industry problem, it is a Microsoft problem.
Mark Fleury:
C# to be the number one language in two years: you've got to be
kidding me.
Mark Fleury:
JBoss is a responsible, moral, and open player.
Sang Shin:
Web services is like teenage sex, everybody is talking about it but
nobody is doing it.
Sang Shin:
My grandmother called me last night to tell me that she is doing web
services.
Mark Fleury:
ADO sucks, Dot-Net caching is not there.
Greg Ackerman:
C# is great, very Java like.
J2EE 1.5 previewed
J2EE 1.5 previewed
04/26/2004 07:03 PMSAN FRANCISCO -- Ease of development will be a core focus of J2EE 1.5,
the follow-up to the much-heralded J2EE 1.4, a Sun Microsystems
official said on Monday.
J2EE Security
J2EE Security
12/22/2003 01:49 PMSimon P. Chappell writes "Security is not just for the paranoid
anymore. There is plenty of documented evidence to show that there are
people that are out to ...
Stitching up J2EE
Stitching up J2EE
12/02/2003 01:18 AMHelp us support both your platforms, or we'll write for neither. That
seems to be what ISVs have been saying to IBM and ...
Breaking up J2EE
Breaking up J2EE
06/06/2002 06:00 AMCNET Jun 5 2002 10:13PM ET
Dentata J2EE CMS
Dentata J2EE CMS
06/04/2004 07:10 PMDentata J2EE CMS Approved
DST Systems to purchase healthcare
business from CSC
DST Systems to purchase healthcare
business from CSC
04/11/2005 11:37 PMComputer Business Review Apr 12 2005 4:16AM GMT
Welsh to splash GBP88m on healthcare IT
Welsh to splash GBP88m on healthcare IT
12/12/2003 01:56 PMvnunet.com Dec 12 2003 12:53PM ET
Solution for Affordable Healthcare?
Nanotechnology
Solution for Affordable Healthcare?
Nanotechnology
05/31/2004 01:47 PMSo says healthcare and nanotechnology expert Richard H. Smith. In his
upcoming talk for the World Future Society National Capital Region
Chapter on Thursday, May 20 at 8:00pm at the Friendship Heights
Embassy Suites, Mr. Smith will discuss recent nanotechnology advances,
what they portend for the future in healthcare and trends that might
derive from current research and development which could revolutionize
how doctors think about and administer care. [PRWEB May 18, 2004]
Child healthcare goals unveiled
Child healthcare goals unveiled
09/15/2004 05:39 AMThe government has unveiled standards for the healthcare of children
and adolescents.
Wireless & mobile will revolutionise
healthcare
Wireless & mobile will revolutionise
healthcare
06/02/2004 05:25 AMinSourced Jun 2 2004 8:54AM GMT
A Canadian reporter looks at Texas
healthcare.
A Canadian reporter looks at Texas
healthcare.
12/09/2003 12:22 AM A
Canadian reporter looks at Texas healthcare. More Work Needed on 3G Healthcare
Applications
More Work Needed on 3G Healthcare
Applications
09/07/2004 03:04 AMWireless Healthcare, the Cambridge UK based ehealth consultancy, has
suggested that a special interest group is formed to develop and
exploit healthcare applications for 3G networks. [PRWEB Sep 7, 2004]
European healthcare 'online by 2008'
European healthcare 'online by 2008'
05/05/2004 05:25 AMTechnology will make everything easier. No, really
J2EE Design Patterns
J2EE Design Patterns
12/02/2003 01:27 AMGeronimo: Apache y J2EE
Geronimo: Apache y J2EE
11/18/2003 08:07 AMSun Gives Early Peek at J2EE 1.5
Sun Gives Early Peek at J2EE 1.5
05/07/2004 07:41 AMAt the Serverside Java Symposium, Sun execs say ease of development is
the major theme of the Java 2 Enterprise Edition 1.5 as Sun pushes to
attract more developers.
Sun readies J2EE 1.4, app server
Sun readies J2EE 1.4, app server
11/14/2003 05:14 PMNew version will enable the use of Web services in Java applications.
J2EE 'grossly unreliable'
J2EE 'grossly unreliable'
12/02/2003 01:18 AMAccording to a survey published by performance testing company Wily
Technology, applications that run on the J2EE ...
J2EE 1.5 will ease development, says Sun
J2EE 1.5 will ease development, says Sun
04/27/2004 10:22 AMComputer Weekly Apr 27 2004 2:07PM GMT
Notes from the Dot-Net vs J2EE shootout
Notes from the Dot-Net vs J2EE shootout
03/15/2003 01:29 PM
Here are my notes from the
TechEngage J2EE vs. Dot-Net
shootout. I tried to be objective while I took these notes
Wednesday and while I typed them in today. I may have made some
mistakes and I may have let some of my open-source/Java bias show
through. You be the judge and leave a comment if you see something
that does not look right.
Opening Statements
MS [Dot-Net]: Dot-Net is a vision of XML web services enabled
by the Dot-Net Framework that happens on the Windows platform. The
evolution of computing goes like this: Mainframe OLTP, Client-server
OLTP, N-Tier TP monitors (MTS 1997, first OTM), web applications
(J2EE, Cold Fusion, Windows DNA), and finally Web Services on the
Dot-Net
platform. When people learn about Dot-Net they wonder where is the app
server? The app server is the Dot-Net Framework, Windows 2003 Server
(with load balancing and clustering), plus developer tools (like
Borland Sidewinder and Together Control Center). Windows is the app
server.
Sam Shim, Sun [J2EE]: Let's talk about Microsoft's contribution
to the evolution of computing. Microsoft's contribution is Fear,
Uncertainty, and Doubt. F. U. D. FUD. Let's talk about some of the FUD
that Microsoft is spreading. FUD #1 is that J2EE is expensive. Don't
listen to them. J2EE is free. The analysts at Gartner say that the
hidden cost of Dot-Net is 40%-60% (sorry, couldn't follow this). FUD
#2 is that the Dot-Net server is a product. Dot-Net server is not a
product yet. Once it is released, how many bugs will it have? How many
security problems?
Microsoft says that portability is not important. This is very
important. Microsoft wants to lock you in. Single vendor lock-in.
Lock-in is not a horrible problem when you are talking about
applications like office suites, but for infrastructure, single vendor
lock-in is very dangerous and expensive. Microsoft touts
interoperability, but only as a bait to draw you into single vendor
lock-in. They also say that J2EE is no good for web services:
wrong.
FUD #4 is that Dot-Net performs better. This is only true in Microsoft
funded benchmarks that are tuned in favor of Microsoft. And look at
this paper about the Dot-Net Petshop, it shows that the Petshop is
pure spaghetti code. Look at this method call from the Dot-Net Petshop
(everybody laughs), this method has 36 arguments. Spaghetti!
FUD #5 is that Microsoft believes in standards and interoperability,
but Dot-Net is not a standard. Only about 5% of Dot-Net has been
submitted as a standard. None of the important stuff you need to
develop app is standard: Winforms, ADO, etc. Even when Microsoft
supports a standard, they always add that "Microsoft extra" that
breaks compatility with other implementations of the standard. Here is
a list of examples: Kerberos, etc. etc.
Greg Ackerman, IBM [J2EE]: I like Letterman and his top ten
list so here is my top ten list for J2EE:
1. Openness, avoid single user lock-in
2. Web services, J2EE fully supports
3. Superior platform support, TCO, scalability, Linux
J2EE websphere reference customers (eBay)
4. Products designed to fit your needs
5. J2EE connects to what you already have
6. World class leading development tools
7. Best dev support programs
8. Partner support
9. IBM does not compete with ISVs
10. J2EE is a complete platform
Mark Fleury, JBoss [J2EE]: We are free and we don't suck. JBoss
supports all of the J2EE standards and helps Sun to write those
standards. JBoss has a services oriented architecture, a microkernel,
and a sophisticated net-boot capability. JBoss brings you unified
classloading, no more ClassNotFoundExceptions. If JBoss can't find
your class, then your class really can't be found.
I'm very impressed with Dot-Net. The method and class atributes
support Aspect Oriented Programming. JBoss does some of the same
things, adding capabilities to your classes by using attributes,
dynamic proxies, and interceptors. All of this stuff can work outside
of the JBoss platform too.
JBoss is the defacto standard. 150,000 downloads per month. App server
market share is 48% JBoss, 28% BEA, and then the others. JBoss offers
extreme stability. JBoss group is 30 people and growing fast. Some of
our references customers: EA Games SIMs online is all JBoss, Playboy
(I'm very proud of this), BASF, MITRE, McDonalds, etc. etc.
Richard Weeks, NetEdge [Dot-Net]: Customers use different
programming languages and Dot-Net supports 40-50 different languages.
Dot-Net is all about multi-language support. Those Java guys want you
to rewrite all of your code, don't do it. Don't rewrite your code, get
interoperability with web services. Dot-Net does not leave anything
behind, you can still use your old code.
Richard Lee, Borland [Dot-Net]: Open source is good, but
sometimes there is too much choice. Microsoft has learned from Java
and open source and has taken the best aspects of them and has built
them into Dot-Net. Borland knows how good Dot-Net is because Dot-Net
made it possible for us to build products very quickly. Our Dot-Net
products come out of our Rapid Application Development (RAD) group
because they are so rapid. Dot-Net makes things so easy, Microsoft is
not the dark side, they are our friends.
Q1: What sets your platform apart?
Sam Shim, Sun [J2EE]: Our vision has always been "the network
is the computer". We have been active in open source software with
Open Office, Netbeans, and Apache. J2ME is everywhere. Java is
everywhere from cars, computers, and phones to rings, smart cards,
etc. Java makes true end-to-end computing possible. Our innovation
continues with the N1 project which promises complete virtualization
of resources, ORION to solve maintenance and upgrade problems, and
Madhatter to bring Linux and open source to the desktop.
Greg Ackerman, IBM [J2EE]: The things that set J2EE apart are
openness, standards, and choice. The things that set Websphere apart
are scalability/TCO, web services, comprehensiveness, dev support,
business partner support, support for open source, and most
importantly community.
Mark Fleury, JBoss [J2EE]: Everybody brags about open source.
At least Microsoft is honest about it. Microsoft does not like open
source and they say so. Sun is very hypocritical about open source.
Both Sun and Microsoft have accused JBoss of taking away the license
revenue money that drives R&D. Guilty as charged! The truth is
this: the big guys can't compete at the container level and that is
why you hear about portal this schmortal that. SOURCE CODE is what
sets us apart. The advantages of J2EE are that it is mature, free, and
ubiquitous. Dot-Net on the other hand is expensive and buggy.
Remember, JBoss wants to commoditize the app server and Microsoft
wants to commoditize the developer.
Richard Weeks, NetEdge [Dot-Net]: Dot-Net supports both managed
and unmanaged code. Dot-Net is flexible. Sometimes web service
implementations don't really follow the standard and Dot-Net helps you
to get around this by allowing you to tweak how it's implemented.
Plus, you can call COM objects. I know BEA has some Java2COM tool, but
Dot-Net's COM support is better. The SDK and the class libraries are
free and there are lots of free tools, SharpDevelop for example. You
don't need a big expensive app server because Dot-Net gives you
choices. You can use only the small parts that you need. Use your old
code, don't rewrite it.
Microsoft [Dot-Net]: Windows is the app server and Windows is
not expensive. Windows Advanced Server is only $5000. Microsoft and
IBM are driving the web services standards, not Sun. Windows is a
standards-based integration platform and platform integration gives
Dot-Net much better performance than Java. The Dot-Net developer
experience is fantastic. We've got multi-language support, the best
web application development environment ever in ASP.NET, ADO.NET, and
a strong versioning story.
REBUTTAL: Sam Shim, Sun [J2EE]: Sun was not involved in the Web
services standards because Bill Gates was playing politics. Bill made
sure that Sun did not get invited. Microsoft wants royalty based
licensing included in standards. Microsoft wants to charge for every
packet of information and monopolize the internet.
Q2: show and tell how you support web services?
Greg Ackerman, IBM [J2EE]: Websphere supports "on demand"
computing which allows you to compose your applications as reusable
services. Let's look at a demo of creating a web services using
Websphere Studio (shows an AVI animation of Websphere Studio). Let's
build a stock quote web service. You can build in Websphere Studio and
then use a Dot-Net client to access the web service.
Mark Fleury, JBoss [J2EE]: This is when I go Phbbbbtbphphppph
(makes a loud farting sound with his lips). Web services is totally
vendor driven and all hype, but JBoss supports it fully. We integrate
Axis. I don't have much else to say. Let me ask you some questions.
How many people do Java and have a Java app in production? (20 or 30
people raise their hands) How many people do Dot-Net and have a
Dot-Net app in production? (20 or 30 people raise hands) How
many people have a app that uses both Dot-Net and Java at the same
time? (nobody raises their hands) See? This
interoperability stuff is just vendor noise. You need to avoid
serialization and avoid RMI and remember SOAP is the biggest dog of
them all. B2B will not work. I worked with SAP once and found that
these guys can't even create a common object model across one company.
B2B vendors are never going to be able to create object models that
cross industries.
Richard Lee, Borland [Dot-Net]: Let's use Control Center to
create a web services. You just set the project type to C# and you are
off. You can add a class using UML notation and the code is
generated automatically. If you change the code, the diagram changes.
If you change the diagram, the code changes. You can use a wizard to
make any object into a web service.
Kenny Jones, MS [Dot-Net]: Analysts say that Microsoft has the
best support for Web services. We support web services through our
entire product line from Office, MS SQL, and MSMQ, to BizTalk, Excel,
etc. Look at you you do web services in Dot-Net Studio. You just add
an attribute to your object and it becomes a web services. Let's look
at how you use a web service in Dot-Net studio. You just add a "web
reference" and then you have a proxy object that you can use to call a
web service.
Sam Shin, Sun [J2EE]: Web services is like teenage sex:
everybody talks about it but nobody is doing it. There are three
phases of web services adoption: 1) simple (now), 2) Enterprise
Application Integration (beginning) and 3) Business web services
(2004). #3 is the most important and Sun will support it through
J2EE, UBL, ebXML, and the Liberty Alliance. It is very easy to
create web services by exposing EJBs, here is how you do it in
Netbeans (shows a wizard).
REBUTTAL: Greg Ackerman, IBM [J2EE]: the analysts are mixed on
who is the leader in web services. Some say Microsoft and some say
IBM. IBM does web services for many more customers than Microsoft
does.
REBUTTAL: Mark Fleury, JBoss [J2EE]: IBM is much better
on standards than MS.
REBUTTAL: Microsoft [Dot-Net]: J2EE support for web
services is irrelevant. App server vendors and open source software is
pushing web services much harder than Sun.
Q3: how do you support building apps for hundreds of thousands of
users?
Mark Fleury, JBoss [J2EE]: To support big applications you need
grid computing, but grids are too expansive when you must pay for
software licenses. You also need caching and JBoss has great support
for caching. Don't use serialization. Use caching. Also, you need to
integrate the stack within one virtual machine. Dow Jones uses
JBoss to support 10,000 clients.
Richard Lee, Borland [Dot-Net]: How do you build N-Tier
apps? You need to use modeling and code generation. You need to
use Model Driven Architecture (MDA). Here is a demo of MDA in Together
Control Center.
Kenny Jones, MS [Dot-Net]: We support this by the scalability
of the Windows platform with load balancing, clustering, and caching
built into ASP.Net that allows you to easily cache pages and portions
of pages. Also with distributed session state and the ADO disconnected
data set. You need technology, but you also need the knowledge and you
can get teh knowledge from the MSDN program and Microsoft Patterns and
Practices. Look at all of these customers who use Microsoft to support
giant customer bases Merril Lynch, London stock Exchange, etc.). To
summarize, the platform is scalable and the knowledge is
available.
Sam Shin, Sun [J2EE]: Java has the scalability. Sun has 64-bit
support in the Java VM. When will Microsoft have that? One VM can
scale up to 100 processors, X RAM, and X threads. Tremendous
scalability of just one Java VM. J2EE is all about scalability and
reliability. J2EE vendors compete on scalability and reliability to
benefit you. Dot-Net is constrained by Windows, Dot-Net is not
proven, Dot-Net is single-vendor lock-in. Why should you be the
Dot-Net guinea pig?
Greg Ackerman, IBM [J2EE]: IBM has a great deal of experience
in distributed computing (CORBA, Encina, etc.). J2EE is designed
for this stuff. Remember the case studies. Java and VMs
are scalable.
REBUTTAL: Microsoft [Dot-Net]: The analysts say that
portability across J2EE app servers is going to become more and more
difficult. Java app servers do contain vendor lock-in features.
Java allows you to scale to bigger more expensive hardware. With
Dot-Net you won't need to do that, you can stick with the hardware you
already have.
REBUTTAL: Mark Fleury, JBoss [J2EE]: The EJB spec does not give
you what you need to scale, you need the cache. The spec is fighting
the implementation here. J2EE is not moving fast enough. We need
Aspect Oriented Programming, from Xerox, where all good things
emanate. Dot-Net does not have what it takes here either: ADO sucks
and Dot-Net caching is not there.
Q4: explain your platform's security system?
Richard Weeks, NetEdge [Dot-Net]: Dot-Net provides code-access
security. This allows you to say where what a piece of code is allowed
to do. For example, if you have a consultant that you don't trust, you
can lock his code down so that it does not threaten you. Encryption is
built in. ASP.Net has forms based security. No more buffer
overflows because of the Dot-Net runtime. Microsoft is putting a big
emphasis on integrated securty.
Kenny Jones, MS [Dot-Net]: Windows security vulnerability is a
myth. Security is an industry wide problem, not Microsoft
problem. Windows has fewer CERT security advisories than Sun or
Redhat. Microsoft has a serious "trustworthy computing" initiative
going on. Microsoft won the Open Hack 4.0 contest. Let me
show you how code that is downloaded from the internet is treated
differently than code that lives on your hard-drive. See: this
downloaded code is not allowed to run.
Sam Shim, Sun [J2EE]: Security IS a Microsoft problem. Security
must be built-in from the beginning. You cannot just bolt it on as an
afterthought. Look at the passport fiasco. Microsoft's Passport
identity management system was centralized, single-point-of-failure,
controlled by Microsoft, and single point-of-attack. No wonder
everybody hated it and it failed. The Liberty Alliance on the
other hand is a federated system, much better. There are 52,000
viruses for Windows and the analysts say it is time to switch away
from Windows based web servers. Viruses are very expensive. The ILOVEU
virus costs us $1 billion dollars. NIMBDA costs $2.6 billion.
Recently, Microsoft's Craig Mundie said "we've been thinking about
security for almost three years now." Microsoft has been in
business for 27 years. It took them 24 years to realized that security
is important.
Greg Ackerman, IBM [J2EE]: Good for Microsoft! They finally
realize that security is important, but security needs to be built-in
from the start. Look at Dot-Net security: sandboxing,
code-access security, not exactly novel concepts. Dot-Net security is
just a copy of Java security. IBM is cooperating with Microsoft
on Web services security.
Mark Fleury, JBoss [J2EE]: UNIX has had better security than
Windows for many years. Security cannot be bolted on. Java
security is excellent. JBoss did JAAS security years ago, before all
of the other app server vendors. JBoss can also use interceptors
to add additional security.
REBUTTAL: Sam Shin, Sun [J2EE]: Microsoft FUD #9 is that
Dot-Net is secure. Dot-Net depends on COM+ which is not managed code
and is therefore unsecure. C# permits unsafe and unsecure code.
Passport has already been hacked.
Closing Statements
MS [Dot-Net]: Let's take a look at what it takes to build a
mobile web app, one with an adaptive UI that looks different depending
on which device you use to access it. Let me cut-and-paste some code
here and let's try to run it. Oh no, the Dot-Net server is not
responding (his computer appears to lock-up). Analysts say that
C# is going to be the number #1 language in two years.
Mark Fleury, JBoss [J2EE]: C# to be the #1 language in two
years? You're freaking kidding me. Dot-Net has some good features, but
multi-language support is just cute, no more. Without portability off
of the Windows platform, Dot-Net will go nowhere.
Sam Shim, Sun [J2EE]: Java is the most powerful development
technology ever. There are 3 million Java developers, 65 million
Java enabled phones, 8 million lines of Java source contributed to
open source, etc. etc. The development resources are all free: open
source software is almost all Java, tutorials, knowledge base,
community!
Greg Ackerman, IBM [J2EE]: C# is great, very Java like.
Make the rational choice (no pun intended). VB.Net has a big learning
curve, even for veteran VB programmers. C# does too, so why
don't you just go directly to Java. We will welcome you into the
community. Come on out the the Websphere Users Group and the Java
Users Group meetings in the Park.
Mark Fleury, JBoss [J2EE]: JBoss is a responsible, moral,
and open player. Let JBoss be the standard, not Dot-Net or J2EE.
Richard Weeks, NetEdge [Dot-Net]: We keep hearing about free
this and free that. Open source is not free. Support costs
money. Multi-language is not just a cute feature. Each language
has it's own unique advantages and disadvantages. C# and Java are
different. C# is better.
Does J2EE live up to expectations?
Does J2EE live up to expectations?
09/06/2002 10:43 PMCNET Sep 6 2002 10:06PM ET
Dynamically Typed: J2EE Guy Still
Doesn't Get PHP
Dynamically Typed: J2EE Guy Still
Doesn't Get PHP
07/01/2004 08:47 AMDynamically
Typed has a new entry concerning the past post about
Friendster going PHP, and how
the J2EE
guy still doesn't get it.
Does J2EE live up to hype?
Does J2EE live up to hype?
09/09/2002 10:39 PMCNET Sep 9 2002 10:11PM ET
Cyanea buy should help IBM compete in
J2EE and APS
Cyanea buy should help IBM compete in
J2EE and APS
08/10/2004 09:25 PMComputer Weekly Aug 11 2004 1:07AM GMT
The LAMP alternative to J2EE or .Net
The LAMP alternative to J2EE or .Net
04/06/2005 12:14 PMLinux, Apache, MySQL and either Perl, PHP or Python provide low-cost,
open-source options.
Grok Description matches for Developing for Healthcare - .NET vs J2EE?
GrokA matches for Developing for Healthcare - .NET vs J2EE?
Developing for Healthcare - .NET vs J2EE?
