This post is now available on my new blog The IT Report:
http://theitreport.com/entries/project-management/net-vs-j2ee—butter-or-guns
sheehantu
linux, technology, lifehacks
Recent Comments
 | Grayda on Free Software Licenses in a… |
 | James on .NET vs. J2EE – Butter o… |
 | Valentine Aaqil Mahm… on Glipper – A Real Clipboa… |
 | Hi fi on Frostwire – Best P2P Cli… |
 | coder on .NET vs. J2EE – Butter o… |
I will choose PHP
1. Build Your applications fast (May be 4 or 5 times faster that J2EE and 3 Times faster than .Net)
3. Zillion of books and articles
4. Zillion of Framework and tools
5. Zillion of open source project cover every thing
6. It run every where and with every DBMS (Unix, Linux, Mac, Windows, MySQL, SQLServer, Oracle, DB2,……)
7. It is always Easy to hire PHP Developer than Java (i donot know about .Net)
The Only thing i miss in PHP is Some thing to Build work flows (Like JBoss JPBM) it is fun any way to build from scratch
You’re right about everything you said with PHP. There is only 1 thing that I’ve seen – PHP has not been adopted by the enterprise because it doesn’t have industry backing, therefore is not supported or included in most enterprise strategies.
For all other things not-enterprise – go php!
I’m not sure how good PHP is for an enterprise application. That being said, I’m going to JavaOne in May and there is a course there on mixing PHP and Java. I might check it out.
There are a bunch of build-management and deploying tools for Java now. Have you checked out Maven and Archiva? Very nice. It’s what we use at work for the app we work on. Sure, you have to configure it. But I think that’s an acceptable price to pay for diversity and options. You only have to do the hard work once. Especially with the newer tools like Maven, once you have your stuff in place, you don’t have to all that much to modify it later.
I haven’t worked with .NET, so I can’t make any comments. But the reason Microsoft .NET would work so well is that they can make a LOT of assumptions about the build environment. It’s simple – it’s always windows. The convenience of a monoculture and a monopoly
.
Internet runs on LAMP stack but high available enterprise application are ready to accept a technology which is not standardized, supported and proven. Even if architects suggest PHP as development language you hardly find such professionals in service companies. Any thing which comes for free has always been considered secondary than licensed software when comes with support though has less features.
JEE vs .NET I was associated with .NET development for quite a long time and I’m working on JEE. The paradigm has shifted from one vendor platform to mixed platforms with SOA in place. Java always going to win the game because of its open strategy. .NET has really amazing development platform its developers paradise. Visual Studio is the one stop workshop for .NET developer. But JEE suffers and give choice with many vendors platforms and standards.
This is what I don’t like about J2EE. The market is fragmented. You have Java standard and Java Enterprise. Then you have so many frameworks and most of them are hard to get working smoothly. Then the IDE whether it is Netbeans or Eclipse is slow. Then the programmers want to use Weblogic or Webmethods or Websphere. Then they want to use Oracle and pretty soon the cost is 100 times more expensive then just buying Visual Studio which has a really good IDE, debugger and a 4GB version of SQL server which is an excellent database. We always have configuration issues because we are using so many different products. In the end I can produce pages faster and with little cost compared to J2EE. In reality I don’t understand why anyone would do the J2EE except where they get 10’s of millions transactions per day.
I choose JEE cause for building enterprise application, especially with different business logic’s frameworks according to the scenario multi platform support all are available under the single shelter, if i choose sql & .net then i have to follow the microsoft way of programming, cost concerns all mysql postgre and lots of bsd and low price database is also available, glassfish is one of the best j2ee server like bea systems products so we make our choice unless focusing on the same ting again and again, most probably the security concern ms products is a weak entity
.net sucks. If you look at c# in terms of OOP, is sucks, if you look at asp.net, in terms of computer science, it sucks.
I dont understand why and how people use it. it s really terrible. Look at J2EE, Spring, Struts, Hibernate etc. Ruby On rails even Php frameworks makes more sense than the way c# and asp.net works.
.net is really terrible.
Mohammad Elkersh:
1. Build Your applications fast (May be 4 or 5 times faster that J2EE and 3 Times faster than .Net)
Blissfully ignoring maintenance, extending, scaling etc. P.S. I used to be a PHP developer and I can write .NET applications as fast as I used to be able to write PHP apps with fewer years experience in .NET. I can go faster if I want to adopt the simplistic approach most PHP developers and particularly small teams in organisations take when writing their apps
3. Zillion of books and articles
Mostly written by hacks
4. Zillion of Framework and tools
Inferior and immature, Zend and Symfony are coming along nicely, and Aptana Studio and Netbeans are okay but are still considerably inferior, and debugging, continuous integration, monitoring are further below par
5. Zillion of open source project cover every thing
Again, mostly written by hacks, even most commercial PHP applications are poorly written
6. It run every where and with every DBMS (Unix, Linux, Mac, Windows, MySQL, SQLServer, Oracle, DB2,……)
One good point however it is barely taken advantage of: the vast majority of PHP deployments are on *nix using MySQL/PostgreSQL though.
7. It is always Easy to hire PHP Developer than Java (i donot know about .Net)
It’s harder to find decent PHP developers as decent ones usually learn .NET and Java to avoid working with hacks. It’s easy to find PHP developers though as it’s easy to learn and management in projects where PHP is chosen is poor enough to hire these hacks.
Patrick: yes, far too much segregation, even amongst J2EE alone
coder: please elaborate