{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Emotional °昔 的问题《What's the golden code/comment ratio? [closed]》','https://www.manongdao.com/q-1235158.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Is there a code/comment ratio that you consider to be a sign of good (bad) code health?
Can you give examples of open source projects that are considered to be well coded and their respective comment ratio?
(I realize that no ratio is "true" for every project and there may very well be crappy projects that exhibit this theoretical golden ratio. Still...)
I try to keep comments at a minimum. Code should be self explainetory and while source code tends to change the comments almost always remain behind as a wrong explaination.
There is no such thing as a good comment to code ratio. In the old days some people believed that you needed to have a comment at the head of every function explaining what it does.
However, with the advent of modern languages code is pretty much self documenting. This means that the only reasons left to put a comment in the code is to either explain where an oddball decision came from or to help with understanding a really complicated subject.