• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Official Free References Thread

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Well, i suppose i used to be alluding to the task of mixing everything into one post at the terribly high. Specifically:

1) Move the contents of post one to post two and contrariwise.
2) The links to 'General,' 'Programming,' and 'Linux' be removed.
3) underneath every language, produce sub-sections - one points to tutorials whereas the opposite points to any reviews (if available). i actually do not care regarding the reviews, therefore even those is born. i'm simply making an attempt to come back up with a hierarchy that may add up to most of the people.

Again, i'm thinking of constructing this as lean as potential. Overall, we must always merely stick with languages in order that we will [possibly] gather additional community content that is particular to languages. Let American state recognize if you had alternate concepts.
 
Thanks for sharing this information. I am actually searching and reading about these languages. i have got much help from this thread.
 
When you get around to it, I'd recommend:

  • For the Godot game engine (Which is also getting used to make game development tools like Pixelorama and Material Maker), I'd suggest Godot 4 Recipies on the KidsCanCode site as an extension to the first-party documentation (like those O'Reilly '... Cookbook' books) and, if you're accepting "references" in a more "learn how to use the ecosystem" sense, Awesome Godot for a list of other resources.
  • For the Rust programming language, I'd suggest Blessed.rs for an unofficial guide to the recommended choices for extending Rust's intentionally minimal standard library, the Rust Cookbook for a semi-official analogue to those O'Reilly "... Cookbook" books, and, on the most "learn how to use the ecosystem" end of the spectrum, Rust Interop and areweextendingyet for lists of tools and libraries for using Rust to write compiled extensions for other languages, and lib.rs for a third-party frontend to the package repository which is focused on making it as easy as possible to evaluate packages you're considering using.
  • For Django, I'd suggest Django Packages because it's not just an index of reusable components, it also has comparison tables that help you to get up to speed with the ecosystem.
Heck, when Rust was much younger, the most common complaint I saw was that the documentation seemed to either be all beginner stuff or all very advanced and this sort of middle-ground stuff was hard to find.
 
Back
Top