19
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Sep 2024
19 points (95.2% liked)
chat
8174 readers
537 users here now
Chat is a text only community for casual conversation, please keep shitposting to the absolute minimum. This is intended to be a separate space from c/chapotraphouse or the daily megathread. Chat does this by being a long-form community where topics will remain from day to day unlike the megathread, and it is distinct from c/chapotraphouse in that we ask you to engage in this community in a genuine way. Please keep shitposting, bits, and irony to a minimum.
As with all communities posts need to abide by the code of conduct, additionally moderators will remove any posts or comments deemed to be inappropriate.
Thank you and happy chatting!
founded 3 years ago
MODERATORS
SPSS and SAS are atrocious. For a weakly typed programming, I'll reach for some well-known python packages.
I'm slightly wary of weak typing nowadays tho. I've seen at least two times where weak typing lead to processes not throwing exceptions and producing slightly weird results in huge data sets. I'm probably biased against R because these happened to be R lang processes. Both were not detrimental, fucked up optimal pircing in vampiric industries (like self-storage). Of processes I've inherited though, good tests and artifact validation (that have worked and caught things) were more commonly written in Python.
Is there anything especially good that's strongly typed? Spark is fine, but I'm one of 5 people I've ever encountered who's actually using the typed dataset APIs or leaning into type safety as a feature, and doing so puts me at odds with basically every book anyone learning Spark is likely to read.
Python is strongly typed. It's also dynamically typed
That's different than weak typing
The qualifier "especially good" excludes Python. Static typing would be preferred, but not required.
I really like kotlin
I'm already writing Scala, Kotlin feels like it'd be a lateral or even negative move. ๐ I'd be curious to see what some nontrivial Spark in Kotlin looks like, though.
Yeah, I don't think you'd have much to gain moving to kotlin