On Fri, Sep 26, 2014 at 1:30 PM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:

> On 09/26/2014 09:45 PM, Rob Reynolds wrote:
> >
> > Java just on server side. Native is moving towards C++.
>
> No wait, what, really?
>
>
Felix, if your "what?" is about Java (the language), that was a mistake.
JVM on the server side, generally written in Clojure, is the direction
things are heading. C++ on the client side. Ruby is still sticking around
in order to support extensions. That said, some things we'll need to
discuss and figure out what the best way to move forward is. Luke wrote up
a good post about some of these changes at
http://puppetlabs.com/blog/evolving-puppet-for-next-ten-years

As I said in my original response about apply, that is something that we
still need to figure out and something that will be coming up on puppet-dev
in the future. There is a lot to consider and discuss in that decision
because of the number of people and systems affected.


>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/5425CCD6.8050703%40Alumni.TU-Berlin.de
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Andrew Parker
a...@puppetlabs.com
Freenode: zaphod42
Twitter: @aparker42
Software Developer

*Join us at **PuppetConf 2014, **September 20-24 in San Francisco - *
www.puppetconf.com

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CANhgQXt7E%3Dw%2Bw4fhmvargeLdtDsdMvJ7CLFikKECBTiidZ-nYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to