Hacker News new | ask | show | jobs
by sdfhbdf 1962 days ago
It's not bashing a tool per se, sorry if you read it as such. I was pointing out that with the abundance of tools we have at our disposal this project sounds to me like a solution looking for a problem.

As for the solution not existing yet - as people pointed out there is tar, zip, git, and shar which all seem to accomplish the same thing
1 comments
BoorishBears 1962 days ago
Did you read the very thorough rationale provided by the project page, complete with pro-cons for many other methods?

I have no idea how someone could read such a thorough README and say "this sounds like a solution looking for a problem" with a straight face.

link
sdfhbdf 1962 days ago
Yes I read it and I don't agree with the posted downsides for most of them, since the tool itself seems to share the downsides with the posted pro-cons of other solutions and doesn't seem to solve any problem it promises to do.

Is visibility into what's being created a problem?

The listed problems like "everytime the template changes, author has to rezip and reupload the folder" don't seem to be solved with stamp to me, it seems like the problem is now shifted to controlling a version of this new format and still distributing it somehow (probably through git) at which point you ask yourself why can't the git repo already have the structure? If somebody wants to rename something they do this really easily, no need for var substitution.

If there was a migration mechanism that would move files from an old template to a new one I would see value added.

link
iudqnolq 1962 days ago
The difference is you can directly edit the file in a text editor (possibly even in the github ui) instead of needing to unzip, edit, and rezip.

It makes find and replace across all files trivial with your editor, whereas that would be less fluid with a zip.

link