Viewing profile — magaudet

Chris is definitely an inspiration to many, myself included.

For those curious about background: https://blog.cloudera.com/blog/2013/02/inside-cloudera-impal...

While the 'Pitfalls' paper was implemented on top of the Testarossa compiler technology (that underlies the OMR compiler technology), the OMR project has spent a lot of engineering…

Thanks so much for posting this! That was exactly what I was curious about!

Alas, our connection Eclipse is only a legal one. We are an Eclipse Foundation project, but not directly related to the IDE. So won't have any impact on eclim. Sorry!

When you say "native languages" you mean a statically compiled language? It's been done before with the technology underlying the OMR compiler component, however there is some work…

I really enjoy meeting up with the JRuby+Truffle people whenever I can at conferences. Though our approaches are really different, there's definitely a cross-pollination of ideas: …

Not as well as I should be able to, for sure. In my mind, I look at Truffle and Graal as a potential way forward to build new high performance JVM languages. OMR I see as a way to …

It's great. I do it every day: Headless ubuntu image that I then use Cygwin's X server to SSH into and run xfce4-terminal. Only disappointment has been my laptop's decreasing stabi…

Someone out of band poked me to give an eye as to what I see the roadmap is. I'm currently working on getting the JIT working with Ruby trunk ( https://github.com/rubyomr-preview/r…

Thanks! That's definitely the exact hope we have for OMR as well. Similarly, improvements in OMR can be shared among all languages using it; ie, because we build both IBM's Java JD…

I have some performance numbers from my original talk at RubyKaigi [1] [2]. Still a ways to to go, but we've built out a reasonable foundation to start with. [1]: http://www.slides…

Officially, OMR is a meaningless title, like LLVM. Similar to LLVM, it once stood for something, but then we realized that it didn't actually match the project's 'charter' quite as…

Whoops! That's actually an editing mistake: The Ruby+OMR preview is actually for Ruby 2.2 right now. You can follow the work in progress on trunk (what will become Ruby 2.4 in Dece…

Author here: Feel free to AMA!

Hey! thanks for the shout out. I would totally love to see more feedback as well! We haven't turned on the issue tracker on that repo, but the glue has it's issues turned on: https…

Hey, OMR developer here. Ruby+OMR is developed in three pieces: 1) the language independent core, then 2) The language dependent portions (i.e., the VM, and what we call the 'glue'…

OMR Team member here: Glad to hear you had a good experience with our tech preview! We really appreciated the feedback you provided, and would definitely be willing to take more.

Unfortunately no dates. We're still working on this, but we really want to do it right, so we're taking the time we need. Sorry!

(IBMer working on said JIT here) As Chris Seaton points out as well, we're not really open source yet. Working on getting there, but it's going to take time. The important thing no…

One of the key parts of this project is that we are using the code in production. Each piece is being used in our shipping releases like Java. Open sourcing will happen. Doing it r…

(BTW: Count me as a very happy user of Bench9k. It's been a very appreciated tool here. I'm hoping to contribute some of our harness customizations back when I have the time to cle…