Read RustLast summer, I finally decided to start learning Rust. I published my first blog post about Rust in September, I then attended my first Rust conference to learn more about the language, and started three Rust projects on GitHub. I now have more experience about the Rust ecosystem, and I want to share some feedback. The call for community blog posts by the Rust team comes right in time!
Rust 2018
Hopes and dreams for Rust in 2018. Posts 
100 posts were made by the Rust commmunity:
I’ve been working on some rust projects recently and I really really love this language. I’d love it if one day I could get paid just to write rust! Until then, I’ll make do with …
Here’s my late #rust2018 post. I contribute code to a lot of projects in a lot of different languages. I think it’s really important not to think about Rust in isolation, but in the context of the greater open source world. Here area few specific ways I think about this:
Before I address my hopes for Rust in 2018, I thought I'd look back at a year of meet ups that we've organised for London's Rust user group.
This blog post isn’t so much about what I want from the Rust language in 2018, but more about where I see an opportunity for Rust to gain more widespread use in 2018.
I’ll first talk about my opinions about safety as an abstract concept and my experiences with practicing safety in various environments; I’ll then talk about my experiences programming at work in C and Ruby; then I’ll draw upon these to talk about what Rust can currently offer my work and what I believe it still needs in order for it to strengthen its utility and efficacy in our contexts.
Since you asked for blog posts, and I already read many of them that didn't share my concerns, here is my take. # What I did in 2017 (and also a...
I like the concepts behind rust. I haven't had as much chance to use it as I'd like - it isn't one of the approved languages at work, and ...
There’s been a lot written about what can be done to make Rust’s tooling, libraries and infrastructure better for embedded programming, but I’d like to cover a slightly different topic: what can be done to make Rust the language itself safer and easier to use for low-level programming?
When I started with Rust, I was planning on blogging about my experience. As I learned though, I found most of the documentation I needed was in blog posts that, though helpful, would give different suggestions without a hint as to why they solved the problems differently. This is frustrating for someone new because you just want to get your task done and not have to first research a whole other area. I realized that the more valuable route for me would be in improving documentation and tooling to serve as living documentation.
Hi there! I'm Nico, and I've been lurking around these parts for about a year now. I thought I'd give my 2 cents on Rust's 2018 plans. Note: this...
This addition to std could significantly change how people use rust. "Secretly" it requires some advanced features though. impl<T, const C:...
The call for community blog posts has inspired lots of great responses. Most of the things that I feel are important have already been said. This post is a collection of thoughts on what I feel is important for Rust to flourish in the future. It is perhaps a bit late in the process, but it may add some new perspectives.
Note: This is the first blog post that I’ve ever written. Feedback is much appreciated :).
A blog about Rust and embedded stuff
What has gotten really, really good in rust-land as I remember this year:
Rustaceans may already be familiar with Read Rust 2018. Its really awesome to see all blog posts by other people. I’m yet to finish reading all of them :P
Adding to the chain of wishlist and suggestions for Rust’s roadmap for 2018, here’s my Wishlist:
This isn’t something that I would do very often, but a call was made, and I would like to take that chance to fill in some ideas with…
I wanted to write a post laying down my thoughts about Rust for a long time, and it seems like the perfect time to do so. Most of the things I've said have been touched upon recently, and probably more aptly, but here it is nonetheless!
A friend and I are working on adding Rust support to Metaparticle. We did a simple search for “decorators in Rust” and found this repo, which seemed promising. My friend added it, but s…
I have to 100% agree with @nrc's post. I feel like Rust has a lot of great things in the pipeline, but it worries me that there are so many open tracking issues and open issues in general (over 3100 at time of writing).
A lot has been written already about this, so instead I will focus on a few areas of technical debt that I see as particularly high-impact.
This is a response to the #Rust2018 call for blog posts with a little bit of my experience and how I see the 2018 year mo...
I am pretty amazed that the Rust team always tries to get information about Rust usage from its users. Having a great vision is important, but it may not be enough to succeed. It is crucial to convince people to use Rust, and to know how to do that, we must take the perspective of the people who DO NOT use Rust.
Well. Just two "minor" points: 1. Game Development Libraries 2. Rust idomatic GUI Frameworks
Code injection attack is a method of taking advantage of a flaw where an application can be tricked to relay malicious code from a system…
The Libs Team met today to discuss a weighty topic: what is its mission as a team, and are we set up to achieve it?
As team lead, I took the liberty of proposing a mission statement:
To improve the quality of the crate ecosystem, as a product.
Although I’m a rust beginner, I’ve thoroughly enjoyed reading all the Rust 2018 blogposts lately. And as a systems engineer who leans…
At Fortanix, we are big proponents of deterministic security. Designing in security from the get-go by using secure programming principles is a big part of that.
With this post, I would like to give my feedback to the rust community in the
scope of A Call for Community Blogposts. This article is structured in …
Since I'm coming pretty late to the #Rust2018 party, most of the things I wanted to say have already been said! Ashley's kick-off post was kind of a meta-#Rust2018 for me, calling for us to experiment with new ways to get community feedback in Rust. I personally really enjoyed
Rust, in no small way, has captured quite a bit of my imagination in the last 4 and a half years. The language and community has a lot of…
There are plenty of exciting language features which should land in 2018, I'd love to see further reductions in compile times, and there are a lot...
*ring ring*
Recently there was a call for community blog posts themed about ideas and expectation for Rust in the coming year. I definitely can't count myself as part of community yet as my experience with Rust so far has been purely about experimenting and research but it feels like a great opportunity to share my thoughts so far.
Rust in 2018: it's way easier to use!
While I’ve been thoroughly enjoying the Rust community’s spirited #Rust2018 blog-fest, I wasn’t really thinking of participating myself until Julia Evans pointed out the leadership wants to hear from everyone—even if I might not have anything especially new to add. So here’s my little wish list for Rust in 2018. Since I’m not in Rust’s leadership, I don’t have to worry about synthesizing some grand narrative for the whole of Rust. So I’ll just focus on a few things that would be personally useful to me. In particular, I’ll stick to topics that would be helpful for my Neon project, a set of bindings for writing native Node extension modules in Rust.
I recently picked up an embedded project that I hadn't touched for a few months, so I could add some new features. I was disappointed to not...
Never Slow Down.
This post is my personal retrospective of the libz blitz and my part in it. It's also a loose response to the #Rust2018 call for blog posts and a chance to show off my amazingly poor drawing skills. For the part most relevant to #Rust2018, see the last section.
In a call for blog posts, the Rust community team asked community members to write up their vision for what the Rust community should focus on this year. I've wanted to contribute my thoughts and have been thinking about what to write ever since. I've been able to benefit from the many people who already posted their thoughts to sharpen my own thinking. I came up with 5 categories:
*below post is going to update quite often accordingly* This idea is actually something i got from someone else - "now that Rust is getting...
I appreciate the great community effort being fostered by Mozilla’s Rust team and the cool Rust community outside that have been helpful in…
At the request of the Rust team, the community was tasked with writing blog posts talking about the future and history of rust as it would pertain to improving the language in 2018. I thought I'd take the opportunity to finally begin writing, since it seems like blogging is all the rage nowadays.
As a beginner in rust, it has been the gateway to so many interesting concepts.
Robotics developers face two main problems:
This is my reply to Rusts call for community blog posts.
I’m known for being quite happy with Rust as is. Indeed, my first post on focusing on stable Rust was more than 2 years ago ;).
Also, note that I’ve been interested (and practically involved) in the growing and adoption of programming languages since around 2004, which was when I started doing users support for Ruby in Germany.
Rust is already a fast language, but there are still many opportunities to make it the fast language. While many people will rightfully focus on usability, tooling, and community goals for 2018, I will focus on some exciting changes which will make Rust the star of HPC.
Despite the overwhelming success of the impl period, many of the features tackled are massive undertakings which could not possibly have been polished in suc...
Next for Rust in 2018
First; I have the utmost respect for the fact that I'm mostly sitting here wishing, while other people do the actual work. But since you asked...
Rust in 2018 This short post is a reflection on Rust in 2017 and some ideas I would love to see in 2018 written in the spirit of this blog post. I will keep things brief and try not to repeat what others have already shared. There have been many wonderful ideas that makes me even more enthusiastic about Rust so I hope that I can add to the excitement with a few of my own.
Examining RFC 1303 Add a `let...else` expression
I don’t have a wish list of Rust features that don’t already exist. Rather, I mainly wish that in 2018, Rust committed to certain things that already work in nightly Rust and have worked for a couple of years now.
I initially did not want to write a post with what I want and foresee for Rust in 2018, because I’m already very happy with it! I have spent more than 4 years tinkering with the language, exp…
I don’t have a blog or anything, I just wanted to mention an aspect of rust that could use some love this year - cross compiling. Right now...
About an oportunity for Rust, as part of the #Rust2018 request
A week ago we put out a call for blog posts for what folks think Rust should do in 2018. This is mine. Overall focus I think 2017 was a great year …
I use Rust to write simple computer games as a hobby. I'm not a professional or even an experienced game developer. The reason I picked up Rust is because I wanted something that...
In this post, I want to talk about how we talk about Rust in 2018. I think there are some ways we can change what we’re saying and how we’re saying it. These changes will help Rust be more approachable for beginners and an even nicer place in general.
Instead of fire flowers,this year the Rust Team made a public call for blogposts, asking the community to write posts thatreflect on Rust in 2017 and what they wish for Rust in 2018. What follows are some of the things I personally see as important,and that I’d love to prioritize on in the following months.
Snips engineering team works on shipping vocal assistants to mobile platforms (iOS and android) and a growing diversity of single board…
Since we have this January blogging stream, I would like to talk about using Rust for machine learning. First, I would like to point out, that I...
I can think of many goals for Rust in 2018, but for me at least 2017 went through pretty quickly, so I asked myself the question: If I could...
The call for #Rust2018 blog posts has generated a fantastic set of responses so far, and there’s already an emerging consensus around much of the technical focus for the year. Since I largely agree with what others have said on that front, I want to focus my post on the people side of things: what kind of impact do we want to make on people, both contributors and customers, in 2018?
It was asked that everyone talk about what they want to see happen with Rust in 2018, and I'm sure a lot of folks will be saying a lot of things....
TLDR: Big companies adoption determine the success of the language, not the quality of the language. Let’s target big companies / projects…
I wrote about the ...
In the spirit of the current Rust blog post extravaganza, here are my 2¢ on the most important work to make Rust win big
Why Rust? That was a question I asked exactly two years ago when I started Way Cooler (by the way, happy 2nd birthday Way Cooler!).
A careful reader will note the date of this post; it’s fundamentally in response to this call for blog posts, with a rhetorical device of looking backwards as if my personal plans for Rust came true. If you’re reading this in 2019 or beyond, this... | Steve Klabnik | “The most violent element in society is ignorance.” - Emma Goldman
The Rust project has requested blog posts about the project’s goals for 2018. I found myself in pretty much complete agreement with Nick Cameron’s post, so I thought instead I would write about my own personal goals for Rust in 2018. I am fortunate enough to work on Rust full-time; modulated by the work that needs to get done to accomplish larger team goals, these are some things that I’m individually very motivated to make progress on in 2018.
As part of #Rust2018, I thought I would try to writeup my own (current) perspective. I’ll try to keep things brief. First and foremost, I think that this yea...
There’s a call for the community to write what they’d like to see in Rust in the following year. So, here it goes. And yes, this is a bit personal, what I would like to see in Rust ‒ I fully respect that others have different needs and that not my every wish need to be granted, because someone else will have a better idea for sure.
In December, Mozilla Brazil in partnership with the Rust Lang BR community launched a project that brings together Rust programmers and community leaders from regions all over Brazil to advance ...
My 2 cents: Totally agree with people who say we need an "impl year", but also I would love to see wasm become a first class platform. I think...
Rust is a fantastic programming language, but I believe that adoption is held back largely due to a reputation for being difficult to learn. Let's fix that....
First a few words about me. I was and still am a student, and most of my coding is for learning and because it is fun. Also, coding is a great excuse for procrastinating something more important :). Having contributed to open source codebases has helped me determine that I want to do this in a day job once I'm done with my studies.
A Year Of Rust
My wish for Rust in 2018 is a nice and convenient web service framework that runs on stable rust and gets maintenance and regular updates for many years to come. My intent for 2018 is to continue to maintain and improve ructe (and rsass), and try to integrate it with the best such framework i can find.
I want 2018 to be boring. I don't want it to be slow, I want lots of work to happen, but I want it to be 'boring' work. We got lots of big new things in 2017 and it felt...
In this post I share a few small thoughts on what Rust should do in 2018, and more broadly about the current direction of the language. Tooling A …
#Rust2018 blog post
Reflecting on Rust in 2017 and what might be worth focussing on in 2018.
A blog about programming and stuff. I'm in love with Rust, so most of my programming related posts are about that language.
The Rust project is soliciting wishlists for 2018. Rather than list big things that everybody wants like NLL or a more stable tokio, I’m going to list some things that I think are small and could be...
I’m generally terrible at big-picture planning, so instead I’d like to talk about what I want to accomplish in the Rust world in 2018. Whether this slots into anyone else’s planning is another matter, but I’ll leave that as an exercise for the reader.
Per the call for blog posts, I’ve got thoughts and ideas on where Rust can go in the upcoming year. My wants haven’t changed much over the last year or so: give me non-embarassing compilation speed! 😁
Before getting started, I’m very appreciative of the hard work put into the overall Rust community and ecosystem, including the behind-the-scenes work. It’s difficult to understate just how much time and energy people volunteer in pursuit of a better, Rust-ier world.
With the call for #Rust2018 blog posts on how this year’s roadmap should look, I figured I’d chime in with a few items. Now, I’m not using Rust in any shape or form in my day-to-day life (though I’d like to!), but I follow along with the community because so many exciting things happen, and I find Rust itself to be a breath of fresh air. In other words, my view is shaped mostly by my role as observer (rather than active participant), and the primary need I want to address is to make it easier to convince coworkers and higher-ups to give Rust a shot.
The past few years, I’ve been lucky to be part of the Rust community survey process. In 2016, this data helped show the need to improve usability. We had good foundations, but they were too hard to get at. In 2017, we saw a renewed need to reach out to companies, to improve documentation, and a continued importance of pushing to making Rust more usable.
This past year I was pretty well a full-time Rust developer working on a handful of key projects: postmates/cernan postmates/hopper postmates/quantiles Each of these saw a non-trivial amount of work poured into them by myself and others. I wrote some – but not enough – about the work that
I am excited about Rust after spending a little time with it last year. Here are my thoughts on how it can improve in 2018.
Inspired by the Call for Community Blogposts I want to summarize my experiences and thoughts on Rust in 2017 and what I am excited about for 2018.
Reflecting 2017 2017 was an amazing year for Rust. We got 8 releases of rust itself! We got basic procedural macros allowing custom derive (also known as “macros 1.1”) in the first release last year (1.15.0). This made serde 1.0 possible, if I’m not mistaken?
Recently, the Rust teams put out a call for community thoughts on what Rust’s 2018 goals shouldbe, andwe’d like to weigh in from our perspective as a Rust-fo...
κeenです。New Year’s Rust: A Call for Community Blogpostsの一環のつもりです。 恐らく英語の記事が望まれてるんだろうなと思いつつも試しに日本から声を上げてみます。 私はRustは1.0前後の頃から触っていて、ドキュメントの翻訳をしたりここ1年くらいはIdein Inc.での業務でも使っています。
1年ほど使ってみて何が足りないか考えてみます。
blog post on thoughts for rust 2018
Backward stepping Most debuggers provide the following commands: Step into the next function (reaching its beginning-point) Hop over the next function call Jump to the end of the current function R…
Note: This post is not only about Rust, but rather my experiences, problems and solutions throughout 2017.
A response to Rust’s Call for Community Blogposts #Rust2018
Starting today and running until the end of January we’d like to ask the community to write blogposts reflecting on Rust in 2017 and proposing goals and directions for Rust in 2018.
For me it's also a chance to do a review of the year 2017. Most of it I spend on a Rust implementation of PBRT (beside working for The Mill and making sure we can deliver our moving images, rendered most of the time with Arnold).