I actually like the new website. I think the primary barrier to Rust adoption now is something along the lines of "my organization doesn't use it"—this website is clearly geared toward persuading CTOs or administrators. It's a sign of the strength of the Rust community that they feel they no longer need to persuade developers. It implies that many developers have already heard about and are interested in Rust, but ne…
A new look for rust-lang.org
41–50 of 116 posts
Re: A new look for rust-lang.org
#42Re: A new look for rust-lang.org
#43In my (useless) opinion, the old website looks more modern and approachable. I can see immediately what are the benefits of Rust, as well as a code sample. The new site only offers a vague tagline ("The programming language that empowers everyone to become a systems programmer."), which doesn't explain much.
But, in my (useless) opinion, the green is... "bold", and that part isn't very modern or approachable
Re: A new look for rust-lang.org
#44Re: A new look for rust-lang.org
#45The new text is a great improvement over previous programming language theory jargon.
Re: A new look for rust-lang.org
#46The one main objection is the new slogan.
> Rust: The programming language that empowers everyone to become a systems programmer.
They claim it better conveys "what you can do with Rust", but in my opinion being a systems programmer is not more descriptive than the previous statement and it can be read as Rust not being a good choice for anything else than traditional systems programming, which is obviously not true.
Additionally, and this is subjective, I perceive an elitist tone, as in somehow all other programmers should aim to become system programmers, a more elevated type of programmer. I get this is not the intention and I repeat it's subjective, but still.
Re: A new look for rust-lang.org
#47Don't make it so hard for people to find the compiler and documentation. You are not going to attract users this way.
Re: A new look for rust-lang.org
#48When looking at the home page, I don't know what "Get started" is going to take me to, but experience with other sites has given me a bad taste with "Get started" buttons. (The content it leads to here is good, though much of it would have been better put on the front page.)
Personally, I think trying to sell the language on the homepage is the wrong goal. I like language examples on the homepage to make a snap judgement about a language. If I can't see an example, I'm going to assume that there is a reason you don't want me to see it.
If I'm unfamiliar with the language, the things I want are:
* A code example
* A listing of properties of the language (e.g. statically typed, compiled, no gc, memory managed at compile time, etc)
* A command to install it
* A link to a tutorial where I can quickly try out the basics
* A link to the documentation so I can get a sense of its quality
* A link to the github page
Re: A new look for rust-lang.org
#49In general I like the approach of the beta website, though I prefer the very simple visual style of the current one. The one main objection is the new slogan. > Rust: The programming language that empowers everyone to become a systems programmer. They claim it better conveys "what you can do with Rust", but in my opinion being a systems programmer is not more descriptive than the previous statement and it can be read…
Re: A new look for rust-lang.org
#50It was a challenging exercise and so can relate to Rust's community efforts to the redesign. I wanted to offer some perspectives of what Rust's challenges must be.
1. It is really hard to capture the value proposition for a programming language. While working through Ballerina, there is a hard balance between a) describing the language design, b) explaining why language elements are valuable, c) describe the key types of programming workloads that most benefit from your language philosophy, d) direct those interested to learn more to the right information, efficiently.
2. As such, whomever is leading the Rust site evolution over the years shows a real touch and depth for messaging. It takes a lot of insight and careful observation to your community over an extended period of time to tease out which elements are fundamentally what is driving your audience. Having said this, I have a tendency to feel that the messaging in the latest version might be creating a messaging abstraction trying to appeal to a wider developer base vs. the messaging in the current site which is more strongly appealing to existing system developers. Is this a conscious choice of the Rust team?
3. The rust team has figured out, through years of promotion, that the first (and last) question language teams get is always about "who's using the language? how big is the community?". The hardest part about birthing a language is the chicken and egg problem - someone needs to be the first big production app. Dogfooding is really the only way. Rust takes this head on.
I am not a big design person, so don't have an opinion about whether the minimalistic design is better than the new flowing design. A lot of the design influences for ballerina.io came from Go and Rust lang's web site - we are fans! So, I guess you could say that we prefer the minimalism concept.