456 karma · joined May 6, 2011
1: How do I give my documents a title? 2: Does it support Markdown/how do I link to stuff? 3: The home button doesn't appear to work on an iPad
I may very well have missed something (I haven't published anything yet and didn't search too hard for instructions (it didn't seem to need any)) but thought I'd ask anyway in the hope that they prove useful.
I'm not sure how many of these problems this solves, but Wikis in general solve many of them.
Better then to count the meanness as validation of what you're working on and to extract the grain of truth as constructive criticism suggesting how you can improve.
Btw, is there a diagram or something that shows how it's put together internally (I'm pretty comfortable with how to use it from an API perspective, but find myself having to dive into the source code fairly regularly)?
Yes it's optional, and yes you can use jQuery.ajax or whatever, but in reality, it's not quite that simple.
The official guides in Ember default to assuming you're using Ember-Data (though they do at least mention it explicitly). This despite Ember-Data being far from production ready (as stated on the Github page) and far too slow for dealing with large quantities of data. At the same time, the conventions that are found in Ember-Data appear to be built in to core Ember (it says as much in the guides).
As far as Ember-Data not counting against Ember - it may be larger in scope than other client side data libraries (or the M part of other MVC frameworks or whatever) but the fact is that they are most definitely comparable, as it's the way that Ember gets stuff off the server, and saves it back to the server. Without Ember-Data, Ember has no built in way of doing that, which counts against it. With Ember-Data, well, it's not really ready yet, which also counts against it.
I'd be interested in why he believes this isn't currently the case.
I kind of wonder where else would be appropriate to wear it other than on your wrist, given that it explicitly mentions that (Geordi LaForge style visor perhaps?)
FTFY. There are a _lot_ of people who would disagree with you (which is why Beats/Skullcandy/etc headphones are so popular).
1. You have a business. 2. Said business has a website. 3. Said website is bringing in no discernable revenue for your business. 4. Poking around for reasons, you discover that your website ranks really lowly on Google. 5. You have no idea why. 6. You pay an SEO consultant. They take a look at your web site, and your overall web presence, to try and find out what's going wrong. 7. They discover that your markup is terrible, the wrong things are enclosed in header tags, etc. Also, you have little to no visibility outside of your website. 8. They advise some sensible changes to your markup, and force you to start posting things on Google+, Twitter, Facebook, etc. 9. Your ranking improves. As does your revenue.
Which bit of that process is evil and wrong?
Of course, there will always be a shady side to SEO (people taking it too far, etc), but there's a valid reason reason it exists: many people simply do not know enough to get the basic components right. SEO consultants help them do that, and improve revenue as a result.
On the other hand, if the slides are intended for reading, then yes, they may be a usability disaster. But then, slides aren't going to be the best format for reading anyway.
A lot of people have mentioned scatter plots.
I'd quite like to know how you'd represent relationships between things using only a histogram or line chart.
I realise that it's covered somewhat by the "95% of all cases" statistic, but really, as with most things, if all you're doing is visualising relationships, then that statistic is likely way off.
The general point is a good one - use a visualisation that's appropriate for representing your data not one that's appropriate only for looking nice, but I think the message is lost somewhere in amongst the rhetoric.
[1] http://code.google.com/p/google-caja/wiki/JsHtmlSanitizer
Isn't it the other way around? There's no effective way of publicising you app or helping people to find it in an app store short of hoping that the Apple/Google overlords will decide to stick it on the front page. It's remarkably hard to find apps that you're looking for unless you know the name of it (and it isn't a common name, etc), and there's no way of working around it.
In contrast, on the web, if one site doesn't work very well, you go to another one. If one discovery tool isn't working very well (e.g. Digg), you use a different one (e.g. Hacker News).
The web is very discoverable. It just doesn't force a particular discovery mechanism on people like app stores tend to do.
That said, this is a large part of why FirefoxOS is so promising.
While, to a large extent, I already knew everything that you'd written, I'd like to thank you for reiterating it.
Your conclusion may be valid, but I don't think the bug you found has anything to do with it.
[1] http://www.amazon.co.uk/Ninjutsu-History-Tradition-Masaaki-H...
It also points out that there's such a thing as going too far and that merely learning/using some of the techniques that psychopaths tend to exhibit (in a mild form) is potentially useful. It doesn't seem (to me at least) that he's directly advocating pretending to be a council inspector/whatever to kick people out of their home.