I just published a couple of new videos about Oxygene 5 (with more to come), but I thought I would like to clear up a couple of things with regards to names. When we say Oxygene for .NET or Oxygene 5, we are generally referring to the technology that powers Embarcadero Prism XE2, formerly known as Delphi Prism.
What’s in a name? That which we call a rose
By any other name would smell as sweet.– Juliet in Shakespeare’s play Romeo and Juliet
Oxygene is RemObjects’ compiler technology. A couple of years ago, Embarcadero licensed Oxygene to replace Delphi for .NET and this new product was branded as Delphi Prism. Now with the release of XE2, we are releasing our new Oxygene 5 compiler, which now has two personalities: Oxygene for .NET (which continues to power Prism) and Oxygene for Java. That means that Oxygene is more than just the heart and soul of Embarcadero Prism, it exists in two forms, so it is more important to identify it as Oxygene.
- Oxygene 5 = The Next Generation Object Pascal for .NET and Java
- Oxygene for .NET = Embarcadero Prism XE2
- Oxygene for Java = The product formerly know as Project Cooper.
What happened to the “Delphi” in Delphi Prism? This is really just a branding change that we and Embarcadero decided on, in order to better keep Delphi and Oxygene apart – but the next generation Object Pascal language you know and love in Oxygene is still there. If anything, it just got better.
What does this mean for the average developer? Well, if you know Delphi’s Object Pascal, then you can use those same skills to work with .NET and Java now – thanks to Oxygene. If you have RAD Studio XE2, then you have Embarcadero Prism XE2, which includes Oxygene for .NET. If you don’t have XE2 yet, head over to our secure online store and pick up Prism XE2 or a bundle that includes both Oxygene for .NET (via Embarcadero Prism XE2) and Oxygene for Java.
