3 ms·
I think you are reading far too much into their comment. I agree that their comment could have benefited from some elaboration but the simple act of them expres
by subtra3t 3y ago
I think you are reading far too much into their comment. I agree that their comment could have benefited from some elaboration but the simple act of them expressing their opinion (especially one that is not seen in the rest of the thread, as of my writing this comment) is a "helpful contribution to the debate", in my opinion.
- triyambakam 3y agoGiven no other context, it's not very helpful
- seanhunter 3y agoAgree. It also seems a direct contravention of the guidance "Please don't post shallow dismissals.... A good critical comment teaches us something. " https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- lordkrandel 3y agoI didn't know about the guideline, so thank you, even if I disagree with it. A shallow dismissal is anyway a signal you can ignore, but meaningful, especially when people flock and say the opposite. Maybe people don't have definite ideas about things, and just want to say "no" because they feel like, and that's freedom, imho. Anyway I don't use types or type checking, I think that they are the crippling reason why I switched to Python in the first place. There are plenty of typed languages or IDEs that do completion nowadays (which I don't use), but the freedom to completely rearrange the architecture of a program that comes from very loose coupling is not easily traded for compilation time warnings. We've been doing tests because typing blocked us from development, and we just wanted to be able to screw things if we wanted. The company I work for, Odoo, big opensource ERP, also doesn't have types at all. If I wanted types, or a fast language, or "precise interfaces" I would definately rewrite. When I developed in C#, most of the coding time was spent on typing, interfaces, adapters, factories.