-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call for articles #5
Comments
I'm quite excited to see how this project will work out and I've already read #4 and honestly love the idea of the magazine being a complement for TWIR. I'd like to contribute with my little grain of sand but since I'm not a seasoned Rustacean I'm curious about the requirements to be part of this |
Hi, @alejandro0619. Glad you like the magazine. Everyone starts from a newbie, don't hesitate to submit your article if you think your article is valuable to the community. Whether you are a seasoned Rustacean or just getting started with the language, we hope you will join us on this exciting journey. |
Would you be interested in language-intro articles like this? This is an ongoing series that is focused on the understanding/whys of the key language features. https://eagr.dev/2023/01/14/understanding-rust-ownership.html |
I like this article! and have learnt some things from it, so it could be a nice idea but maybe not starting at the very beginning because if you hadn't heard of Rust you perhaps wouldn't be reading the newsletter @eagr ? So probably starting from someone who has just made the decision to learn Rust or is strongly considering learning Rust. I think it would be good to appeal to different levels |
I'm not sure if get the idea as a whole. I take it as a No? Would you mind explaining what you meant by "not starting at the very beginning"? Let me just take a wild guess. Yeah, the post probably wouldn't be a good intro. The Rust book has already done a great job at covering the basics and getting people started. Why do another one right? But still, the content is entry-level stuff and very few assumptions have been made. Clarification: Post's intended for people who have dabbled in the language and want to dig deeper into the rationales behind the language features. |
Well really I meant yes from my point of view as long as it didn't start as if someone had never heard of Rust like "Rust is a high-performance, statically-typed programming language with the main focus on safety and performance". Does that seem to make sense ok? I liked the other article and the dabbling plan |
Oh, I see what you're referring to. It makes sense, and yes that opening could be annoying. I felt, at least in the context of that post, "high-performance" and "safety" were a bit underspecified that it might need to elaborate on for thorough understanding. And not everyone is appreciating Rust as a safer C/C++ alternative as it should be. That said, I agree that it can be rewritten better, at least for the purpose of the magazine. How would you suggest that I address the opening issue? |
At Rust magazine, our goal is to provide a platform for the Rust community to share their knowledge, experiences, and insights on using the language. Our magazine will feature articles from experts and enthusiasts on a wide range of topics, including best practices, new features, and real-world examples of Rust in action.
In addition to articles, Rust magazine will also include tutorials, interviews, and other content to help readers stay up-to-date on the latest developments in the Rust world. We will also be highlighting notable projects and communities within the Rust ecosystem.
We are thrilled to be launching Rust magazine and look forward to providing a valuable resource for the Rust community. Whether you are a seasoned Rustacean or just getting started with the language, we hope you will join us on this exciting journey.
The text was updated successfully, but these errors were encountered: