@aral @katzenberger @mmstick in that case, I was referring to the statement here https://mastodon.ar.al/@aral/112638007852850343 so you're quoted correctly
Notices by ragectl (ragectl@hachyderm.io)
-
Embed this notice
ragectl (ragectl@hachyderm.io)'s status on Friday, 21-Jun-2024 15:25:00 JST ragectl -
Embed this notice
ragectl (ragectl@hachyderm.io)'s status on Friday, 21-Jun-2024 15:24:59 JST ragectl @aral @katzenberger @mmstick so now that we've clarified that you're not just talking about IBM and Canonical
In conversation from gnusocial.jp permalink -
Embed this notice
ragectl (ragectl@hachyderm.io)'s status on Friday, 21-Jun-2024 15:11:43 JST ragectl @katzenberger @mmstick @aral every linux distribution? is that blanket enough?
In conversation from hachyderm.io permalink -
Embed this notice
ragectl (ragectl@hachyderm.io)'s status on Wednesday, 27-Dec-2023 14:24:21 JST ragectl @inthehands @finestructure the comments in the videos were just in agreement with the idea that if your tests are only really trying to validate data types, you should be looking to move that code to a statically typed language. In context, the videos were talking about how python frameworks wrap C/C++/Rust code for the speed of core functions.
In conversation from hachyderm.io permalink -
Embed this notice
ragectl (ragectl@hachyderm.io)'s status on Wednesday, 27-Dec-2023 08:53:55 JST ragectl @finestructure @inthehands I was watching some videos on Python and Rust, and they both had the same message about data types.
One said not to bother with type hints in Python because that wasn't the point of writing in Python to begin with
In conversation from hachyderm.io permalink