Devhints: A collection of developer cheatsheets | Hacker News Reader

Devhints: A collection of developer cheatsheets

devhints.io

259 pointsjhabdas29 comments

This looks like a really useful resource that I will inevitably forget to ever use in the future and will instead, continue to google/stackoverflow programming questions.

that's why God created pinned tabs

TIL about pinned tabs

still surprising that God possessed several developers just to force them to implement such a feature in specific browsers.

i think the EU should open another case of favoritism and give out penalties against these browser vendors. Thats definitely an unfair advantage if God is helping in their development.

The nocode cheatsheet is pretty darn helpful. I couldn't find it anywhere else. Thumbs up.

It's odd that nocode uses the Apache 2 license. I'd have thought they'd go for something that is maximally permissive so that nocode could be used in all applicable situations.

I really like this. Nice, easy UI, small and simple code examples. I'd see myself using this a lot for stuff I'm not 100% sure about. Nice work.

For the Mac users interested in this, I highly recommend Dash[0], which is an awesome offline alternative and has some ui integration as well. Works on the plane, unlike a website.

[0] https://kapeli.com/dash

Dash has a nice landing page but, after trying it personally a few years ago, didn't care much for its portability or pricing and ended up going with devdocs.io in a pinned tab for the majority of my web development needs.

I have been on the road a lot and with spotty connections, the offline capabilities of Dash are unsurpassed. Also, offline copy of Stackoverflow is golden.

Devdocs is offline-first. :/

Devdocs desktop app https://github.com/egoist/devdocs-desktop

`brew cask install devdocs`

Also I don't really like pages that don't immediately tell me what I get for free and what I will have to pay for. If you will put all your good features behind a paywall, I don't have to waste time downloading a trial. Other way, if you don't tell me I'm going to get pretty much everything I need for free, just with some small limitations, I might not try it, just because I think it's not worth it, without knowing what I get.

From ES6 section, first thing I notice:

> let is the new var. Constants work just like let, but can’t be reassigned. See: Let and const

I say it once, I say it one thousand times: "Let is not the new Var".

They certainly have some similar behaviors but surely they do communicate very different things to a developer who is reading the code.

let: "you shouldn't/can't edit outside this block scope"

var: "feel free to change me whenever you want inside this scope (whether it's global or function)

JS stuff aside, this is actually very helpful.

I think the point being made is that `var` used to be the default assignment operator due to a lack of better options. This has now changed. And it's debatable whether `var` is still useful given its "odd" (i.e. unexpected) behaviour.

Personally I'd go further and say `const` should be used by default and `let` should be reserved for when you really need it.

Not sure how much this overlaps, but I also have this bookmarked:

http://overapi.com/ "collecting all cheat sheets," repo at https://github.com/overthecs/overthecs.github.io but I don't see a lot of changes in the past few years.

Looks very nice, like how it's organized. But the cheatsheets I was intersted in aren't complete. Namely, I'd love to use a more complete bulma cheet sheet, likewise, if you ever get around to adding Django, that'd be phenomenal too! Anyway, great looking site, good job.

If you know of improvements, you may be able to submit them via the github repo: https://github.com/rstacruz/cheatsheets

Looks great and helps lay out certain things in a concise manner.

Seeing some visual bugs with headings. https://devhints.io/xpath for example, currently has misaligned sub headers for most of the sections.

Devhints is a go-to for me with Elixir-related questions. Insanely well put together!

I guess all it needs now is a sweet SVG favicon?

What are the advantages of using this over tldr[1] or cheat[2] ?

[1] https://github.com/tldr-pages/tldr [2] https://github.com/chubin/cheat.sh

One that I could think of is that you're using a system with strict permissions so you can't install or use either of them.

And after looking at how cheat.sh works I wouldn't use a tool that requires me to curl everything. Some may like to use it, but I prefer not to.

Cheat (not Cheat.sh) doesn't require any admin permissions to install (with homebrew at least) https://github.com/chrisallenlane/cheat

Honestly, it's more work to use the curl command and for some examples I've tried with cheat.sh I didn't get any answer, which then costs me even more time to look up the actual answer.

Your tool tells me from the start, what I can get and what I can't get. So I go on the site, write down the language/framework/whatever and get an answer. Better UX and to be honest, way better and modern UI.

I'm aware of [1] and [2] but never used them, honestly they seem to be a bit too much for the problem they try to solve. I could be wrong since I haven't used them, but that impression is why I haven't even tried.

I appreciate that this is quite low-friction. One click and I can see quick examples of bash (which I don't script enough in to be comfortable with the syntax).

But regardless I'm not super keen on cheat-cheets in general either.

I don't understand exactly how this is low-friction in any possible way...

1. Open browser -> Go to devhints -> search for "dd" -> select doc

2. Open term -> type tldr dd

Another thing that is missing is offline access, localStorage integrates in minutes...

I simply feel like this is someone trying to reinvent the wheel and also that this medium (a website) might not be the best way to do that. Sure it has a pretty frontend and a somewhat decent user experience for a web "app", but I (and probably many more devs) spend about 90% of my day in my terminal...

Installing something means to open a browser in the first place, do research, install it, and then launch it and figure out how to use it. Many many orders of magnitudes worse.

Yes, the benefit comes from already having it installed and knowing how to use it next time. I'm saying that the problem it solves isn't worth going through all that hassle even once.

Unrelated comment but how did they make the gif so long on cheat.sh?

The file was only a small size of 621kb and almost 1 minute long

Reply on news.ycombinator.com