News for hackers. Stuff that matters.
Re:Ansible 2.0 released by crdoconnor on Tuesday January 12, 2016 @06:46PM (#10891283)
The point is that it's not turing complete. Thus it's more readable, less susceptible to technical debt and less susceptible to bugs and always by definition, declarative.

Turing complete code turns into an unreadable mess far more easily.

Re:Ansible 2.0 released by wstrange on Tuesday January 12, 2016 @09:15PM (#10891918)
But isn't in fact Turing complete?

It has variables, control structures, loops and exceptions.

Re:Ansible 2.0 released by jzd on Tuesday January 12, 2016 @09:36PM (#10891990)
That does not make it Turing complete.

"You need some form of dynamic allocation construct (malloc ornew or cons will do) and either recursive functions or some other way of writing an infinite loop. If you have those and can do anything at all interesting, you're almost certainly Turing-complete." -- http://stackoverflow.com/a/449170

Re:Ansible 2.0 released by wstrange on Tuesday January 12, 2016 @10:00PM (#10892069)
There is a do-until loop: https://docs.ansible.com/ansible/playbooks_loops.html#id22

Which satisfies the infinite loop issue.

Have not looked carefully at the dynamic allocation, but I am guessing (hand waving here....) that it could be accomplished.