04/24/08

Permalink 02:35:19 pm, 262 words, Categories: main, RemObjects, Oxygene, .NET, Cocoa, Mac, Windows, Linux

RemObjects Oxygene 3.0

As you might have seen, this week we've announced Oxygene, the next major release of the language formerly knows as Chrome.

I'm very excited about this release as we have a lot of great things going on. Like last year when we released 'Joyride', i find myself in the position where i've been using versions of Oxygene for the better part of the past eight or ten months, so for me it's been an incremental stream of improvements and new features and minor tweaks — for you out there who are currently using 'Joyride', it will be a major step forward.

We have a set of major language extensions there that (imho) rank up there with the introduction of Generics or LINQ, with the big difference being that while Generics and LINQ have come with the framework, and Chrome was merely being a good citizen by implementing them. The parallelism stuff we're shipping in Oxygene – starting with futures, but there's a lot more it it than just those – is a different ballpark altogether, and it's something you don't get anywhere else — not in C#, nor in any other mainstream language, managed or unmanaged.

You can get a first peek at Futures on our new documentation wiki at wiki.remobjects.com/wiki/Futures.

But of course futures and related parallelism features aren't the only thing, we have more exciting additions to the language that i'll talk about more as we near release.

The first release of Oxygene, incidentally, will ship on May 30. Make sure your subscriptions are renewed in time! ;)

Comments, Pingbacks:

Comment from: M [Visitor] Email · http://thinkersroom.com/bytes
Looking good. Although I wonder what's the rationale behind the name change? With the plethora of 'new' languages (Scala, Sapphire, etc) arent' you risking getting lost in the buzz? Wouldn't it be better to keep building the Chrome brand?
PermalinkPermalink 04/24/08 @ 16:28
Comment from: marc hoffman [Member] Email
M,

You raise a good point, yes.

I cannot go into the many details, but suffice to say this was not a decision that was done lightly and we are aware of the recognition and good-will that the "Chrome" name has built up over
the past months and years. But, given all the considerations that played into this decision, we concluded that the real strength of Chrome is the quality of the language and product itself, and our vision for where we want to take the language in the future.

Trust me when i say that lot of factors played a role here, and the decision we did make on this will be for the benefit of the product and all its users, more so than any other option we could have pursued.

I also believe that with the recent changes in naming conventions, from Chrome 1.0 and 1.5 over Chrome "Joyride"™ to now simply Oxygene, and with the already public use of "Oxygene"™ as a beta code name for version 3.0 for a while, this name change will flow over almost naturally (as natural as they come, at least). Of course there will be some initial
friction in the transition, but ultimately, we believe Oxygene will be
a great name for the language and product.

thanx,
marc
PermalinkPermalink 04/24/08 @ 18:04
Comment from: Eber Irigoyen [Visitor] Email · http://ebersys.blogspot.com
very nice
PermalinkPermalink 04/24/08 @ 19:02
Comment from: Richard King [Visitor] Email
I know the name change is a done "deal"; but I'll still put in a vote to retain the Chrome name in some form. I loved the MonoChrome (and SilverChrome?) play on words. Mono-Oxygene doesn't have the same ring.

Also, many Delphi developers have heard of Chrome so now they will need re-educating. But maybe this is an opportunity to bring more across.

Let's make sure we pronounce the new name right -- is it Oxy-Jen or Oxy-Jean? (I'd say the latter given the final 'e') just like we say Del-fee and not Delf-eye down here.

Richard
PermalinkPermalink 05/07/08 @ 05:27

Leave a comment:

Your email address will not be displayed on this site.
Your URL will be displayed.

Allowed XHTML tags: <p, ul, ol, li, dl, dt, dd, address, blockquote, ins, del, span, bdo, br, em, strong, dfn, code, samp, kdb, var, cite, abbr, acronym, q, sub, sup, tt, i, b, big, small>
(Line breaks become <br />)
(Set cookies for name, email and url)
(Allow users to contact you through a message form (your email will NOT be displayed.))
This is a captcha-picture. It is used to prevent mass-access by robots.
Please enter the characters from the image above. (case insensitive)

 

marc hoffman

Chief Software Architect &
Spare-time Photographer

mh

Links

Twitter (experimental)

  • loading...
follow me...

Navigation

Search

XML Feeds 

Who's Online?

  • Guest Users: 42

Flickr