Micah

Our expectation is that people will likely want to use one or the other for their projects since that's what people have wanted from us. Like has been said though,...

To add onto this, we aren't going to do the above soon and in fact don't even have a ballpark estimate for when we'll do it. We anticipate having to...

We can if nothing else change that error to indicate what file it's having difficulties writing to, but I'm not sure this is a bug. Can you try running Rojo...

Alrighty thank you, I'll take a look. I suspect you're probably right but we shall see.

Can you confirm that nothing else is bound to that port?

We *are* working to make this less destructive by adding ChangeHistoryService waypoints and asking users to confirm the details of an initial sync, including deletions. Those are merged into the...

I'm open to a top-level setting like that. It certainly makes compatibility easier. I'll talk to the other maintainers to see how they feel but I think it's a reasonable...

> I think it's fine to introduce breaking changes with no backwards compatibility considerations. Users can always stick with the older version of Rojo until they're ready to correct the...

A thought: how comfortable are we with being annoying to the end-user? I want to push people to include a `version` field for projects, but having a warning every time...

So, I've thought about this off and on. I definitely see the appeal of installers because it would remove some of the friction from users, but I don't think it's...