News for hackers. Stuff that matters.
Re:“The days of using untyped languages on non-trivial proje... by slashdev on Friday July 14, 2023 @01:40PM (#36727304)
Regardless of the cycles in the computer industry, I would never consider a dynamically typed language for large projects ever again.

I’ve been there, done that, and worked most of my career in dynamic languages. There’s just better tools available today. There’s no going back for me.

Python with types or TypeScript is as dynamic as I’m willing to go now, and only as a last resort.

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.
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.
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.

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.