Skip to content

Rust birthday post #101

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

Merged
merged 6 commits into from
May 16, 2016
Merged

Conversation

aturon
Copy link
Member

@aturon aturon commented May 16, 2016

usable with a wide range of existing tools; it works out of the box with
[lldb], [gdb], [perf], [valgrind], [callgrind], and many, many more. Our
focus has been to [enrich the experience] for these tools by adding
[Rust-specific hooks][gdb] and [workflows][cargo profile]. Another major
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there are two gdb links

@steveklabnik
Copy link
Member

Looks good here 👍

@sophiajt
Copy link
Contributor

Would love to see more visuals to give it a bit more pop. You mention numbers - could we show graphs? We could also use logos to call out projects that use Rust now.


Second, there's Mozilla. They've long been developing [Servo] as a research
browser engine in Rust, but their first *production* Rust code shipped through a
different vehicle: Firefox. In Firefox 45, without any fanfare, Rust code for
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Firefox needs more emph. It's the punchline of the sentence. Could use "firefox itself" or bold.

@aturon aturon force-pushed the one-year-anniversary branch from 2593594 to c77c2af Compare May 16, 2016 15:14
@aturon
Copy link
Member Author

aturon commented May 16, 2016

Nits addressed.

@aturon aturon force-pushed the one-year-anniversary branch from c77c2af to 3b3eb7d Compare May 16, 2016 15:16
[groundwork for Rust integration]: http://wiki.mozilla.org/Oxidation

In both of these cases, the people involved were hardened C++ devs who knew its
downsides—and Rust's upsides—in their bones. But there's another
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wording here feels awkward and a little confrontational. Could we use something like "In both cases, the people involved were C++ with years of experience and opted to use Rust for its benefits". I know, maybe wordsmith to give it some punch. IMHO main point: Rust stands on its own, we don't need to criticize other tech.

@aturon aturon force-pushed the one-year-anniversary branch from 3b3eb7d to 9b94e47 Compare May 16, 2016 15:19
[more flexible borrowing rules] and [specialization]), [Rust users] by and
large are happy with the core language and prefer the community to focus on
the ecosystem and tooling.
[improved error hanlding], [more flexible borrowing rules] and
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

speling

@aturon aturon force-pushed the one-year-anniversary branch from d177265 to b407e65 Compare May 16, 2016 15:36
[lalrpop]: http://smallcultfollowing.com/babysteps/blog/2015/09/14/lalrpop/
[html5ever]: https://kmcallister.github.io/talks/rust/2014-rust-macros/slides.html

- **Platforms and targets**. Rust's footprint is not much bigger than C's, which
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rust has feet? ;) May want to say "Rust's memory footprint..."

@aturon aturon force-pushed the one-year-anniversary branch from 774b816 to f4dc642 Compare May 16, 2016 16:02
@aturon
Copy link
Member Author

aturon commented May 16, 2016

If folks want to take another look -- been wordsmithing with the help of @jonathandturner, and also added some cupcakes :)

[custom intermediate representation][MIR], which has many other benefits as
well. Another focus has been errors, including
[detailed explanations of most errors][error index], and ongoing work to
[improve the clarity and focus of errors][error format]. Expect to hear more
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe instead of "improve the clarity and focus of errors", can we say something like "improve the 'at a glance' readability of errors" or something like that? Clarity and focus is helpful, but our goal is on the developer understanding the error as fast as possible.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I bet there's some language that Elm pioneered that might make sense here.

@steveklabnik steveklabnik merged commit ff18921 into rust-lang:gh-pages May 16, 2016
@steveklabnik
Copy link
Member

Happy birthday! 🍰

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants