News for hackers. Stuff that matters.
Re:3 weeks writing code in Go by bsaul on Saturday February 01, 2020 @10:32AM (#22211004)
I agree and in fact i think this sentence is a self-contradiction in some way :

If you want a "big longstanding" project, then doing "complex" thing is probably the thing you want to avoid at all cost. And as a proof that it's possible, one can have a look at the standard library, which is big, longstanding and is the most readable std lib i've ever seen.

Re:3 weeks writing code in Go by weff_ on Sunday February 02, 2020 @12:58AM (#22215408)
So when is it appropriate to do complex things?
Re:3 weeks writing code in Go by sfifs on Sunday February 02, 2020 @01:11AM (#22215458)
HPC where you try to wring the last ounce of performance from machines insufficiently powerful for the task. Weather forecasting, weapons simulation, protein folding...
Re:3 weeks writing code in Go by weff_ on Sunday February 02, 2020 @02:43PM (#22218926)
That's interesting. I don't think as optimized memory manipulation via convoluted casting and such as "complex stuff". I think of that as optimization.

I thought what the author meant by complex was a gigantic system that needs to use many design patterns for good reasons; the code models a very complex, convoluted domain.

Re:3 weeks writing code in Go by bsaul on Sunday February 02, 2020 @05:22PM (#22219868)
When you prototype. But once it reaches production, you should hopefuly have managed to reduce the complexity to its bare minimum