TJ
TJ
yikes! what a verbose way to get a url :s I know what you mean though, rails (and I guess every mvc framework) has similar.
yeah :foo essentially attempts to consume as much as possible within a path segment, whereas \* grabs as much as it can spanning segments ("/")
just brainstorming, in a lot of ways tarballs would be superior to npm/gem etc
yeah, it would be more akin to go's nice binary stuff, really hot to roll up your deps into one thing
well you could do a number of things, you could build the tar ball on one server and push it out to the others etc, or cross compile
expresso is defunct
yeah I was thinking about making it a more generic shell-like language, I have mixed feelings on that since it's already (and will probably be more so) geared towards provisioning....
I want to change up the DSL (or lack of) quite a bit actually haha, might warrant doing a little interpreted language, stack will just be ship with that lang...
yea I like that too, I guess it's really just fancier `set -e` at the moment, which itself is pretty sweet for provisioning haha, sucks that the rest of shell...
yeah I have to say pretty much the only thing I like about shell scripts is that commands are first-class haha that's about it, `foo(){}` is a pretty nice syntax...