11 ms·
A new look for rust-lang.org
- mjw1007 8y agoA personal opinion: The old site said to me "Here's a programming language made by programmers for programmers.". The new site says to me "Here's a programming language which has a marketing team.". The "Featuring" bullet list was an excellent way of calling out what makes Rust distinctive, and I felt I could trust what it said to be basically true. But claims like "empowers everyone to become a systems programmer" or "Rust has great documentation", coming from the language's own designers, convey little information: they might be an over-optimistic view. (Or, in the language of the blog post: I trust them to tell me what a fireflower is. I'd rather judge for myself whether I believe that it will turn me into Fire Mario.)
- ajkjk 8y agoI strongly agree. The list of features on the old list is very meaningful to a C programmer who will recognize all of those things as things would love to use every day. Its underlying message is "we're technical nerds and we made a thing that you'll like". The new version is corporate-speak that won't appeal to.. anyone? Its underlying message is "we're trying to get you to like us and we studied how to do this". But, like, what's the point of a programming language's website anyway? Most people who visit the site will probably be at least vaguely aware of it. You use it if recommendations online, code samples, etc are compelling, and if the early adoption story (examples and motivations) are compelling. All I ever want is a list of examples up front and center. The more words I have to get through that aren't literal actual examples that show both what the language looks like and what differentiates it... the more exhausting the whole experience.
- rhn_mk1 8y agoI totally agree. As a coder, whenever I visit a website of a project I'm interested in, I'm looking for key technical features to convince me it's the right tool for the job, or that it offers an unique property tht I never even thought about. That's usually conveyed in a list of bullet points, and a couple of examples. I can rarely find it though. I wasn't quite able to grasp why, and I kind of accepted this as how it is. But after seeing the two revisions side by side, I finally get it! The important, unique information found in the old version. The majority of project web sites are closer to the new version, which hides the complexity behind colorful "screens" and headlines which are short, friendly, distracting, and very, very bland, delivering the same "simplicity, performance, productivity" message regardless of the project. Can you guess what Docker does (or does especially well) just based on the website? [0] I've learned to cut the crap and go straight to the "about" page to understand the distinct advantages in a more condensed form, but that seems to be missing from the redesign. [0] https://www.docker.com/ https://www.docker.com/
- throwawaylolx 8y ago>As a coder Obviously the website is no longer targeted at coders: the Rust Team seems to target managers to push adoption. To me, it looks like a corporation that has to report user growth every quarter, so they start employing harmful UX to desperately try to push the numbers up.
- peterkelly 8y agoI often find myself going to the Wikipedia page of a project to find out what it really is because the project's own website fails to do so.
- deleted 8y ago[deleted]
- anoncake 8y agoWhatever Docker is, it's Windows-only. Apparently.
- ttsda 8y agoThe point of the old website was convincing developers to use Rust. It seems the point of the new one is convincing the higher ups to let their developers use Rust.
- speedplane 8y agoI have been using Google Cloud for many years now. I used it because I thought it was technically superior than AWS and several others. However, for years, many mocked it as a second-tier cloud provider that wasn't "serious". Then Google brought on Diane Green. As a technical nerd, I wasn't too pleased. Their nerdy How-To articles morphed into Enterprise Success Stories. It was irritating, but it also raised Google-Cloud to a "serious" cloud provider. Even though Rust's marketing pivot will likely irritate many, it's likely better for it long term.
- ttsda 8y agoAgreed. As much as I liked the old site I think the rust team made the right call on this one. Perhaps the old page could be moved somewhere close to the language docs instead of being removed, but I'm confident whoever is in charge has given this much more thought than I could ever give (as well as most of the commenters here).
- speedplane 8y agoInterestingly, Diane Green just left Google Cloud, under somewhat unclear circumstances. It's possible that she did her job, "mission accomplished", it's possible that she did not do it well enough to attract big enterprise clients, but the most satisfying reason (albeit least likely), is that the Google decided to focus back on the technology and less on enticing Enterprise clients with laminated corporate-speak marketing. So even though this is probably the right move for Rust, it would behoove them to keep a section of their site/blog/newslettter/slack channel/etc for the nerds to get together working on what they love.
- geodel 8y agoYou are right. Previously it was hackers, now it seems for growth hackers.
- peapicker 8y agoIf it empowered everyone, it would be available on other OSes than Linux, Windows, and macos (ok, it is available on Android and iOS apparently and some *BSD variants too). I'd love to use Rust - but my business requires support for, (in addition to Linux and Windows), Solaris, AIX, HP-UX, and OS400 for me to serve my customer base. Rust can't empower me there, it simply isn't available.
- steveklabnik 8y agoThere are people working on it! Debian is now shipping 14 architectures. The big show-stopper is if LLVM has support for a particular bit of hardware. OSes are easier. We need people who know these systems to help out. It's not easy, but we'll get there.
- deogeo 8y agoThe old site was pleasantly minimal, easy to find the important things at a glance, and fit everything into a single screen. The new one overloads you with bright, ever changing colors and useless marketing, while hiding important stuff like language documentation into a tiny link at the very bottom, next to the site terms and conditions. It is dazzle camouflage [0] for information. [0] https://en.wikipedia.org/wiki/Dazzle_camouflage https://en.wikipedia.org/wiki/Dazzle_camouflage
- HereBeBeasties 8y agoThe existing site's "rust by example" is extremely valuable. It's up front and centre. In the new site it's very buried, which is a shame. Much easier to get started, perhaps, but much less easy to see whether I'd want to in the first place. The getting started stuff is good, though.
- ipsum2 8y agoIn 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.
- alain_gilbert 8y agoI share the same (useless) opinion.
- jszymborski 8y agoThe lack of code on the landing or "learn" page is not great in my similarly useless opinion.
- gaigepr 8y agoI have a similar useless opinion. I liked the old website for its clarity and simplicity.
- jamescostian 8y agoIn my (useful(?)) opinion, the code sample didn't really illustrate the nice things about rust. I do like the bulleted list from the old website, but I find the new website more modern and approachable (especially with all the big headings and smaller text that drills down into the details). Maybe they wanted to give users a more focused view on the biggest selling points, rather than show some generic-looking code and several bullet points that noobs might not understand? But, in my (useless) opinion, the green is... "bold", and that part isn't very modern or approachable
- TylerE 8y ago"empowers" is such a bullshit word.
- alexandernst 8y agoI guess that's the result when a Rust developer does the job of a Web dev.
- revskill 8y agoIs it a compliment ?
- nixpulvis 8y agoI don't hate it, but I do miss the similarity the old site had to the rest of the ecosystems documentation. I'm glad to see more information added though.
- tphan 8y agoTabbing through the page is kinda annoying because they've set outline: 0 on all the buttons.
- steveklabnik 8y agoCould you file a bug please?
- knrz 8y agoGenuinely curious about any opinions on how to handle this. I've personally set outline: 0 because I can't stand the blue glow that Chrome puts on. Is there a way to have good keyboard support & have it look good?
- unethical_ban 8y agoI'm not a huge fan, but it's not bad. Some Rust sponsors have their big logos on there, and the Rust Book (the real documentation) is at the very bottom of the page.
- deleted 8y ago[deleted]
- RcouF1uZ4gsC 8y agoThis website seems like they are targeting CEO and CTO's. The website looks very much like a business website trying to get corporations to sign up. The old website felt it was targeting programmers with it's code sample that you could modify and run directly on the web page.
- Siilwyn 8y agoYes exactly! The content targetting "system programmers" is odd as Rust is great for so much more like the examples towards the bottom about webassembly and such. Additionally the website seems to take longer to load.
- gpm 8y agoGenerally LGTM. I loved the playground editor embedded in the old front page. Any chance it can be added to this one as well?
- steveklabnik 8y agoWe loved the code snippets in the abstract, but nobody could come up with good, succinct, representative ones.
- laszlokorte 8y agoThe colors, the fonts and the thick bars behind the headlines are really distracting and most important: example code on the front is missing as well as the clearly stated list of features ("zero-cost abstractions, move semantics, guaranteed memory safety [...]"). The buttons in the "get involved" section should better be labeled "read the book", "watch videos" and "read contribution guide". The z-index of the "Click here to try out the new beta site!" banner on rust-lang.org is wrong when scrolling down.
- laszlokorte 8y agoAnd in my opinion the old white/blue/black color scheme provided a very familiar and simple corporate identity throughout the ecosystem. I don't think those new playful colors will fit the whole ecosystem.
- binarycrusader 8y agoI have to agree, the colors seem very "off" to me, but it seems fine otherwise. In particular, the "fuschia" background color makes for poor readability (at least for me).
- riccardomc 8y agoDoesn't the "small Rust application" at the bottom of the page lack an "extern crate ferris_says;"? I know very little about Rust, but I cannot get the example to work without that...
- steveklabnik 8y agoRust 2018 does not require extern crate anymore (except in certain very limited circumstances); when this page goes live, that will work. Or you can try it out on beta.
- Twisol 8y agoFor those curious (like me), this is described in the upcoming Edition Guide at https://rust-lang-nursery.github.io/edition-guide/rust-2018/module-system/path-clarity.html https://rust-lang-nursery.github.io/edition-guide/rust-2018/... .
- steveklabnik 8y agoAnd the exceptions, yet to be described in the guide: https://github.com/rust-lang-nursery/edition-guide/issues/121 https://github.com/rust-lang-nursery/edition-guide/issues/12...
- federicoponzi 8y agoI think it's beautiful! :)
- whalesalad 8y agoMissed opportunity for some circa-2005 rusty photoshop tutorials in action here. https://photoshopcafe.com/tutorials/rust/rust.htm https://photoshopcafe.com/tutorials/rust/rust.htm
- LandR 8y agoI liked the old site better. It looked like a site about Rust programming language. It had the benefits of the language on it, this new site doesn't look like a site for programmers at all. It now just looks like every other generic looking product page out there. I think if I had come to this new site, and not the old site, I might not have bothered to even try Rust out. The new look is just so 'meh'.
- nathanaldensr 8y agoForm (brand) over function, I guess?
- disillusion 8y agoWarning; I'm going to have a brutally honest opinion here. It's better to start over. With a proper UX design, a proper visual design and a good quality frontend developer. Or at least, as close as you can get. My first few thoughts on the design: The design language doesn't seem to convey anything. Whoever chose that color palette? What are the core principles it's supposed to show you? Elements are severely misaligned all over the place. There is no coherency, composition or vertical rhythm to be found. It has a hodgepodge of font sizes and weights without clear typographic hierarchy. Links are actually missing a hover state. Buttons have a hover state, just don't expect it to be noticeable. Just like the font size on the buttons - those are 12px. We don't have 1280x1024 screens, unless I've somehow traveled back in time to 1999. 16px minimum, please. There is too little breathing room on mobile. It's not actually responsive, it just collapses on a single breakpoint. That breakpoint is also in the wrong place (960px), making it too big on tablet portrait (750px buttons, really?) and too small on desktop (960px max on HD+ screens, even 2.5K screens - really?). It looks like it's made with an off the shelf layout framework without any sort of customization. There's a horrible google calendar embed - why not a simple, integrated solution? There are upscaled(!) PNG logos on there (Chucklefish, Yelp) - why not use a vector file, like decent folk? Those design patterns are barebones, but work reasonable well on the homepage. However, the moment you click through they seem to be (ab)used for anything and everything. Where are the other, less generalized patterns? And why are the patterns not actually designed for mobile as well? Just dumping all the buttons below each other and making them 100% wide does not make for a good user experience. For that matter, why are there not more effective patterns used? Code example could really use an, oh I don't know, inline code example perhaps? Fortunately, almost all links go to external (sub)sites -without warning- so you won't have to look at this for too long. Just a shame everything looks different from each other, even subsites. Where are the loving touches? It doesn't have to be a christmas tree, but a little transitions and effects go a long way. As for the code: A display font is fine, but preloading six (6!) font weights of the body font, just on the homepage? And not even .woff2 or .woff, but huge .ttf files at that! That's about 3MB of fonts. Nice when you're on 3G; you can see the webpage building up. It seems to use utility classes. The responsibility for style composition should be in your stylesheets, never in the HTML. The classes look like some clever backend developer cooked them up: "v-top pl4 pl0-l pt0 pt3-l measure-wide-l mw4 mw5-ns w-100 mw-none ph3 mw8-m mw9-l center f3". There, everybody intelligent will immediately know what it does! If you rely on good will for maintenance, this will limit the amount of developers willing to dig in. Also, there are 4 different CSS files, separated for no apparent reason. Three of which aren't even minified. SVG illustrations should be placed inline. As someone with an enmity for big javascript libraries used in the wrong places, the fact that there's no JS should be wonderful. Except that I'm guessing that's part of the reason those design patterns are so barebones. There's lots more, but let's pick the low hanging fruits first. PS: I prefer this version: https://www.rust-lang.org/en-US/ https://www.rust-lang.org/en-US/ ;-) It might be stamp-sized visually, but it does some things much better.
- shafte 8y agoI 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 need higher-ups to approve using it.
- asauce 8y agoWell said. As a programmer I prefer the old site, however you bring up a good point. The new site is a lot better for people in management to see that Rust is used by other large companies and to not immediately discredit it.
- spacesuitman2 8y agoThen why not make two sites? management.rust-lang.org and rust-lang.org
- androidgirl 8y agoI also appreciate and like the new site. I love the use of color, it's very dynamic and "fun", and the typography is nice in my opinion as well. It's more engaging to me, at least.
- ken 8y agoThe new subtitle "The programming language that empowers everyone to become a systems programmer" is a perfect example of that. Any C programmer can see it's factually false, but it could definitely suggest to a C-level exec that they'll have an easier time hiring in the future if they use this language.
- timwis 8y agoI love it!
- fishtank 8y agoThe colors are great, really comfortable contrast level, and the typeface is easy to read. Fairly tight information density, but low-density layouts are a common complaint with the target audience so I think it strikes a good balance. My compliments to the designer.
- pornel 8y agoThe new text is a great improvement over previous programming language theory jargon.
- boatadventure 8y agoYeah who wants to hear programming language jargon when looking up a programming language
- kiliancs 8y agoIn 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 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.
- Skunkleton 8y agoAlso, systems programming is about so much more than being good a programming in a particular language. Programming in rust doesn't make you understand memory barriers.
- saagarjha 8y ago> Programming in rust doesn't make you understand memory barriers. I'm not a fan of the new website, but it's possible that the intent was to be "with Rust, you don't have to".
- Skunkleton 8y agoI guess it depends on what you mean by systems programming. You absolutely need to understand memory barriers if you are doing operating systems work; no language can spare you from that.
- zzzcpan 8y agoFear of empty space is showing a lot on new website. Also poor contrast, poor font size, poor vertical spacing, buttons as links - all make things very difficult to even just read. Meanings of links and labels are confusing too. Don't make it so hard for people to find the compiler and documentation. You are not going to attract users this way.
- piinbinary 8y agoFeature request: A documentation search bar right at the top on the homepage. As an existing user, that's usually the first thing I want to see. After that, a link to browse the documentation. Then a link to install it. When 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
- steveklabnik 8y agoPart of the issue with that is that our documentation search isn’t unified. It’s gonna take a lot of work for that to happen.
- TylerJewell 8y agoI'm CEO of WSO2 and we are working on a programming language for writing microservices called 'Ballerina', and we host it's community at http://ballerina.io http://ballerina.io. Prior to the first public launch, I pulled 9 of our core community members into an offsite where we developed and implemented the web site. It 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.
- steveklabnik 8y agoJust... thank you. Truly.
- TylerJewell 8y agoKeeping the history of the evolution and the rationale for each iteration was great. It's really good insight into the evolution of the thinking for a passionate community team that is doing its best to communicate why their efforts should be considered by others.
- andrepd 8y agoThey have a clean, effective website. It has a pleasing look, and mostly it's just what a webpage should be, after all: a document. Text, images, an interactive code editor. Some CSS to make it look pleasing and readable. A navbar at the top. It works, it is pleasing to the eye, it communicates what it what it is meant to communicate and links to 4 important sections of the website. Wait, let's throw all that away and develop a vomit-inducing monstrosity, complete with: in-your-face extra-bold title headers, jarring colours and colour changes, overall very large design suitable for tablets and not desktops (which is after all where most of your target audience should be accessing from)... What a complete cock-up. The web design equivalent of painting flames on your car: an immature attempt to look "cool" that turns the thing into an horrendous mess. I can only sincerely ask why why why.
- vtesucks 8y agoI don't want rust cool and popular, I want it well designed.
- steveklabnik 8y agoThese things do not have to be at odds.
- vtesucks 8y agoYour own blog post on Haskell (rightly I think) disagrees.
- steveklabnik 8y agoThe blog post is about choice of priorities, not about some sort of determinism between two extremes.
- keyle 8y agoI agree, as a long time designer and as a prospective user, it's godawfully puke worthy. Classic case of "my nephew can do it with paint shop pro".
- geodel 8y agoOld website looked like made by well meaning technical people who do not have all the time in world to make website with all the latest fads in web design. New one looks like some shady marketing crap put together with off-the-shelf components like bootstrap libs. But it does 'empowers everyone'. May be they can add 'No programer left behind' and we all be happy.
- mwcampbell 8y agoI'm disappointed that the Rust community is moving from open IRC to proprietary Discord. Sure, people think IRC is archaic, but for them, the Discourse-based forum is plenty modern, isn't it? The fact that Discord is proprietary means that people aren't free to use any alternative client they want. This is especially problematic for people who aren't well served by the official client, e.g. blind people.
- steveklabnik 8y agoDiscourse is for async communication, you need both. We love open source, but it’s one of many options to weigh. They’re also a production user of Rust, which is a pro. It’s not that there are no cons, of course... there’s just really no perfect option in this space.
- vtesucks 8y agoI just want to say that if and if not you're the PR guy for rust, you're doing a great job. Rust is a well thought language and while I don't agree with the redesign, I like that you bring the thoughtfulness to the non-language component as well. I enjoy your blog posts. Ps: Your parent comment was opposed to discord not discourse.
- mwcampbell 8y agoI don't think Steve got Discord and Discourse mixed up. I did suggest that people who won't get on IRC could use Discourse instead, but Steve rightly pointed out that they're different. Maybe Gitter instead of Discord? After GitLab acquired Gitter, they open-sourced it.
- steveklabnik 8y agoWe had a bad experience with Gitter, and so decided against it.
- steveklabnik 8y agoMy job is documentation, but I've always advocated for things I work on, believe in, and enjoy. Thanks. (and my sibling is right, they suggested that those who don't like IRC could use Discourse instead.)
- detaro 8y agoThe content changes make a lot of sense (even though I'm not a fan of a screenful of "testimonials"), but the design feels dated, and not in the good way, like a bad kind of pseudo-retro :/
- shmerl 8y agoI like the design of Haxe front page: https://haxe.org https://haxe.org It explains both what it is and how it can be used, with a simple (but not oversimplified) presentation. It has a code sample too. It's better to keep the the code sample on the Rust site as well.
- Insanity 8y agoI prefered the old slogan. It actually told me a bit about the language and made me curious to pick it up. The new slogan does not do that for me. But I might not be their main target - I like programming languages for the code itself and not the applications/domains where I can use it. The website didn't need a redesign either imo, but it is better than the changed slogan.
- IshKebab 8y agoI mean, it's ok. But language sites should have examples of the language on their home page and this removes that in favour of a load of marketing fluff. That is just wrong. I get that you want to say what works well with Rust, but frankly few of these things are unique to Rust. With minimal changes I could turn this page into one advertising C++ or D. It's ok to add the new content but the code example and list of unique features shouldn't have been removed.
- hartror 8y agoLove the new design, it adds a feel to the project that many others lack. Compare it to https://www.python.org/ https://www.python.org/ for example which is perfectly functional but squint and you could be on any page on the internet.
- sciurus 8y agoThe beta site is several times slower to load than the old site. https://www.webpagetest.org/result/181130_4K_96804be61480d159a727823bbf4d1aff/ https://www.webpagetest.org/result/181130_4K_96804be61480d15... https://www.webpagetest.org/result/181130_FK_8e4d67b49b8d2ea9772797f0da039081/ https://www.webpagetest.org/result/181130_FK_8e4d67b49b8d2ea...
- steveklabnik 8y agoYes, we’ve done zero performance work yet. That comes next. There’s no reason this site can’t be super fast.
- amckinlay 8y agoThe new design looks like it was made in Microsoft Word.
- andrewflnr 8y agoRule #1 of useful programming language websites is to have some sample code above the fold. With this design, I'm not sure where I'm even supposed to go to find some. I'm surprised at how decent it looks visually on my phone, despite my disliking the color scheme. But please, you're not selling some amorphous, all-singing, all-dancing enterprise product, you're trying to tell us about a programming language. So tell us about the language.
- hardwaresofton 8y ago> Please file an issue with any feedback you have! We’re also looking for people with abilities of all kinds to help maintain the site, and especially people with design, CSS, and marketing skills. If you’d like to get involved, please email us! Just a reminder that if you've got some time to type out a comment in this thread voicing your dissatisfaction you could type that comment out into a Github issue[0] and become a certified open source contributor(tm)! One of the best things about rust is it's community and it's willingness to change and find better ways to do things. [0]: https://github.com/rust-lang/beta.rust-lang.org/issues/new/choose https://github.com/rust-lang/beta.rust-lang.org/issues/new/c...
- kreutzwj 8y agoI don't see any support for switching human language on the beta site. Having the ability to switch on the page itself helps a lot.
- steveklabnik 8y agoAs we said in the post, that’s because the translations aren’t ready yet. When they are, we’ll make it obvious.
- kreutzwj 8y agoSorry, I must of missed that in the post before looking.
- steveklabnik 8y agoIt’s all good!
- csomar 8y agoI don't like the new beta website. It doesn't feel rusty. It would have been better if they just kept slowly improving the old website.
- xedrac 8y agoI honestly can't look at the page for more than a few seconds without feeling very nauseous. The stark color changes everywhere make it hard to scan the page for relevant information. It feels way too distracting. I really like Guile's front page. It's very easy on the eyes and yet provides a lot of useful information: https://www.gnu.org/software/guile/ https://www.gnu.org/software/guile/
- juststeve 8y agosorry, too much happening on the page for me. not wild about the colour scheme. it looks fresh, but it's a lot of colours all at once sorry.
- juststeve 8y agoless is more for me
- majewsky 8y agoThe one thing that I noticed immediately is that it sends all visitors' data to Google by means of embedding a Google Calendar. I'd like it more if the "Upcoming Events" panel listed the N upcoming events with a link to the Google Calendar, so that users can decide whether to send data to Google servers.
- nachtigall 8y agoThis new site looks really awesome and really got me into why not trying rust the next time I'll write a hundred LOC bash script. Much better than the previous version. I had a Wow effect yesterday on mobile and now seeing it again on desktop, it's till wow! Strange that there are so many negative arguments here. Also really interesting to learn about the fireflower problem - there's some truth in it! Applicable to so many things in live...
- k__ 8y agoHaha, someone read Badass
- anoncake 8y agoThat slogan, with the emphasised "everyone", reads to me like "The systems programming language for idiots".
- rayascott 8y agoI like it, but I would ditch the super heavy fonts. They are needlessly difficult to read. You only have to look at the Governance page to see that you’ve gone a few weights to far with the font choice. https://beta.rust-lang.org/governance https://beta.rust-lang.org/governance