News for hackers. Stuff that matters.
Re:Otto, the successor to Vagrant by divan on Monday September 28, 2015 @03:35PM (#10292576)
Otto uses Vagrant under the hood.
Re:Otto, the successor to Vagrant by vezzy-fnord on Monday September 28, 2015 @03:37PM (#10292600)
Indeed, which makes the tagline "successor to Vagrant" a dubious choice. It would be like referring to fleet as the successor to systemd. They're stacked layers driving existing utilities.
Re:Otto, the successor to Vagrant by ChuckMcM on Monday September 28, 2015 @04:15PM (#10292881)
That makes sense, the announcement seems to imply that really the problem was that Vagrantfiles were too restrictive, so make a Vagrant 2.0 that can read the old files (and will whine) and it uses the new super "Appfile" format as its native format. Maybe there is a tool to convert a Vagrantfile to an Appfile automatically (as Appfiles are supposed to be able to do everything Vagrant can do and more)

Anyway, in a more typical software development environment you'd provide such transition tools and carry your users along, so that the next version already starts with a huge base of users. Rather than throw out the old way and come in with a new completely incompatible way to do things.

Very confusing.

Re:Otto, the successor to Vagrant by verbin217 on Monday September 28, 2015 @04:20PM (#10292920)
I think the idea is that Otto is the (new) interface and Vagrant is a potential implementation. A 2.0 would hide this distinction.