• 0

J2EE vs .Net


Question

I'm learning about these two development environments and I was wondering what your thoughts are on the differences between the two, specifically from a standpoint of integration to existing environments and interoperability? For example, I thought .Net was proprietary to M$oft and can only run in their environments, whereas J2EE is proprietary but can be run on multiple platforms. What are some other comparisons/contrasts between the two? What do you favour?

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/
Share on other sites

12 answers to this question

Recommended Posts

  • 0

I've yet to meet anyone with depth in both technologies, so I sincerely doubt you'll be getting, uuummm, unbiased answers. I'm sure they both have plusses and minuses, but they both get the job done. Really, your questions, especially when you include the $ in MS, are probably going to invoke a mudslinging contest.

Frankly, I like working with MS tools and languages. I think MS has the best tools around, and I'm quite fond of C#. I don't work enough in Java to speak to it. I do know that I missed a lot of C# features when I had to use Java for a couple of courses. But, that was years ago and a lot has changed. The few people I do know that have worked a bit in J2EE are happy to be in .NET.

Technically, .NET can run on multiple platforms, too. Mobile, web, *nix(via Mono), and Windows. I've yet to be in a company that had such a heterogeneous environment that they needed both Java and .NET. At best, I've been in places that have both AS/400 and Microsoft servers, and we can communicate with the AS400 stuff just fine. I think the majority of interoperability between Java and .NET is going to come from web services or generic protocols, and not at a link level.

I've been using .NET since its inception and I think its growth is fantastic. It's a great platform to work on, and the tools are excellent. Again, I cannot speak to Java. I think C# is advancing at a more rapid pace than Java, and personally, think it is the better of the two in terms of consistency and expressiveness(from what I recall having to deal with in school). As anything in technology, it all changes, so take this stance with a grain of salt. By no means is my opinion an assault on Java. It is a great tool by all accounts, and has a great developer base. I learn a lot from that camp. Of the two, I think Java has the most mature developer base and probably the most depth in the engineering discipline. I think .NET is catching up, tho.

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589699000
Share on other sites

  • 0

^^

excellent answer....

  Quote
thought .Net was proprietary to M$oft and can only run in their environments, whereas J2EE is proprietary but can be run on multiple platforms.

both are open standards, thus why you have the mono project (no one that I know of uses mono in corprate world).

So MS and Sun publish the specs. to be a certified J2EE vendor such as BEA, you need to meet specs specified by Sun.

lots of corps like runnin unix... so J2EE is I would say preferred. Though I am bias towards J2EE as that is the area I work in.

I think I agree with this statement

"I think Java has the most mature developer base and probably the most depth in the engineering discipline".

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589699468
Share on other sites

  • 0
  _kane81 said:
both are open standards, thus why you have the mono project (no one that I know of uses mono in corprate world).

So MS and Sun publish the specs. to be a certified J2EE vendor such as BEA, you need to meet specs specified by Sun.

lots of corps like runnin unix... so J2EE is I would say preferred. Though I am bias towards J2EE as that is the area I work in.

I think I agree with this statement

"I think Java has the most mature developer base and probably the most depth in the engineering discipline".

Wow these are excellent points that I never even considered. It makes sense that .Net typically roll out things (such as whatever it contributed to Vista) which was arguably inappropriate for the needs of the market because of its serious flaws, and I've not seen this sort of thing originate from Sun. I like your points about certifications.

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589701728
Share on other sites

  • 0
  Asymptote said:
Wow these are excellent points that I never even considered. It makes sense that .Net typically roll out things (such as whatever it contributed to Vista) which was arguably inappropriate for the needs of the market because of its serious flaws, and I've not seen this sort of thing originate from Sun.

What? :huh:

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589701834
Share on other sites

  • 0
  Asymptote said:
Wow these are excellent points that I never even considered. It makes sense that .Net typically roll out things (such as whatever it contributed to Vista) which was arguably inappropriate for the needs of the market because of its serious flaws, and I've not seen this sort of thing originate from Sun. I like your points about certifications.

.NET doesn't have serious flaws, nor does MS' OS platforms nor its database server, and _kane81 wasn't implying that it did. He was merely saying that there are companies that prefer unix, which makes J2EE the preferred platform for them. Mono isn't mature enough to bet your business on just yet.

I work for a fairly large company with soon to be over 500 stores running on Microsoft platforms. We have to have 24/7 uptime as we are a convenience store chain. Our AS400 stuff is for our accounting system. We are converting to .NET in many areas, albeit with some growing pains, but we're finding better reliability and resilience in the platform than what we have/had in VB/ASP/COM, mainly due to the change in programming paradigm and a more robust platform. Most, if not all of the problems we have are due to developer problems, not platform problems.

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589701906
Share on other sites

  • 0
  _kane81 said:
Asymptote

I think you have misuderstood my post... (as stated above)

When I said "serious flaws" I was thinking of things like the emails between Msoft execs saying what a horrible o/s Vista was yet they had to sell it, or all the problems XP had before it got its first service pack. Aren't those operating systems written in the .Net environment?

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589708134
Share on other sites

  • 0

Most problems at launch with XP and Vista were driver-related and had nothing to do with the .NET framework, and as drivers mature they reveal themselves as versatile, fast and reliable operating systems.

Besides, XP was released 1 year before version 1.0 of the .NET framework. :rolleyes:

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589708336
Share on other sites

  • 0

I've worked with both C# (.NET) and J2EE (JSP, servlet, beans) in the past, I'd say it's easier to get a project start and running with C#, while there are more mature and open frameworks for J2EE, for example struts + hibernate. But then I'm not too familiar with MVC frameworks in .NET

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589708664
Share on other sites

  • 0
  wellofsouls said:
I've worked with both C# (.NET) and J2EE (JSP, servlet, beans) in the past, I'd say it's easier to get a project start and running with C#, while there are more mature and open frameworks for J2EE, for example struts + hibernate. But then I'm not too familiar with MVC frameworks in .NET

Thank you, Asik. I wasn't sure if it was because of inabilities of .Net or something else. Just one of those things I learn as I read more about this.

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589709164
Share on other sites

  • 0
  Asymptote said:
Aren't those operating systems written in the .Net environment?

XP and Vista are not written in .NET. .NET is a platform that sits on top of the OS. The OSes themselves are written in a blend of Assembly, C, C++, etc.

There is research going into writing an OS using mostly managed code (such as Singularity), although there will probably always be parts written in lower level languages.

Link to comment
https://www.neowin.net/forum/topic/661830-j2ee-vs-net/#findComment-589709378
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This was cool back in the day when done properly - loved having icons of specific devices.
    • Microsoft quietly burying a massive Windows 7 hardware driver feature as Windows 11 kills it by Sayan Sen Last month Microsoft announced a big update for Windows hardware drivers. The company declared that it was killing Windows Device metadata and the Windows Metadata and Internet Services (WMIS). For those wondering what it is, device metadata, as the name suggests, is the collection of additional, user-facing information that an original equipment manufacturer (OEM) provides about a hardware device. The feature was introduced with Windows 7 and can include stuff like icons, logos, descriptive texts, among other things, that help the Windows UI display details about such devices in places like Task Manager or Device Manager. This was a huge deal back in the day when Windows 7 debuted. The company called the feature "Device Stage" and Microsoft described it as a "new visual interface" that essentially worked like a "multi-function version of Autoplay where it displays all the applications, services, and information related to your device." It is often considered synonymous with the Windows "Devices and Printers" Control Panel applet. Neowin did an in-depth overview of the feature when it first launched which you can find in its dedicated article here. The Windows OS was able to obtain the device experience metadata from the WMIS, but now that the feature is being deprecated, Microsoft has begun removing information about Device Stage from its official support documents. Neowin noticed while browsing that a support article regarding automatic Windows hardware drivers was updated for Windows 11 and 10 sometime last year after the release of Windows 11 24H2. Previously, this article was geared for Windows 7 and was much longer. It also contained information about Device Stage, which, as mentioned above, was a headlining feature on Windows 7. In the said article, the section "If Windows can't find information about your device in Device Stage" has been deleted. You can find the archived version of the support page here. Aside from shortening the amount of information on the page, Microsoft has also added some more details on it. The company has now tried to define what the Microsoft Basic Display Adapter is, how updating drivers through Device Manager works, as well as a thorough and detailed troubleshooting section for common hardware driver errors on Windows, including one for USB-C. You can find all the new details on the updated support page here on Microsoft's website.
    • Sounds creepy to say the least. Don't need nor want AI having access to my history. They're claiming it to be an "offline" model now, but how can we guarantee they don't go behind our backs and change that?
    • Exactly! Without those fundamentals you've mentioned, Democracy is literally just Demonstration of Crazy, nothing to be proud of in such system.
  • Recent Achievements

    • Veteran
      Yonah went up a rank
      Veteran
    • First Post
      viraltui earned a badge
      First Post
    • Reacting Well
      viraltui earned a badge
      Reacting Well
    • Week One Done
      LunaFerret earned a badge
      Week One Done
    • Week One Done
      Ricky Chan earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      481
    2. 2
      +FloatingFatMan
      264
    3. 3
      snowy owl
      238
    4. 4
      ATLien_0
      233
    5. 5
      Edouard
      176
  • Tell a friend

    Love Neowin? Tell a friend!