Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics.
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
I will take a look at Polaris. I started out in C and C++ years ago, so I all no stranger to strong typing. The Python devs have realized that there needs to be ways to add strong typing, so you can now explicitly type inputs and outputs to functions, which helps a lot. Also, there are places where other companies have implemented things in Python, so you are somewhat pigeonholed into using Python or reverting back to the C++ SDK for them, which can be a nightmare in its own right. Lucky for me I am the only one really touching the code I am working on and it is all bespoke, but someone will need to maintain it later so I have been taking to the strong typing in my recent work.
I will have to take a look at Rust some more and see how it feels. Thanks for the analysis.
If you're familiar with C++ and C, Rust should be easy to learn. It's basically just enforcing all the stuff you shouldn't do in C/C++ - double free, too early free (dangling pointers), reading and writing to stuff from two different threads at the same time (data race). And at the same time modernizing the whole experience (actually useful compiler error messages, easy and convenient dependencies that "just work" without having to worry about a build system, in-built test system, etc.)
Ooo, that all sounds kinda sexy. I may have fun.