News for hackers. Stuff that matters.

A comment on The cost of forsaking C. Parent comment

Re:The cost of forsaking C by StavrosK on Wednesday October 05, 2016 @01:04PM (#12645655)
You're actually talking about typed vs untyped, which isn't so much about C vs Python. Python is slowly acquiring static type checking (and it's working rather well nowadays).
[ Parent | on HN ]
Re:The cost of forsaking C by bluejekyll on Wednesday October 05, 2016 @04:59PM (#12647815)
Yes, I should have been clearer that this wasn't in support of C over Python. I'm commenting on the relative safety of Python and the downstream costs of using it.

C is not typesafe either, and blows up for other reasons at runtime.

[ Parent | on HN ]
Re:The cost of forsaking C by StavrosK on Wednesday October 05, 2016 @06:46PM (#12648619)
Yep, agreed. I'm very excited about the optional type checking in Python, and can't wait for it to improve so I can use it in all my projects.
[ Parent | on HN ]