When I worked on OpenStack for a few years, 80% of the bugs I fixed were type errors that could have been prevented by Python being staticly typed.
This describes literally every python contract job I’ve ever had.
ASM doesn’t care about your variable types, because it doesn’t care about your variables. What’s a variable, anyway? There is only address space.
juniorest of memes
deleted by creator
clearsThroat.shSTATIC TYPING FTW. FIGHT ME, YOU BITCH-MADE INVERTEBRATES.
As long as your byte consists of 8 bits.
Like any newb, the nuance is lost.
Data types don’t matter, the interface matters.
pydantic goes brrrrr!
Elixir and Clojure are awesome languages and don’t need no types. Elixir is getting them though, so you weird static type absolutists can finally look at it soon. I even use Haskell and OCaml and Rust which has stricter types than the languages y’all write in and I never complain about the lack of types in languages.
I’m the guy on the right, typescript devs are in the middle
Lately my approach to dev is “I don’t care about your language feautures, I’m going to treat it like lua and just stuff objects with data and write bare functions to process them”
Unless I need to engineer something complex, everything is dict[any:any].
Cool. Where do you work again? Just so I can make sure never to end up there to clean that shit up.
I’m mostly joking, but most of what I code lately is integrations and data tools where 90% of the thing is configuration and lining up different tools.
It’s a lot of load data form yaml, build json, throw that into a tool and the build a report kind of glue. I’ll use pydantic and stuff where it makes sense, but I’ve been spending a lot of time lately between lua and python and javascript.
I used to do more system and engineering stuff which actually required a lot of planning, but that’s just not what has paid the bills for me the last few years.
Man, I love lua, but after switching to a different job on typescript I feel like lua could only benefit with a similar type system. So many bugs avoided just because I know for a fact what a function returns and expects.
