I just read this thread so decided to add my 2 cents into the collection of opinions.
Guys, I tried it out a couple of weeks ago (was told about it by one of my colleagues). This is really incredible! Especially given that you completed it in 24 hours :) I think as YAQL attracts more and more users it will be very handy tool. I am actually for improving it further. Thanks a lot! Looking forward to switch to yaql 1.0! Renat Akhmerov @ Mirantis Inc. > On 05 Aug 2015, at 04:09, Stan Lagun <sla...@mirantis.com> wrote: > > Dmitry, > > yaql 1.0 has both str() and len() and much much more so there is no need to > support them explicitly since Mistral is going to switch to yaql 1.0 and > yaqluator.com <http://yaqluator.com/> is going to do the same > > Sincerely yours, > Stan Lagun > Principal Software Engineer @ Mirantis > > <mailto:sla...@mirantis.com> > On Tue, Aug 4, 2015 at 8:55 PM, Dmitri Zimine <dzim...@stackstorm.com > <mailto:dzim...@stackstorm.com>> wrote: > Awesome! Really. > > Thank you folks for doing this. > > I am so much looking forward to moving it to 1.0 with more built-in functions > and more power to extend it... > > Note that Mistral has a few extensions, like `str`, `len`, which are not in > the scope of evaluator. > > DZ> > > > On Aug 2, 2015, at 12:44 PM, Stan Lagun <sla...@mirantis.com > <mailto:sla...@mirantis.com>> wrote: > >> Guys, this is awesome!!! >> >> Happy to see yaql gets attention. One more initiative that you may find >> interesting is https://review.openstack.org/#/c/159905/ >> <https://review.openstack.org/#/c/159905/> >> This is an attempt to port yaql 1.0 from Python to JS so that the same can >> be done in browser >> >> Sincerely yours, >> Stan Lagun >> Principal Software Engineer @ Mirantis >> >> <mailto:sla...@mirantis.com> >> On Sun, Aug 2, 2015 at 5:30 PM, Nikolay Makhotkin <nmakhot...@mirantis.com >> <mailto:nmakhot...@mirantis.com>> wrote: >> Hi guys! >> >> That's awesome! It is very useful for all us! >> >> -- >> Best Regards, >> Nikolay >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org >> <mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > <http://openstack-dev-requ...@lists.openstack.org/?subject:unsubscribe> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
