I'll bite. I don't particularly dislike Airbrake, but I don't particularly like it, either, and I periodically want to use something else:
1. The hideous UI. =)
2. Airbrake would 500 when trying to render the data about some of our 500s! A Rails app I work on was raising Rack exceptions about UTF-8 encodings, but viewing them on Airbrake caused it to fail, too. Meh.
3. We had to disable the JS error handler, as it would routinely take 3+ seconds to download for clients, or just time out entirely. Meh.
4. A few people on my team just never received the emails from airbrake. They were registered with the right address, it didn't go to spam, etc. It just never showed up. We gave up and switched it to mailing our foo-dev@ mailing list, and now people that have no ability to address the issue (and, honestly, mostly overreact to exceptions =) get the email, too. Meh.
See, it's just that "Meh." at the end of everything. A pretty reasonable summary of my Airbrake experience.
I have been passively searching for a new error monitoring service, so I clicked this link from my phone while on a train to work. I'm not going to find headphones, wait on a video to load, and then hope it's high enough quality on my phone to be a useful look at what you're offering. And the About page is hidden beneath a 'Docs' menu, which is actually right next to two links that take me to a sign-in form, so it never even occurred to me to look for it. I thought 'How It Works' was all you had besides the video.
So I added it to my "hey maybe come back and look at this some day" list of TODOs. That's a very big list. I rarely actually go back and look.
Had it been two screenshots of a decent UI and a quick blurb about your (likely very useful!) grouping/filtering functionality, I'd have been much more likely to make sure I went back to view the video.
That said, I'm now watching the video, and this looks pretty nice. Good luck!
I've been using Windows.app for about a week now and use it pretty extensively these days. For whatever reason, I could never work divvy/sizeup/slate/etc. into my workflow; the config UIs generally felt tiresome or overwhelming.
You can configure it with JS or CoffeeScript, and using JSCocoa gives you access to most (all?) of Cocoa's API to do as you please. And the latest version has a minimal REPL that you can use to tinker.
The author has a nice config you could paste into ~/.windowsapp.coffee to get started:
Which is perfectly fine. I mostly want to be able to trivially use packages which solve my trivial problems, so I can move on to something more fun.
The issue eventually becomes a one of search; when I'm looking for a package, how do I know which are maintained, which never picked up broad adoption, etc?
Between the npm registry[1] and node-toolbox[2], there's already decent visibility into it. I often find the output of 'npm search' daunting to the point of mental paralysis, though.
The Unicode Consortium manages the process of defining the unicode standard. Various committees are formed, composed of representatives from whatever other standards bodies are interested and from companies with a stake in the standard.