Forgot your password?

Close
typodupeerror
Java

smitty_one_each's Journal: Does Easy Virtualization Render Java Moot? 13

Journal by smitty_one_each
It always seemed the chief selling point of Java was the JVM, so that robust applications could be deployed more places, yet run in a way that shielded the environment on which they ran.
Now you can virtualize Linux on Windows on OS X on whatever, and write an application that uses a system which is a fat or skinny as you like, integrating whatever fits well with the virtualized OS.
What is the motive for doing Java anymore, beyond its blessed coffee connection?
This discussion has been archived. No new comments can be posted.

Does Easy Virtualization Render Java Moot? More

Does Easy Virtualization Render Java Moot?

Comments Filter:
  • One giant reason. Also.. the dirty little secret in IT is that performance wise, virtualization mostly sucks - especially if your app is resource intensive.
    • I've installed a Hadoop cluster, as a matter of fact.
      Nothing going on that seems too Java-centric. I guess that Java does a better job of maxing out all your resources.
      However, I can't believe that a custom filesystem wouldn't do better than HDFS/[whatever], just by throwing away excess indirection.

  • Java. It's the Cobol of the 2000's. In everything for businesses everywhere.

    Also, virtualizing infrastructure is not automatically virtualization of application logic. I can't just "spin up" a second and third Exchange server, having them auto-join an existing pool.

    A new app model that is also virtualized is needed.

    The way that this is panning out? Agile and horizontal application scaling models for Java, that are coupled to context, not to specific topology and can be easily instantiated and pooled.

    The

    • I sincerely thank you for a what amounts to a 'mental bagel' of a response. I'll be chewing on that a while, to ensure that I actually grasp the fullness of what you said.
      It's like a blast of the old Slashdot, where I felt like I learned something while flaking off here.

      • Sure!

        Someday, all compute will be so transparently virtualised and managed as a fabric, that we will pay as little attention to it as we now do for block allocation on storage devices... The applications will do the work.

        We aren't there yet...

        I had as a customer the very large, online auction site.(TM)

        They insisted that Java was their virtualization layer/strategy for years. as the concept of "cloud computing" entered the discussion, around 2007-8.

        I worked hard to establish the value of server virtualizati

        • In moving to the Information Age, we lifted information off of paper and ran it on hardware. Now we're moving information off of explicit hardware and making it more fluid. You can seriously go after "Test Driven Network Engineering" now. The irony of modern life is that, for all of the Really Smart People doing this sort of thing, our political leadership is a pack of relative dunces.

  • moof (Score:1)

    by Bill Dog (726542)

    Java was invented by Sun because Wintel was the near-universal platform, and Sun had no revenue stream from it (i.e. no reason to buy expensive Sun hardware). That and, the language of small business being VB and that of big business COBOL, I think an updated language for the "I only care about solving business problems" crowd was conspicuously needed. Java would be advertised as the "programming language for the rest of us" (meaning non-technical developers) and at first appear very simple, until the layer

    • "I can't really add garbage collection to native code by running it in a VM."
      The point of my post is that the VM, itself, becomes The World's Crudest Garbage Collector.
      In #3, you use SMB. Do you mean Samba? I thought that's CIFS now.

      • Re: (Score:1)

        by Bill Dog (726542)

        SMB as Small and Medium-sized Business.

        Being a fan of deterministic destruction (I love symmetry, and things working like clockwork), it was hard for me to "let go" when switching to a managed language. Instead of taking the candy out of the wrapper and throwing the wrapper on the floor temporarily, knowing that I (or the compiler) would be picking it up again right after finishing the candy, I had to get my mind to being at peace with just throwing wrappers on the floor and trusting that, if enough of them

Pyros of the world... IGNITE !!!

Close