this post was submitted on 03 Sep 2023
15 points (94.1% liked)
Book Recommendations
187 readers
1 users here now
A community dedicated to recommending books, both new and old.
Please follow this instances rules.
To find more communities on this instance, go to: !411@literature.cafe
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
The goal isn't to make things a fully automated whitelist, it's more so a list of instances that cause issues or are suspected as spam that would be blocked. Even then, instances see the info and are given the opportunity to do what they want with the info as they see fit.
It really takes a lot to get fediblocked as a small user instance.
I fully understand your anxiety on the matter, and this is a critique I have actually had directly with the software. I did get into it a bit with db0 (sorry man!) over it, and thankfully my critiques were listened to and the reasoning behind the software itselfs overall use was clarified.
The goal isn't a glorified whitelist, but rather a crowdsourced tool that people can use what they want with it. You can automate the blocks if you want, you can make it so that there's warnings when blocks are made, you can impliment a whitelist if you want, it's really on people who use it. The only somewhat automated aspect of it that's by default is the identification of instances with spam like behavior, and there is steps to rectify that if they are identified as such so it's not like a permanent mark of shame.
I participate in these conversations of fediseers tooling and development with single user/small instances in mind, so know that as tools are being made I am making sure others are mindful of how it may affect small single user instances/new niche communities. I will continue entering those conversations with those communities in mind as well. I gotchu.
Nah, i dont think that's true at all. Priority number 1 is learn the language that deals in what you're most interested in. Priority 2 is learning the language whose ecosystem you can tolerate.
Why? Because you learn most when you enjoy what you're doing.
I'm interested in performance and systems programming so i tried to start with c++. C++'s ecosystem and tooling are complete garbage and i spent more time fighting it than learning to program. I learned python for a specific project, but eventually started learning rust because i was frustrated with python's lack of low level functionality (and speed).
Rust has a lot of modern features that c++ doesnt (and that arent buried behind 20 years of "do this, no wait that's bad, actually do this instead"). The tooling is excellent for beginners, and there's lots of core and standard library features that simplify some of the stupid things about low level programming. And you dont have to start with all the low level fiddly bits, you can start with variables, conditionals, and functions just like you would in python or whatever.
As for book recommendations:
NOT the official rust book. Imo it assumes you already know at least one other programming language. It doesnt always go into enough detail about advanced concepts, but other times goes into WAY too much detail for true programming beginners.
The two that i liked the most were:
Programming Rust by Blandy, Orendorff, and Tindall
Rust in Action by Tim McNamara
I've also heard good things about Command-Line Rust by Ken Youens-Clark, but i havent read it myself.
Also, dont be afraid to read language-agnostic books that cover general computer science concepts like Dive Into Algorithms, Understanding The Machine or Data Structures The Fun Way after you've gotten your feet wet.