Live data from Hacker News

Sloc Cloc and Code – What Happened on the Way to Faster Cloc

boyter.org

21–23 of 23 posts

Re: Sloc Cloc and Code – What Happened on the Way to Faster Cloc

#21
post #12
post #8

Earlier quoted context omitted.

Number of characters is a meaningless metric because it depends on identifier lengths, which can be very different between coding styles. A much fairer metric would therefor be the number of lexer tokens in my opinion.

Number of "words of code"?

I guess you could call it that.

Re: Sloc Cloc and Code – What Happened on the Way to Faster Cloc

#22
post #19
post #4

Earlier quoted context omitted.

Depending on what you are working on you can pre-allocate everything you need and then turn the GC off. You can even do it in code which is nice. Similar approach to Java.

How?

You can control it through an environment variable or through code https://golang.org/pkg/runtime/debug/#SetGCPercent

Re: Sloc Cloc and Code – What Happened on the Way to Faster Cloc

#23
post #11

well the cost estimate is a little bit funny. Probably inaccurate :D > Estimated Schedule Effort 25.879043 months > Estimated People Required 18.118657 Well I'm working alone on the project for 4 years...

Certainly could do with some tweaking. Its based on the simplified COCOMO model. Its entirely possible I made a mistake in there.
Post reply on HN