I frequently find myself going back and forth on this. I've worked with a lot of technologies over the years, and some of them are pretty bad for my career. Notably I have a year of VB6 and Microsoft Access. I've omitted these technologies from my resume out of fear of being label "out of date". But I suppose there is an argument for being upfront and honest about the work you have done.
What do you think? Does bad tech go on the resume? When do you draw the line of what goes, and what stays?
I think a CV has to be truthful, but it doesn't have to be complete. You can choose what you want to highlight. I like to downplay Python even though it's popular (I think) and I did it quite a lot. But I don't want to be pushed to Python positions anymore these days.
I would add them to my resume.
Skill is a Skill and in most of the cases it is hard earned. Be it Visual Basic, MS Access or GWT. At one point of time these were much needed skills to acquire. Also I feel, we would have spent lots of hard hours to master those than we do today. Simply because, more resources and opportunities available now.
I wouldn't term those as bad tech either. Those are probably something least important today, that's fine. I will add.
I would also publish my resume as a timeline so that, it indicates that, I had worked on some of those when and how I have upgraded over time.
Maybe don't add them too your skillset but add them as a challenge in your individual project overview.
Alex Ershov
Here is a good example how to put side projects into your resume: The Complete Guide Of Full Stack Resume Writing. Good luck!