prev.rust-lang.org

For Rust, Chucklefish has written rust for all the current generation of consoles: https://github.com/rust-lang/prev.rust-lang.org/blob/master/... There are other game companies doing stuff, but we have less details including platform: EA’s SEED division, Ready At Dawn, and Embark (some ex-SEED devs making a new studio where Rust is the primary language.)

They already have done so for some of it! https://github.com/rust-lang/rust-www/pull/853

- User doesn't like the fact that buildbot (which they think is maintained by mozilla) uses "master/slave" terminology https://github.com/rust-lang/rust-buildbot/issues/2 . Mozilla gives buildbot $15k for changing it https://blog.mozilla.org/blog/2015/12/10/mozilla-open-source... - User doesn't like that dining philosophers is cited with some male and/or gender-neutral pronouns and placeholders (even though the original exposition was already changed to female pronouns) -- proceeds to change the rest of the pronouns to female (I guess gender-neutral didn't make sense) https://github.com/rust-lang/rust/pull/25640 - User thinks "bad code style" is offensive https://github.com/rust-lang/rust/issues/41646 - User doesn't like brotli encoding type being called "bro" https://bugzilla.mozilla.org/show_bug.cgi?id=366559#c147 - User thinks that th

https://github.com/rust-lang/rust-www/pull/685#issuecomment-... Not too sure of the segfaults bit, feel free to put in your thoughts on that PR

I disagree with the segfaults bit (which is what you had been focusing on so far, and which is what I've been arguing against) but yeah, "guarantees thread safety" is iffy. The wikipedia definition is pretty vague, it relies on a concept of "safe" that isn't defined there. It's acceptable to say that "data race safety" is "thread safety", though confusing. Rust's homepage does clarify what it means in the bullet points below that statement, so I wouldn't call this a lie. It may be misleading though, and this is a common misunderstanding as steve mentioned, so I submitted a PR to fix it https://github.com/rust-lang/rust-www/pull/685

I don't think a compressed video with 4 times as many pixels will be 4 times as large. Consider you already have one pixel of each 2x2 pixel group, then you can predict very good how the other pixels are looking, so you don't need as much data anymore. The same holds true for images/graphics. Take a look at the (blk) rust logo at several different sizes: https://github.com/rust-lang/rust-www/tree/master/logos 16x16: 351 Bytes; 32x32: 691 Bytes, factor 1.97 from 16x16; 64x64: 1.41 KB, factor 2.04; 128x128: 3.4 KB, factor 2.41; 256x256: 7.29 KB, factor 2.14; 512x512: 10.9 KB, factor 1.50 So it certainly can both hold true that 4K HEVC encoded video has the same bitrate as 1080p AVC encoded video and that it has 50% savings.

Edit: Rust's website has an open-source license[3]. You can copy the code and use it directly! That's great news because they host it on S3 with Jekyll, which is ridiculously inexpensive. I'm not an expert or a designer. Your users will show you how to improve the design because you'll see evidence of where they're getting tripped up. For example, if a certain page is the last one most people see before leaving the site (other than front page), then you can tell that page A) solves a problem, or B) causes people to lose interest. A good starting point is to look at other language sites and decide which ones seem friendliest and least friction-y. How easy it is to get started? As examples, I really like Rust's website[1], and Elm[2] is pretty good, too. Rust's site is great because it's readable, all the important stuff is above the fold,

Hello everyone, As part of the current push to improve the Rust website [1], we are seeking input on what to include in the new and improved Frequently Asked Questions page [2]. If you have questions about Rust, suggestions for concepts that should be clarified via the FAQ, or any other ideas related to this issue, feel free to share them here. More specifically: - What questions do you or have you had about Rust? - What problems have you encountered during your experiences programming in Rust? - What topics or concepts in Rust do you feel deserve clarification? - Do you have any other ideas or comments about what the Frequently Asked Questions page on the Rust website should include? Thanks for any and all input you can offer! Each answer helps make the Rust learning experience better. [1]: https://github.com/rust-lang/rust-www/labels/RW

Thanks! https://github.com/rust-lang/rust-www/pull/64 submitted.