Like nitrogen explains as well, it's just too much, even if you concentrate on what you are actually usually working on/in, depending on what your field is. I.

Like nitrogen explains as well, it's just too much, even if you concentrate on what you are actually usually working on/in, depending on what your field is. I.e. if you are working on anything that is currently a 'web app' of some sort, then depending on what company you were at, you would either be using one framework or another. So you might write in the "I know technology X" column things like "jQuery, React", because your last job used JQuery, then they grew up and switched to React. In the "I don't know technology Y" column, you write things like "BackboneJS, AngularJS" etc. (the actual lists would be much longer, this is just to take an example). You're still current if you use either Angular or React it just happens that you (or someone at your company) didn't choose one but the other. And then there's the myriad of other frameworks that come and go or that a particular niche of companies might prefer. If you're a web app FE or full stack guy you can still pick any of these up easily enough, so it makes sense to list them for the "pattern matching HR drones" (or computers :)) to get the interview.