joestelmach

New York - Perka (getperka.com)

We're looking for engineers with an interest in Java / Android / iOS / JavaScript.

Perka was recently named one of Fast Company's most innovative company's in local: http://www.fastcompany.com/most-innovative-companies/2013/in...

We also contribute back to the open source community: https://github.com/perka

Please contact joe@getperka.com if you're interested.

Thanks! https://github.com/perka/backbone-ui/issues/9

That's a great point.

It's been on my todo list for a while now to remove the JQuery dependency from Backbone UI, since we're now only using it mainly for event handling and positioning.

JQuery was an obvious choice when this project was born over a year ago. I've since formalized my preferred method of DOM generation into the Laconic library, but have yet to do the same for the last bits of JQuery still being used.

care to elaborate?

Have a closer look - this library was built solely for generating UI from JavaScript.

No, this is not by the same people as Backbone. The name refers to the fact that all components are Backbone Views.

Here's an example of a real product built using Backbone UI: https://getperka.com/signup/#account

Thanks for sharing your viewpoint.

I realize that templates are a popular choice for many, but I view them as an unneccesary layer of indirection. Sort of like printing out an email, hand writing a response, and scanning it back in as a reply. Once your markup has been converted to a document object model, why not embrace it?

Thanks for sharing.

JavaScript has come a long way, even from 2006, yet most developers still have the mindset that this sort of thing can't perform well. What we're left with are solutions that are more complex, and perform similarly for most applications.

Thanks for the tip, but I've had much success using this method on teams of 5+ developers and a full-time designer.

I'm only disagreeing with the use of the word 'performant', and the popular viewpoint that any solution that isn't as fast as possible can't be labeled as such.

While I agree the $.el prefix is annoying, I don't believe it has a negative effect on readability. For me, templates are just another level of unneccesary indirection.

While I don't entirely agree with your first statement, you could just grab the outerHTML instead of appending the element directly to the DOM:

  $.el.div($.el.span()).outerHTML

Many would frown upon polluting the global name space with functions corresponding to all known HTML tags.

Though I did a poor job at documenting it, $.el is actually a function that accepts a tag name as the first parameter. The following two snippets are equivalent:

  $.el.div({className : 'foo'});

  $.el('div', {className : 'foo'});

Thanks for the feedback.

The chronic project was actually the original motivation behind natty. I think the chronic project is great, but I believe the grammar-based, AST approach is the way to go for long-term maintainability.

Implementing relative times has been on my list of things to do (in addition to recurrence.) I created a feature request here: http://github.com/joestelmach/natty/issues#issue/4, so feel free to list any time formats you'd like to see implemented.

I agree that a generic list of test cases would be nice. Any thoughts on how such a list should be published?

Thanks for the feedback.

I'll admit to the amateur mistake of not handling leading white space (that's now fixed on the master branch.)

It looks like the only example from your list that couldn't be parsed is "The day before Sunday week". Forgive my ignorance, but I've never seen 'week' used in that context here in the US. If you'd be willing to describe the proper use, I'll look at implementing it.

As for the UK format, please see the issue I created here: http://github.com/joestelmach/natty/issues#issue/3, and lend some advice if you'd like.

The test set is available here: http://github.com/joestelmach/natty/blob/master/src/test/gun...