Seems like the Dash dev disagrees with the icon author on where the line between "inspiration" and "plagiarism" lies. It doesn't help that there's a language barrier between the icon author and Dash developer.
But sadly it seems like this issue hasn't been rectified, but has just been forgotten about. I only found out about this after I'd bought a license; I'm posting this here in case someone else finds it relevant to their purchasing decisions.
I'm not familiar with the controversy besides what you posted, but my take away is that icon dev has some talent. The bookcase D is clever and well done, at least at that size.
In the link for the alternative icon, the icon designer has declined to enter any new discussions, as he felt "insulted" with the Dash developer's reactions on Twitter. He feels any more discussion is "a waste of time."
At any rate, I wish we non-Mac users had something like Dash.
In the interests of quoting the full context rather than just a few words, here's what he said in full:
"Dear The Great Developer of "Dash.app".
I do not ask you anymore.
I do not say anything about your icon.
It's a waste of time.
But I am vindictive.
Conversely, I inspired from your icon.
This is the way of my protest.
This time, you do not plagiarize this my icon, please.
Sayonara さよなら."
It seems the designer is Japanese, so there might be a language/cultural barrier too, but for what it's worth I think I would feel insulted by the Dash developer's reactions too!
Not to mention you can import and make your own DocSets, can integrate it with Xcode and much more. If you're developing anything on a Mac, you should probably have this installed (and pay to support it of course).
It's also a snippet manager, though I don't think many people use it for that purpose.
I love Dash, it's saved my butt when I've had spotty or zero Internet access. However, I've found that on my laptop it is far faster to do a web search for documentation than it is for Dash to do the search locally.
No, a better submission would have been a title that says what it is.
The idea that I have to click to find out is nonsense. It's link-bait.
I would have never clicked if I knew it was docs for HTML/CSS/JQuery, no matter how slick.
I thought it was something more exciting, like a service where developers can submit their own docs and it's a central repository of sorts. Now that would have been interesting.
This is awesome and I'm going to start using it today.
Suggestions: Look at what AaronO built and use it to add other sources.
Keep the current interface free, but let me pay some amount of money per year (or month?) to create an account and configure what sources it looks through. I'd like to have it search through django, python, git, and bootstrap docs as well.
I agree, dev doctor is awesome! It integrates everything on devdocs and more (caniuse, MDN for instance). Works seemlessly with alfred, making doc lookups super quick.
Full disclosure: friends with author of dev doctor
Doesn't look like it. See the about page, I think that's a pretty good indicator he intends to host it (although might be open to selling a license).
Why isn't this project open-source?
Ultimately I'd like DevDocs to provide me with some income so I can keep improving it over the long-term. Until I figure out how to do that I've decided to keep the project closed-source. If you have comments or ideas about this I'd love to hear them.
Found a big bug: use up/down arrow keys to select an item on the left, then hit right and left keys to open and close the sub-lists. But, if you hit right twice or more it will append the sub list continuously below.
Although you have browser support covered on a doc-by-doc basis, I would find it useful to have a rollup page by browser of gotchas. e.g. all the common JS gotchas for IE8 (e.g. no go on client.innerWidth), IE9 not supported opacity, etc.
Just a feed back: For me, I click on HTML(1) in the menu on the left, and it expands below the page. There seems to be a thin scroll bar to the right to scroll down, but I cant grab it to scroll down. Only arrow keys and mouse wheel work. IMHO, scroll bar needs some work.
Edit: (1)Correction
I click on HTML, then HTML5. Then the list goes below the bottom of the browser, then I cant grab the scroll bar.
- I don't have to select a programming language before I can start searching
- It handles keyboard input a lot better. As soon as the page loads, I can start typing, move down with the arrow keys and activate a selection with the enter key.
It seems odd that something that's just fetching and displaying snippets of HTML doesn't have a non-js fallback. But from the About it looks like this is a personal project made public in case anyone else finds it useful.
Really nice! It would be usable if it was free software so I could add docs for the different libs&langs I'm using. When it's closed, it's sadly not usable (although a very nice show).
I am using WebKit nightly (which should be categorized under "Safari 5.1+"), and it gave me a warning that said my browser was unsupported. As a user of a potentially unstable browser, I don't mind when sites freak out because it's usually something I can report back to the WebKit team. So I'd really like to see if my bleeding-edge Safari (I guess this would be 6 technically?) can run DevDocs… :)
Here's a suggestion. My favourite source for Rails docs is apidock.com because it allows people to comment and supply examples. It would be really nice if devdocs could incorporate something like that or perhaps even a wikipedia-like way to update the docs.
As a long time technical writer, allow me to convey my sheer joy at how awesome this is. Issues with the submission and its descriptiveness in terms of HN standards aside, this is super wicked awesome and makes me warm and fuzzy inside.
How is this site made? It looks like changing pages are ajax transitions but the url is changing at the top? Could someone point me in the direction of how this is made please. Would be really interested.
I'm not sure that it's the only reason why IE isn't supported, but currently no version of IE supports the history api, which is a bit of an annoyance if you aren't developing a site that you can block certain browsers from using.
Very simliar goal, but offline and instant. After using it for a while it's hard to imagine going back to reading documentation in a web-browser.