Skip to content

Comment on Free solo coder – Programming without safety equipment

Comments

At the end chapter:

The best example of explaining what I want is giving an example of what I really bugs me. Go throws an error whenever you have an unused variable.

This is really a idiosyncracy of Go, unrelated to safety, and comes I guess from the Rob Pike attributed dogmatic stance "We made a deliberate decision: no warnings. If it's worth complaining about, it's worth fixing."

Yeah true, it's not the best example, and completely unrelated to type systems, I agree.

Although warnings in someway are a safety mechanism so I think it could contribute to another section of the article, but it'd be much better to have a different example for that paragraph.

Thanks for the feedback

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.