“The days of using untyped languages on non-trivial projects are over.”

Re:“The days of using untyped languages on non-trivial proje... by happymellon on Saturday July 15, 2023 @10:13AM (#36736945)

I've personally found that Python with types is just not quite enough if I have to work with other people.

[ Parent | on HN ]

Re:“The days of using untyped languages on non-trivial proje... by slashdev on Saturday July 15, 2023 @10:54AM (#36737334)

I’ve also found it insufficient. I’d much rather have a stronger type system.

[ Parent | on HN ]

Re:“The days of using untyped languages on non-trivial proje... by lisasays on Saturday July 15, 2023 @02:00PM (#36739412)

Yup, it can really suck, this working other people thing.

But can you elaborate or provide some examples, please? I'd like to know more about this angle.

[ Parent | on HN ]

Re:“The days of using untyped languages on non-trivial proje... by wryanzimmerman on Sunday July 16, 2023 @01:32PM (#36749519)

My guess is he’s referring to the way that types are fundamentally optional no-op statements in python, and therefore the level of “typing” in a given project is necessarily opinion-driven and can only be enforced through building up a lot of tooling, like making sure a type checker passes or fails all code going into deployment or CI. And even in the best case, types are duct-taped on, so there is no such thing as “perfectly type-safe”

So as soon as you have two developers on one project, you have two different opinions about it.

[ Parent | on HN ]