Earlier quoted context omitted.
I think dhh's quote just isn't very good -- of course someone who has so much identity invested in the ecosystem is going to say "I looked around and still nothing is better than ruby!" Well maybe not even of course, not even every "BDL" is as cringingly self-promotional as dhh, some have a bit of humility. i agree it's not a great look. Hopefully the website will keep getting regularly updated and tweaked (software,…
[flagged]
Ruby website redesigned
101–110 of 224 posts
Re: Ruby website redesigned
#102Re: Ruby website redesigned
#103So many Web designers put zero thought into how their page looks when it is not loaded or not scrolled exactly past the trigger. So many sites say "0 happy customers", because someone thought showing incrementing numbers is cool. On this page, it opens up with a "100%" loading indicator, for a site that appears to have no interactivity that would require JS, just to show a pointless animation.
I am sure that the designers had to juggle a massive amount of community input and feedback and I know that this is not easy. Kudos to them for (i) leading with some very apt code examples, (ii) the 4 "whys" and (iii) the multilingual support. Speaking from experience (recently we rebuilt https://raku.org ), I am sure that they will come back and optimize, but tbh this is not the priority with a new site where the hi…
You don't need to "come back and optimize" if you don't start with needing a progress indicator for a "transform: scale" animation to display a single static download link. The number of hits is not relevant.
Neither do you need to do three separate fetch requests for static plain text examples that you then laboriously dump into the DOM by creating dummy elements, putting content in there, then looking up and cloning `code` tags to then dump those code tags on the page.
Re: Ruby website redesigned
#104Re: Ruby website redesigned
#105I like the new design, however, I strongly believe the website could've been optimized further and used much less JS. Opening the website with JS turned off makes the code examples not load and the front page freezes as "0%" loading. What does it do exactly? It just fetches[1] to another part of site and retrieves static text[2] to be displayed. This part could've been kept as part of the html, no need for this artif…
I like instantaneous page loads after the initial first page load, which is what the JS does here. Hard to do so without it.
Re: Ruby website redesigned
#106Earlier quoted context omitted.
> used much less JS The homepage loads 9.7kB of JS. Navigating to every single link in the main nav results in no additional JS being loaded. The site is fine.
This page doesn't need JS. It doesn't need a loading indicator for said JS. It could just be html and css, otherwise unchanged.
Re: Ruby website redesigned
#107Re: Ruby website redesigned
#108Earlier quoted context omitted.
I think dhh's quote just isn't very good -- of course someone who has so much identity invested in the ecosystem is going to say "I looked around and still nothing is better than ruby!" Well maybe not even of course, not even every "BDL" is as cringingly self-promotional as dhh, some have a bit of humility. i agree it's not a great look. Hopefully the website will keep getting regularly updated and tweaked (software,…
[flagged]
Re: Ruby website redesigned
#1091. Code examples are fetched via JS instead of being in the HTML. They're static text - there's zero reason for this.
2. The "0%" loading spinner blocks everything. It's literally just displaying a download button and some text.
3. With JS disabled, you get nothing. A language website should be the poster child for progressive enhancement.
The irony is that Ruby itself has always emphasized developer happiness and doing things "the right way." This site feels like it was built with the modern JS framework mindset rather than the Ruby philosophy.
Still, huge improvement over the 2005-era design. Just wish they'd optimized it properly.
Re: Ruby website redesigned
#110Earlier quoted context omitted.
Why does a site even need a light/dark toggle, when you can just use prefers-color-scheme in CSS, and the user can select that in their browser settings? (Also, technically, alternative stylesheets can be defined in HTML, except every browser except Firefox removed it: https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/... )
Because being able to switch from light to dark mode by clicking a single button is a useful feature, and while it would be nice if operating systems provided this out of the box, many (e.g., Windows) do not.