mattinsler

I hate when I get emails from recruiters that say "Looks like you're a great javascripter. We have this awesome front-end position for you." Though if they understood my github and linkedin accounts at all they'd see that everything is node.js, ruby, java, etc. If getting away from the "classic" form of recruiting would cut that down I'd be thrilled! And now as an employer I don't want someone spamming candidates on my behalf in such an annoying way as well.

Oh shoot, I see what you mean. So sorry, I was stupidly testing with the trackpad which is obviously not arrow keys.

Sorry about that! The theme has issues on Firefox for some reason and I haven't been able to track it down (and the theme author hasn't responded either). This is horribly annoying, but try opening it in another browser.

Multiple ways. First off, Clarity costs money and AwesomeHours are free. Second, Clarity has a very specific focus around business advice. The point of AwesomeHours is that any expert can host for any topic. For instance, people have contacted me to host hours for personal finance, content strategy, and fitness. There will of course be business-focused hours as well, but that's by far not the focus.

This has to do with keeping some words reserved or just off-limits. For example, some 4-letter words would not be preferred as usernames, as well as things like login, auth, etc.

Please email us at contact@awesomebox.co so we can straighten this out!

Thanks so much! We hope you like the product!

You're absolutely right. I completely didn't think ahead with that project. I've actually had feedback from people who want to use it that I should change the whole project name too. Was just never sure of what exactly to call it.

Also, all of the code for Awesomebox is completely open source. Please check it out if you'd like.

The CLI client is here: https://github.com/awesomebox/awesomebox

The rendering core is here: https://github.com/awesomebox/awesomebox-core

Also, lots of the modules used in both the CLI and backend of the product are available here: https://github.com/mattinsler?tab=repositories

I promise this isn't a trojan horse! Trojan is actually an npm module that allows you to compile down nodejs code so that you can package it all as a single downloadable.

Check out trojan here: https://github.com/mattinsler/trojan

This helps with managing download times for all the transpiling code that we use for things like coffeescript and less and ejs.

At the time I wrote this module I thought it'd be funny to name one of the files horse to continue the joke. Definitely time to change that filename. =-)

I'd be happy to walk you through how all the code works if you're interested.

You're absolutely right! We're so sorry about that! It's fixed now. Thanks for finding that!

We're going to be following up with people to bring them into the product and helping them become successful with it. You're right though, a use case would help a ton. Perhaps this would be a good start to our blog. Contact us at contact@awesomebox.es if you'd like to discuss the idea further.

Better yet - if you sign up for the beta, we have a working product for you to try out.

Thanks for the feedback - this is really more a case of "two hackers trying to describe what we're building" than a "vague PR statement".

I think where we're struggling is narrowing down exactly what we do, without being pigeonholed into "just another hosting platform". We're really excited to talk to the many people who did signup and learn more from them, so that we can get better at this overtime. Thanks for being a "BS filter" and telling us where we're wrong - if you have more thoughts to share, we'd love to hear from you. contact@awesomebox.es

Totally understand the confusion - this is the first time we've put this out into the world, and it's great to get feedback about which parts are or aren't clear. Here's a bit more on what we're building:

http://awesomebox.co/vision

If that sounds interesting, we'd love to talk to you about the pain points you have building front-ends and UIs. Feel free to send us an email at contact@awesomebox.es

Thanks Tyler! Just pushed and added it to the homepage. Here's the link:

http://awesomebox.co/vision

Check out http://awesomebox.co/vision to see what it's all about.

Sorry about that! We'll add a link to the page from the landing page so it's easier to find.

Nice code, I'll update the readme to be more realistic.

Absolutely!

We actually had a special case of a UI that needed to have many many things updating via push events, and have profiled it a few different ways. Turned out that with the frequency of updates we were making, larger chunks of HTML ended up being multiple times more expensive than adding a class here, or changing the text in a tag over there. This method actually _was_ the optimization.

Rivets actually does a great job allowing you to create functions for similar formatting, which allows you to have very very short attributes, which in turn ends up being multiples of lines less than the equivalent javascript.

The main reason to write it into the HTML was to be more maintainable, by putting the presentation in the HTML presentation layer. Most libraries, such as rivets do very similar things for very similar reasons. When I know there's a data formatting issue in 1 element in the HTML, I can just fix that in the HTML. I don't need to go into the javascript and find which jquery snippet changes that HTML element and does the formatting.

With one exception. Spellbinder will add/remove classes as the model value is changed. It does the initial rendering and then will alter the html, style, classes, properties on the fly as you change the values in the model without reloading the page or re-rendering the view.

No benchmark, but it's been running in production for over a month and I haven't noticed any significant speed problems. Though admittedly I haven't looked for them.

Domains look awesome!

Sorry Tom! Feel free to take my code, haha. I'm actually making my own version of the kegbot right now for our sales team. It seems like I keep working on similar projects to you.

I definitely could have and hope that I gave enough credit where credit is due. It was 2am and I was trying to debug some issues in production and I needed a fix, so I patched Tom's code to make it do my bidding and then kept on tweaking things. It just turned into a full rewrite after a while and the name longjohn got stuck in my head, so I published it. No ill will meant.