3 ms·
Yeah, we're still working on a way to make this work better for the sort of ongoing web development that most HN readers probably spend a good amount of time do
by tghw 15y ago
Yeah, we're still working on a way to make this work better for the sort of ongoing web development that most HN readers probably spend a good amount of time doing, but we do think it is very useful for smaller sites that don't need parallel deployment of markup and style changes.
We're also releasing this very early, for a Fog Creek project, to see what people think. It might be that this becomes a desktop tool using something like Titanium, or we might try to integrated version control into it as an alternative to publishing. As such, we're open to suggestions and feedback.
- dolinsky 15y agoFirst, congrats on the product as I don't want to come off as being a bowl of sour grapes when that's not the case. I totally dig the concept of immediate results for changes made. Like I said in my OP, I'm approaching this from the viewpoint of a team of more than 1 where there are multiple environments to account for so that's my starting point. For a very small team / personal site built using Rails that has no development environment I can definitely see the usefulness of this product.
- tghw 15y agoThanks! Your point was one we expected to hear, especially here on HN. We actually did look into getting Mercurial (which is what we use internally and what we provide via Kiln) up and running in AppEngine, which has been done before, but was just beyond the scope of the first phase of the project. And I agree, I don't think we'd ever host FogBugz's or Kiln's CSS with it on AppEngine, but I do really want to be able to use the editor and SCSS with those projects, so we'll be keeping an eye towards making that more natural.