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.
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.
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.
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.
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.
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 [email protected] if you'd like to discuss the idea further.
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. [email protected]
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:
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 [email protected]
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.