8 comments

[ 2.7 ms ] story [ 26.8 ms ] thread
The soy templates are a timesaver for anything that is going to be generated in JS and styled by a designer. We use it at work and I haven't regretted it at all. The only thing I want is a better handling of namespaces.

I am debating using the rest of closure for my next project but the verbosity is a little bit scary.

WTH's a soy template? And is it yet another proper name that insists on being lowercased?

(I know I can google it. It just doesn't make sense to me for there not to be an explanation in the article.)

I'm not sure if your question was rhetorical or not (I suspect it was), but for the record, it's a basic templating system for javascript and java like what most web frameworks have. You write a template with parameters ("hello $name") and basic commands ("{foreach $foo in $foolist} ..."). Then in your code you can parameterize the template with data ({name: "benatkin", foolist: [...]}) and it'll get expanded.
Whatever it is, apparently next-generation JavaScript tools are needed for its implausibly excellent dynamism.
I swear I thought those words would get edited out by someone else at Cloudkick. I wrote that half jokingly and I guess it made into the actual blog post. :P
I admit I didn't read past the first paragraph when you asked for proofreading.
It is a proper noun and is usually spelled with capitalization.
It is verbose, but that makes it readable. I don't really type that much more, I just use tab completion in vim.