I used cursor over the past three weeks to update a 12 year-old Ruby on rails project. While it has been slightly updated throughout the years, this was my first proper modernization of the code base.
It’s been a real pleasure getting back into Ruby after so many years in typescript, python, and rust.
Happy to see the update. Real shame about the haters here, the Ruby community is a supportive and positive bunch that has shipped real products while others seem to worship at the altar of computer science alone… that’s about as counter snarky as I want to be here
I spent ~16 years with Ruby (as a non-primary language for the first 5 years, but then as my primary for the remainder), from ~2006/2007 til 2022/2023. I had a couple of hours free to spin up new personal project this morning. At first I was going to default to Python since I use it heavily at work. On a whim, I decided to see what Ruby 3.4 has to offer since it's been a few years. I am very happy with that decision. I really miss Ruby the language a lot, it's such a joy to work with.
Social justice fundamentalism asserts that there are favored (“oppressed”) groups, and disfavored (“oppressor”) groups.
True believers have created a largely arbitrary grouping called “white people”, assigning it the “oppressor” label.
If a favored group’s nation were flooded by “white people”, that would be seen as an emergent situation requiring remedy; the opposite is what we’re seeing play out in societies like Britain, and is Not a Problem. I’m committing an act of violence by even describing it in this way.
How or when a disfavored group is restored to neutral or favored status is undefined; one would presumably have to consult a head priest of the movement for an answer (and I wouldn’t expect any coherence or clarity).
The OP was me. I pointed out how DHH's uses the term "native brit" to mean "white person" even though that is not the meaning of "native", which means you were born somewhere.
>I pointed out how DHH's uses the term "native brit" to mean "white person"
Nowhere in his post does he mention "White person." He specifically mentions "native Brits." The only indigenous Brits native to the Britain are White Brits.
So 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.
Yeah, I thought those code samples would run immediately, in which case maybe the loading would be justified (although surely very easy to avoid). Instead, they're links to a different page that has the same code sample and a link to run the code, meaning I need to press twice to see what the code does when it runs, which isn't a lot but is surely at least one (possibly two) clicks more than necessary.
That said, it's cool seeing some of those samples, because they're honestly not really what I expected. For example, I didn't expect the list subtraction to work at a set operation, so seeing that example gives me a feel for what sort of things I can do with Ruby code.
> I need to press twice to see what the code does when it runs, which isn't a lot
I don't know the exact numbers, but the figures show you lose a high percentage of viewers with each click. So if you have 100 people who view the first page, 10 of them might click the link to the second page, and only 1 of them might click the link to the third page. If having customers view the running code is crucial, you'd want it on the very first page, above the fold.
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 hits will top out at ~ 10k / hour.
I am no great fan of animations, simpler is better imho - and I have resisted requests to add a sandbox to the Raku site since https://glot.io/new/raku does such a good job anyway... but I think Ruby is likely to appeal to a wider audience via a cool design vibe, whereas Raku is still in the early adopter / geek phase of adoption.
> I am sure that they will come back and optimize, but tbh this is not the priority with a new site where the hits will top out at ~ 10k / hour.
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.
I think you might have an issue with modern frontend practices. That's okay, but there's a disproportionate amount of hate towards Ruby's redesigned page. And it looks perfectly fine. HTPP/2 parallel requests aren't that big a deal, all things considered.
The website looks cool to me, makes me want to try Ruby.
He doesn't hate Ruby's redesigned page. He is complaining about yet another example of waste of resources that clients have to do because you want your page look "dynamic". Please, make sure and be aware were these comments are being posted, a site that it's both "dynamic" and doesn't require much resources from the client.
This is a page that appeared on HN front page news.
So what do you expect? People ignoring the frankly idiotic choices made that you now defend with "they will come back and optimize it"?
> HTPP/2 parallel requests aren't that big a deal, all things considered.
I literally see a progress counter that is for some reason required to display the most trivial animation to show ... a single static link. On a gigabit connection. All that takes up to two seconds.
On that same connection the same thing happen to three purely three static examples of code that somehow need up to two seconds to appear and to shift the entire content of the page.
Hmm, I don't see it. The animation loads instantly for me on a cold visit. The examples were already there. I tried it in Orion and things were a bit slower, Firefox too. But still not the multi-second delay, and I'm here on a ~30Mbps copper line with some latency. (Thanks syndicus!)
That said, I've no reason to defend the page. It just didn't strike me as bad, but I can see how others are experiencing a bad page.
I once tried to try Raku years ago, but I was left really confused by the website and docs.
Clicking through the code examples on your new website, I kept being amazed at some of the great things Raku does. It's night and day in understanding the uses and purpose of the language! Thank you.
Unfortunately, as soon as I click into the "introduction" section of the docs I'm abandoned to a wall of links and am once again lost. I'll try persevere this time, but I think you could do adoption of Raku a great favour by working on organising your docs site a bit more clearly. Astro's docs are an amazing case-study on best-in-class docs layout and writing: https://docs.astro.build/en/getting-started/
You don't even need to do a certain aesthetic to make your website fast. Just send your entire content in the HTML, instead of needing extra HTTP requests for JS and then more HTML before having all the stuff for your first render.
The early internet aesthetic is why, as much as I dislike the site's culture, I continue to use reddit + RES.
The UI, the minimal buttons, the tight paddings, the lack of pop-in, the complete lack of animations; these have all been essentially unchanged for the past decade. Even the dark mode colors look exactly as it did the first time I switched it on.
It even loads the code snippets in separate HTTP requests :-(
But the snippets themselves are really good! I'm going to update mine on https://mastrojs.github.io
Yep, and for such cases it is usually very easy to make it work properly, if only a web developer put a little thought to it. We have most or all of the tools we need in HTML and APIs to make it work regardless. Like for example for the happy customer counter one could easily have a noscript fallback, that uses the number one already needs to retrieve to show the animation, but puts it there immediately. Then, iff JS gets executed, one can still animate the shit out of it.
It is part of what distinguishes actually good web devs from move fast and break everything kind of people.
I guess I thought of noscript due to other cases I had recently, where I noscript-ed a whole workflow and displayed elements, that should never appear, when JS is running.
I like how it looks. I don't like to see how badly it is crafted tech-wise - not optimized images by size and deferring, JS for things that work natively in the browser, bloat of tailwind instead of nice clean and modern CSS.
Knowing ruby I can tell that the relaxed approach to the website does not correspond with sophistication in the language itself. If I wouldn't know ruby, that would be a put off for me, thinking that if they don't want to convince me tech-wise by their site, it might be similarly annoying to deep-dive into the language.
- images: none are visible above the fold - all should be lazy loaded (like it is done with all conference images) and
the pragdave.jpeg one does not need to be that large;
- JS: navigation toggle, including chevron rotation can be done in CSS using :has combined with checkbox/radio input. Similarly for header-navigation and theme-toggle (here combined with cookie store). Then toc.js - seems like something easy to do in the backend. Hero-animation - I haven't looked much through it but seems like at least some parts can be done in CSS;
- CSS/tailwind - well it would probably take less typing to do it just in CSS, the site does not seem to be that much componentized to benefit from tailwind.
I would generally caution against doing toggles with CSS. While it can be done, it often has surprising effects, and can be difficult to make properly accessible (for example in the case of opening the navigation, I don't believe it's possible to set the correct aria tags to indicate that the toggle is a button that is showing/hiding another element on screen).
Instead, for a brochure site like this, I'd rather have the links just always visible, because this is the reference site for Ruby and I imagine a lot of people find them by searching "Ruby", coving l clicking the homepage, and scanning for the link to the docs/downloads/etc.
Alternatively, if the show/hide feature is really that important, right now I would (a) explore whether it can be done accessibly using the new invoker API, so you don't need JavaScript at all (with a JS fallback), or (b) just do it in JavaScript directly, but with an accessible default if the JS doesn't get loaded properly.
But yeah, the rest I largely agree with. There's a bunch of stuff here that would have been simpler, and arguably also easier, if they'd taken a slightly different approach.
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?
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.
> 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?
Good question, especially since the Ruby site already does this by default. Perhaps the argument is that one of the two color schemes may be designed so poorly that the user may want to manually switch to the other one.
Because as a user, I want to change the light/dark of your site, not every set, and not my OS. If you don't have a toggle, you are making assumptions that aren't accurate.
I am assuming that if the user selected a specific brightness mode, they want sites they visit to respect that theme. Call me crazy but this seems like common sense.
I know some web developers think that that’s true, but looking at the average people I know, they tend to want different settings depending on the site. People don’t generally want computer-wide settings for darkmode.
This is true, also for people immersed in this world. Sometimes the dark mode of a site is ass, and it's better to set a preference for that site to use light mode to make it more usable.
It could be done with :indeterminate state (so key in a cookie would be absent or removed when switching), but I'd probably would do it with radios instead
Note that a checkbox's indeterminate state can only be set via JavaScript, so that lessens the elegance of a CSS-based approach.
I agree that using radios would be better. Or just prefers-color-scheme, which sidesteps the FOUT issue that often occurs when storing theme settings in localStorage.
Ruby isn't necessarily for web devs. Ruby is popular for all sorts of business line applications. In Japan is popular for lower level programming. You can do game programming via something like Dragon Ruby. Sure its very popular for Rails, but you don't necessarily need to do web dev.
Not long ago I was looking through programming language sites to figure out how to best introduce the language I'm working on.
ruby-lang.com stood out with a text in a big font:
Ruby is...
Followed by a paragraph about what makes Ruby special. I think that was an exceptionally simple and natural way of introducing something as complex as a programming language.
"Programmer's best friend" is precisely the wrong thing to do though (it says nothing and only makes the reader confused. Are we talking about a language or a pet? I'm not looking for a friend.). They took a step back with that.
The old one was better because it said something about what the language is and how it benefits the user. "Best friend" is not descriptive. "dynamic language with minimal syntax that is easy to read and write" at least tells me something about Ruby, its priorities, and value proposition. I'm very concerned about a language that claims it wants to be my friend.
Dunno, it's a comfy tagline. I never got into Ruby but it always feels to me like it's a really ergonomic and cozy language. Sure, the best friend thing is a stretch, but it's honestly a slogan. How many people land on this page with no knowledge of what Ruby is and will confuse it with an app to make friends?
It sure is a comfy tagline, but because it doesn't really mean anything you could say it about any language, and it only works if you already know what Ruby is. It's not that anyone would confused Ruby with an app to make friends, but it doesn't really say anything about Ruby at all. As other pointed out, the page doesn't even make clear that Ruby is a programming language.
I 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 artificial loading. It's not a webapp, it's a website.
I don't think that JS does any preloading. When I open the front page and I click somewhere it loads normally for me, and it downloads the whole page content, after my click (desktop, Firefox).
No. It might, depending on what your browser does, but it's not in the web standard.
But you can have a button that saves your state when you enable javascript, and doesn't save your state (but still works) when you disable javascript.
edit: I think it is possible to save your state on the second click. So the UX is: you have 3 options with a slide. You click one of them, the page theme changes, and the option icon becomes a padlock. You click on it again, and the option is saved.
It seems to be a limitation that without javascript a single click can't change a switch and do something else--make a request to set a cookie. But you can do changing style on first click, then setting a cookie on the second. Here's a demo (written by Claude) (it doesn't work without server, just the HTML part) https://jsfiddle.net/r134vgo7/3/
Meta, but it's kind of ironic that the main Ruby language website shows a "0%" Ruby symbol with javascript deactivated, and doesn't even show the code examples, which are all just links to some sandbox anyway.
It annoys me so much when developers think they can do it better and link with JavaScript. Interactions (like opening a dialog) witj JS - yes. Navigating to sites/positions in-site - that is just dumb. So many pages break the "open in new tab" behaviour with this implementation.
Obviously Raku leans more to `{}` and `my $var` than Ruby - but otherwise I think it does a credible job. Obviously these are carefully chosen Ruby snippets to highlit its unique abilities in strings, "array math" and classes. On the string interpolation, I would say that Raku has the slight edge (and has the whole Q-slang for a lot of fine grained control). On the array math, I had to apply the (built in) Raku set diff operator ... so I guess that Ruby is a little more natural for this (rather quirky) feature. On the class stuff, again very close. Raku has much more powerful OO under the hood ... multi-inheritance, role-composition, punning, mixins, MOP, and yet is a delight to use in this lightweight way.
let say = "I love OCaml"
let () = print_endline say
(* Requires linking in the 'str' library *)
let say = Str.replace_first (Str.regexp {|\(.*\)love\(.*\)|}) {|\1*love*\2|} say;;
let () = print_endline (String.uppercase_ascii say)
let () = ignore |> Seq.init 5 |> Seq.iter (fun () -> print_endline say)
Ex 2
module StringSet = Set.Make(String)
let cities = StringSet.of_list [
"London";
"Oslo";
"Paris";
"Amsterdam";
"Berlin";
]
let visited = StringSet.of_list ["Berlin"; "Oslo"]
(* Requires the 'fmt' library *)
let string_set fmt v = Fmt.Dump.list Fmt.string fmt (StringSet.to_list v)
let () =
Format.printf "I still need to visit the following cities: %a\n"
string_set
(StringSet.diff cities visited)
Ex 3
module Greeter : sig
type t
val make : string -> t
val salute : t -> unit
end = struct
type t = { name : string }
let make name = { name = String.uppercase_ascii name }
let salute t = Format.printf "Hello %s\n" t.name
end
let g = Greeter.make "world"
let () = Greeter.salute g
Obviously, OCaml is a much lower-level language than Ruby or Raku–notably, regex support is not as great, and we have to explicitly tell it how to print values of custom types. Still, I find its lack of syntax sugar makes it easy to read nearly any OCaml code I come across in the wild!
The leading web framework for Raku is Cro (https://cro.raku.org) . Cro has deep support for distributed architectures and middleware pipes and a nice templating language.
Refreshing and delightful! I know how the home page looks doesn't reflect the programming itself, but this design really makes me want to try Ruby again :)
> I know how the home page looks doesn't reflect the programming itself
It does reflect what the language creators pay attention to. Way back when, when I was undecided between learning Python or Ruby, after visiting countless resources I noticed Ruby websites in general looked way nicer and clearer than Python websites, so I picked Ruby. Now, years of experience with both languages later, I have zero doubt that to me that was the right choice at the time. I would’ve been frustrated with Python to no end.
I no longer need either language regularly, but given the choice again I would not hesitate to go for Ruby.
All that said, I do agree with some other comments on the thread regarding the disappointing reliance on JavaScript here. Should just be static.
DHH is the lead developer of the most popular ruby web framework, Sandy is the author of a mildly popular book. Not knocking her work, but DHH is magnitudes more influential.
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, is a living organism!), instead of being frozen in amber for a decade like the last version!
I mean, you're allowed to think an ethnonationalist has a consistent and reasonable worldview. That's absolutely ridiculous but you're free to think it. Nobody's cancelling anyone.
But having DHH as a face of your programming language, a language that's supposed to have a "warm community", doesn't really make any sense, and it will obviously drive people away.
Being critical of MENA migration is not hateful speech.
Hateful speech is stating: you are from a MENA region therefore you are x negative trait.
Being critical of migration is just being critical of migration, which is allowed. His defence ("suicidal empathy" etc;) comes from the situation in the UK where people are being arrested en-masse for "hate speech" for referencing acts of terror[0].
You can dislike what he says, but hateful carries a more specific meaning (to me, at least).
I think he backed his citations, and just because migration from MENA regions (a historically entirely different culture) are “brown people” doesn’t make it invalid. Mexicans are also brown people and so are Spanish people in some definitions. Yet somehow he’s not talking about them. If you look closely he’s criticising the kids gloves that the authorities are handling the newcomers that leads to a worsening narrative for everyone- lets not forget that there are victims in both camps here.
We should be able to criticise migration without everyone saying it’s racism otherwise you loosen the definition of racism so much that everybody becomes a “racist” eventually and it stops having a sting
He did not back those up. He provided anecdata about a single "Pakistani rape gang" story, but the actual statistics say that child sex crime "gangs" are predominantly white [1].
You're allowed to criticize immigration, but if you only ever cherry-pick anecdotes about immigrants of a certain color and creed, and also refuse to correct your statement after you're made aware of the actual facts, you're most likely a racist.
DHH is also not criticizing immigration per se, because he's including non-white native brits in his category of undesirable Londoners. You can't deny that that's racism. These are people who grew up as part of the British culture, they just don't have the right skin tone.
I appreciate the thoughtful response and the commitment to facts. Racism has no place in these discussions. Let’s examine the points with nuance, drawing from the cited report and context.
On the Home Office Report’s Statistics
The 2020 paper states that group-based child sexual exploitation (CSE) offenders are “most commonly White”.[0]
However, it highlights major data limitations. Ethnicity was often unrecorded or incomplete. Police forces supplied partial details only. The report notes that “the academic literature highlights significant limitations to what can be said about links between ethnicity and this form of offending”.
It also cautions against conclusions due to “data quality problems, the way the samples were selected in studies, and the potential for bias”. A 2025 audit by Baroness Casey confirmed this. Ethnicity went unrecorded for two-thirds of suspects. Better data collection is now mandatory.
While the report leans towards White predominance overall, it acknowledges high-profile cases “have mainly involved men of Pakistani ethnicity”.(also in[0]) It does not rule out over-representation in specific subtypes. This invites careful interpretation rather than dismissal.
On Cherry-Picking Anecdotes and Corrections: Selective stories can mislead. Yet DHH often cites aggregated data from European reports, such as Denmark’s figures on higher crime rates among certain immigrant groups. He praises selective immigration from compatible cultures and commends Denmark’s integration policies. This points to policy focus, not inherent bias.
If presented with the report’s full nuances and unmoved, that warrants critique. Given its caveats and recent calls for improved data, the debate remains open.
On Non-White Native Brits and Racism; Implying Britishness ties to skin tone is wrong. DHH’s remark about “Brits being a minority in their own capital” refers to the “White British” census category, at 37% in London per the 2021 census. This tracks ethnic shifts officially.
Non-White British citizens, many native-born and fully integrated, are undeniably British. If his phrasing suggests otherwise, it needs clarification. His posts emphasise rapid changes from mass immigration, not rejection of integrated individuals. Many non-White Brits voice similar concerns on resources and cohesion, without racism.
Criticising policies can be valid if evidence-based and non-dehumanising. Targeting one group without balance risks bias. DHH’s stance seems data-driven on integration, but scrutiny is fair.
You say non-white British citizens are fully integrated undeniably, but somehow you still determine DHH to be data-driven, even though he implies they aren't, by tracking the "White British" ethnic category.
You even mention this, although for some reason do not comment on how it's clearly racist and misleading.
So I have to conclude you're either waffling, or you're pasting ChatGPT output without parsing what it means. Because if you apply your own logic, you would come to the conclusion that he's using far-right talking points to further far-right, racist views.
edit: I thought I recognized that name, you've replied to me previously with LLM-ish output. You're the weirdo Malmö guy with racist irc chat logs (this you? https://darkscience.net/quotes/#123). I mean granted, their ten years old. Men fan pinsamt ändå. Och med eget namn också, Jan Harasym. Inte vassaste kniven i lådan, va?
So, in order to show a single download link it needs to load an animation with visible loading progress even on a gigabit connection. It takes a few seconds to appear. All to show a scaling animation that can be achieved with a couple of lines of CSS.
Same for absolutely static code examples that take a few seconds to load and shift the content away.
You are a rare species, on the verge of extinction.
Unfortunately, most people today probably don't care about what you're talking about. (I do, but I've decided not to comment on it anymore, because it would probably drive me crazy :)
Sure, if you ignore the SSR and SSG part, which sadly most nodejs stuff lacks.
Additionally, Next.js should only be used when SaaS product vendor doesn't allow for any other option, which sadly is the case when making themselves sellable to magpie developers, while riding VC money until the IPO takes off.
I rather deliver, than do yak shaving, but at least can deliver only HTML and CSS if I chose to.
Tailwind maps directly to CSS (well, it is pure CSS) and doesn't require a loading progress for a one-line animation: https://tailwindcss.com/docs/animation
I like the design and content. Being able to immediately try a language online is huge
But there has to be a way to load that content in a progressive manner. Loading a static version first and then hydrating the content if you need interactive actions
Nice! There is a Japanese feel to the lead graphic, their prevalence of cartoon imagery, that one might not recognize without having traveled in Japan.
Is the design debate public? I'd imagine it would make great reading.
The site looks great visually but the technical implementation is disappointing. Here's what's wrong:
1. 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.
I don't get the people who complain about the website not working with disabled js. Maybe I miss something and a large part of users disable / have js disabled in their browsers for some reason?
Why the target audience of the ruby, probably primary web developers, whould do that? Or is this a some kind of secret handshake so community accept you (to build a website that can work with no js)?
Back in the 2000s in the web standards development community there were multiple web development strategies called "progressive enhancement", "graceful degradation" and "unobtrusive javascript":
There were a lot of practical reasons for that: The browser landscape was much more diverse, different browsers had different support of standard Javascript, some browsers didn't even support JS and some people still kept text-only browsers like lynx/links in mind. Also browsers were not evergreen, so a large part of the audience could be on some older versions. Another thing were sometimes brittle network connection, especially over mobile. Depending on JS could in the case of corruption mean non-functioning websites.
For a lot whose exposure to web development and the discussions abound that, that reason will be stuck in their head, even if in the last decade of React ets the "best practices" will have changed.
There is also an aesthetic thing: There is a thing of beauty in simply curling an url and piping it into grep or such to get the thing you need, instead of having so have an headless browser. In my mind that is still how the web should work.
It's a common philosophy for developers with standards of robustness and accessibility to not hard depend on js for things that don't need js to function.
> Why the target audience of the ruby, probably primary web developers, whould do that?
In my experience, it's mostly web developers who care about this in the first place.
> mostly web developers who care about this in the first place.
I’m not sure what you mean by this. We care about our users and how they use our websites. JavaScript is everywhere and has been the de facto frontend standard for the past few years. Supporting no-JS is starting to feel like supporting a new browser. As much as I’d like to, from a business and product point of view, the numbers are just too small for us to even consider it.
I didn't imply that all web developers care about it, but that most of the people who care about it are web developers. I won't deny that it's still a minority.
I can understand the aspiration to have the system that can be run from the lowest level out of box tools, but then, I am doing frontend for almost a decade and this is porbably the first time I'm seeing such attention to this specific 'no js' use case, as in this thread.
Maybe I'm not reading enough webdev forums. I agree though that things that don't required js should be written in no js way.
I see that this coincides with Ruby 3.4.8 release[1]. I wonder we will get another Ruby release on 2025-12-25, since Ruby has made a Christmas day release for 13 consecutive years[2].
It looks great, but it's missing the one thing I want most in the site - the ability to select the version of the language documentation in some way other than editing the URL directly. I use ruby-lang almost exclusively for the documentation.
I also wish the documentation search parameter were saved in the URL. This would allow people to create a custom Chrome search engine like @ruby and dramatically speed up doc searching.
The Lighthouse report is telling. It scores 100% for Best practices and SEO, but 54% for Performance. Pages like these used to be caricatures of the modern web, but are now acceptable. DHH's statement doesn't help either.
Honestly, the synthetic Lighthouse tests would be great but for the fact that they're using Google Fonts. It's like the only major thing in their critical path.
Ruby is GOATED.
You can say what you want but Ruby coupled with Rails is the most productive web stack period.
Why you might ask?
- Omakase Stack
- high level is good for business processes
- modern concepts without JS ecosystem churn
- great testing capabilities
- great ecosystem
- highly effective stack for LLMs (conventions)
Is it fast in Benchmark Games - not by any means.
Will you be able to finish projects and make money with it? Absolutely.
The number of times Matz is mentioned and depicted on the homepage is offputting. MINASWAN feels too close to WWJD for me. I can't think of another programming language community that does this, and I'm including Wolfram in that assessment.
The visual refresh is great, but the technical implementation is disappointing. Code examples are static text fetched via JavaScript instead of being in the HTML. With JS disabled, you get a frozen "0%" loading screen.
This is ironic because Ruby has always emphasized doing things "the right way" and developer happiness. A language website should be a poster child for progressive enhancement - especially one that champions elegance and proper practices.
Still, huge improvement over the 2005-era design. Just needs optimization work to align the implementation with Ruby's philosophy.
Bad branding community wise to quote DHH on the frontpage. Will immediately turn away many. He isn’t worth wasting the reputational loss that comes with printing his words.
I assume you are quoting the Great Replacement theory, which is a whole bunch of far-right nonsense. Or maybe people extrapolated his statements to that, then the Kraken was unleashed.
On my iPad, without scrolling, the screen shows almost nothing, just a download button and some text that, I think users will ignore. I think that’s a waste of valuable screen estate.
Also, apart from a quote from David Heinemeier Hansson the home page doesn’t even mention that ruby is a programming language.
For comparison, the following all mention that above the fold, with a short phrase indicating what you would want to use the language.
- https://www.python.org/ has “Python is a programming language that lets you work quickly and integrate systems more effectively. Learn More”
- https://www.perl.org/ has “Perl is a highly capable, feature-rich programming language with over 37 years of development”
- https://www.php.net/ has “A popular general-purpose scripting language that is especially suited to web development.
Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.”
- https://www.swift.org/ has “Swift is the powerful, flexible,
multiplatform programming language. Fast. Expressive. Safe.”
That’s not funny; it’s good use of the most prominent part of the site.
A site (re)design starts with determining who’s your audience, and what you want to tell them.
These sites will want to serve both existing and new developers.
What they want to tell them will be different for the two groups, but the existing ones won’t be chased away by a short description aimed at newcomers, but newcomers can easily turn away by the lack of such a description.
As to what to put in the description: it sort-of is an advert, so you often don’t exactly say what you are, but more what you want to be.
https://www.swift.org is a clear example. They definitely want to tell everybody that Swift is multiplatform, giving cloud services, command line tools and embedded development more prominence than iOS apps.
For example, on the swift site, they claim ‘embedded’. If you click on that, you get examples for various platforms such as Raspberry Pi and STM32 (https://www.swift.org/get-started/embedded/). That allows you to verify that claim.
In contrast, this Ruby site makes claims such as 'Easy to write, easy to read. Natural syntax like spoken language’, 'Do more with less code', but it’s not easy for users to check whether that’s true.
> somehow, the Ruby community [...] think it's acceptable to have a standard implementation that does neither AOT nor JIT native code compilation
Ruby have YJIT, which is a production ready JIT compiler that generates native machine code. But it requires enabling via flag "--yjit" rather than running by default.
Why? I think it's primarily to avoid build time dependencies on Rust and prevent unexpected overhead for users. This keeps binary light and avoids forcing Rust installation on users, especially for those who run interpreter only, where YJIT adds no value.
Note that including YJIT also bloat binaries by 5 to 10MB (Rust static lib + code cache structures) for source builds and complicates cross compilation since Rust targets vary by architecture (focus x86-64 and arm64, not all platforms).
Also, Rails 7.1+ enables YJIT by default, so JIT (to native code) in Ruby is being utilized when actually needed.
Quickly followed by folks talking about a warm and welcoming community. Which in fairness, is true! DHH is the counterexample. Platforming him in 2025 seems nonsensical.
Ah yes, the "fuck your feelings" reductive response.
But no, what I meant to get at is that DHH's ego is radioactive. RailsConf tried to open their keynote to having Maybe Perhaps Someone Else Talk Sometime and DHH's response was, as it were, [off the rails](https://world.hey.com/dhh/no-railsconf-faa7935e). RailsWorld started the next year and, happy to have DHH keynote, took off. RailsConf swiftly died.
If you're running an ecosystem with a vocal community, is that a fire you want to play with?
His posts, his statements, his treatment of other people, yes, he advocates for things which cause harm to others. The term is stochastic terrorism. He creates a welcoming space _to people who are accepting of his bigoted ideology_ which gives some nice publicity, but is not creating a kind and welcoming community.
Well, for starters, I never got LSP to properly work with Ruby at the same level as other languages, i.e. so it's possible to browse the standard library.
Which LSP are you using? I'm using both solargraph and ruby-lsp and both works fine by me (in neovim).
Although those who really care about LSP support usually will use RubyMine IDE instead. Some of my colleagues are going that route, and they're mostly coming from Java (or similar background)
I'm not really "using it", I'm just trying every now and then, and I keep encountering errors, hangups, and lack of functionality. Now I've tried ruby-lsp, and it just sits there on "Starting Ruby LSP...\n"
Couldn't even install Solargraph, once it errors out with 'Kernel#require': cannot load such file -- yard, other time it installs, but "solargraph scan" fails in runtime with "missing gem date" error.
Sorbet doesn't even work in VSCode, some bugs are over 5 years old.
But yeah, downvote my original post, because apparently all of the above is obviously my fault.
RubyMine was paid until recently, now it's free only for non-commercial use. It's also not really suitable for small scripting.
Historically, one insanely huge advantage of Ruby was that it was pre-installed on macOS'es, but I think they've stopped doing that since some macOS version.
I used cursor over the past three weeks to update a 12 year-old Ruby on rails project. While it has been slightly updated throughout the years, this was my first proper modernization of the code base.
It’s been a real pleasure getting back into Ruby after so many years in typescript, python, and rust.
Happy to see the update. Real shame about the haters here, the Ruby community is a supportive and positive bunch that has shipped real products while others seem to worship at the altar of computer science alone… that’s about as counter snarky as I want to be here
I spent ~16 years with Ruby (as a non-primary language for the first 5 years, but then as my primary for the remainder), from ~2006/2007 til 2022/2023. I had a couple of hours free to spin up new personal project this morning. At first I was going to default to Python since I use it heavily at work. On a whim, I decided to see what Ruby 3.4 has to offer since it's been a few years. I am very happy with that decision. I really miss Ruby the language a lot, it's such a joy to work with.
Ruby is still a joy for me, too, and Rails continues to evolve while providing solid best practices as the default.
A side effect is an increased intolerance to agony, boilerplate verbosity, complexity. I look at the JavaScript world and shudder.
Also, Ruby being as expressive as it is, describing things to an LLM is not really a timesaver over writing the code myself.
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
So everyone born in USA is a native American, right?
Yes, they are native to the USA.
They aren't native american of course. That's a silly dishonest argument based on wordplay.
So why are they not "native Americans" but the people referenced in your quote are "native Brits"?
[flagged]
So using a term as an ethnonym for historically British ethnic people is racist?
If so, is it racist to assert or assume that ethnic Europeans exist?
Social justice fundamentalism asserts that there are favored (“oppressed”) groups, and disfavored (“oppressor”) groups.
True believers have created a largely arbitrary grouping called “white people”, assigning it the “oppressor” label.
If a favored group’s nation were flooded by “white people”, that would be seen as an emergent situation requiring remedy; the opposite is what we’re seeing play out in societies like Britain, and is Not a Problem. I’m committing an act of violence by even describing it in this way.
How or when a disfavored group is restored to neutral or favored status is undefined; one would presumably have to consult a head priest of the movement for an answer (and I wouldn’t expect any coherence or clarity).
It sounds like a Marxist structure with re-assigned labels.
What the hell are you on about.
"Native brit" does not identify a people the way "native american" does.
There is no entry in the dictionary for "native brit".
This is all I'm talking about.
Quit trolling.
"The English people are an ethnic group [...] native to England." [0]
"[White Brits] is an ethnicity classification used for the White population identifying as English..." [1]
The English are the native and indigenous ethnic group to England (London). White Brits are a category that includes the English.
QED.
[0] https://en.wikipedia.org/wiki/English_people
[1] https://en.wikipedia.org/wiki/White_British
OP was trying to talk about ethnic brits, and I think that was clear from the context. He was then rebuked for that.
The OP was me. I pointed out how DHH's uses the term "native brit" to mean "white person" even though that is not the meaning of "native", which means you were born somewhere.
>I pointed out how DHH's uses the term "native brit" to mean "white person"
Nowhere in his post does he mention "White person." He specifically mentions "native Brits." The only indigenous Brits native to the Britain are White Brits.
So 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.
Yeah, I thought those code samples would run immediately, in which case maybe the loading would be justified (although surely very easy to avoid). Instead, they're links to a different page that has the same code sample and a link to run the code, meaning I need to press twice to see what the code does when it runs, which isn't a lot but is surely at least one (possibly two) clicks more than necessary.
That said, it's cool seeing some of those samples, because they're honestly not really what I expected. For example, I didn't expect the list subtraction to work at a set operation, so seeing that example gives me a feel for what sort of things I can do with Ruby code.
> I need to press twice to see what the code does when it runs, which isn't a lot
I don't know the exact numbers, but the figures show you lose a high percentage of viewers with each click. So if you have 100 people who view the first page, 10 of them might click the link to the second page, and only 1 of them might click the link to the third page. If having customers view the running code is crucial, you'd want it on the very first page, above the fold.
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 hits will top out at ~ 10k / hour.
I am no great fan of animations, simpler is better imho - and I have resisted requests to add a sandbox to the Raku site since https://glot.io/new/raku does such a good job anyway... but I think Ruby is likely to appeal to a wider audience via a cool design vibe, whereas Raku is still in the early adopter / geek phase of adoption.
btw Ruby is a fantastic language!
> I am sure that they will come back and optimize, but tbh this is not the priority with a new site where the hits will top out at ~ 10k / hour.
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.
I think you might have an issue with modern frontend practices. That's okay, but there's a disproportionate amount of hate towards Ruby's redesigned page. And it looks perfectly fine. HTPP/2 parallel requests aren't that big a deal, all things considered.
The website looks cool to me, makes me want to try Ruby.
He doesn't hate Ruby's redesigned page. He is complaining about yet another example of waste of resources that clients have to do because you want your page look "dynamic". Please, make sure and be aware were these comments are being posted, a site that it's both "dynamic" and doesn't require much resources from the client.
This is a page that appeared on HN front page news.
So what do you expect? People ignoring the frankly idiotic choices made that you now defend with "they will come back and optimize it"?
> HTPP/2 parallel requests aren't that big a deal, all things considered.
I literally see a progress counter that is for some reason required to display the most trivial animation to show ... a single static link. On a gigabit connection. All that takes up to two seconds.
On that same connection the same thing happen to three purely three static examples of code that somehow need up to two seconds to appear and to shift the entire content of the page.
Both are especially jarring on mobile.
Hmm, I don't see it. The animation loads instantly for me on a cold visit. The examples were already there. I tried it in Orion and things were a bit slower, Firefox too. But still not the multi-second delay, and I'm here on a ~30Mbps copper line with some latency. (Thanks syndicus!)
That said, I've no reason to defend the page. It just didn't strike me as bad, but I can see how others are experiencing a bad page.
Here's mobile experience: https://youtube.com/shorts/LFIQeEL2S0U
The same is on desktop Firefox. For some reason youtube can't process the screencast for that :)
I once tried to try Raku years ago, but I was left really confused by the website and docs.
Clicking through the code examples on your new website, I kept being amazed at some of the great things Raku does. It's night and day in understanding the uses and purpose of the language! Thank you.
Unfortunately, as soon as I click into the "introduction" section of the docs I'm abandoned to a wall of links and am once again lost. I'll try persevere this time, but I think you could do adoption of Raku a great favour by working on organising your docs site a bit more clearly. Astro's docs are an amazing case-study on best-in-class docs layout and writing: https://docs.astro.build/en/getting-started/
thanks I made a docs issue https://github.com/Raku/doc/issues/4739
> Speaking from experience (recently we rebuilt https://raku.org),
FYI, front-page has a lot of examples, that I assume change when switching tabs, e.g. "multi-paradigm" "strict-gradual" "interactive-mode", etc.
But nothing happens, neither Safari 18.6, nor Chrome 143.0, on macOS 15.5.
FWIW, cannot reproduce on Safari 18.6 on MacOS 15.6.1
I really like the 90s-esque aesthetic of sites like HN.
Low bandwidth, minimal in an artistic way.
I wish less sites would try to make them look like a wordpress from the early twenty aughts.
You don't even need to do a certain aesthetic to make your website fast. Just send your entire content in the HTML, instead of needing extra HTTP requests for JS and then more HTML before having all the stuff for your first render.
[matrix voice]
What if I told you that you don't need javascript?
The early internet aesthetic is why, as much as I dislike the site's culture, I continue to use reddit + RES.
The UI, the minimal buttons, the tight paddings, the lack of pop-in, the complete lack of animations; these have all been essentially unchanged for the past decade. Even the dark mode colors look exactly as it did the first time I switched it on.
It even loads the code snippets in separate HTTP requests :-( But the snippets themselves are really good! I'm going to update mine on https://mastrojs.github.io
Yep, and for such cases it is usually very easy to make it work properly, if only a web developer put a little thought to it. We have most or all of the tools we need in HTML and APIs to make it work regardless. Like for example for the happy customer counter one could easily have a noscript fallback, that uses the number one already needs to retrieve to show the animation, but puts it there immediately. Then, iff JS gets executed, one can still animate the shit out of it.
It is part of what distinguishes actually good web devs from move fast and break everything kind of people.
The noscript would not be needed at all. The value could be the real one by default, then in js set to 0 and incremented
True, in this case even easier!
I guess I thought of noscript due to other cases I had recently, where I noscript-ed a whole workflow and displayed elements, that should never appear, when JS is running.
I like how it looks. I don't like to see how badly it is crafted tech-wise - not optimized images by size and deferring, JS for things that work natively in the browser, bloat of tailwind instead of nice clean and modern CSS.
Knowing ruby I can tell that the relaxed approach to the website does not correspond with sophistication in the language itself. If I wouldn't know ruby, that would be a put off for me, thinking that if they don't want to convince me tech-wise by their site, it might be similarly annoying to deep-dive into the language.
> not optimized images by size and deferring, JS for things that work natively in the browser, bloat of tailwind instead of nice clean and modern CSS.
care to elaborate?
Sure:
- images: none are visible above the fold - all should be lazy loaded (like it is done with all conference images) and the pragdave.jpeg one does not need to be that large;
- JS: navigation toggle, including chevron rotation can be done in CSS using :has combined with checkbox/radio input. Similarly for header-navigation and theme-toggle (here combined with cookie store). Then toc.js - seems like something easy to do in the backend. Hero-animation - I haven't looked much through it but seems like at least some parts can be done in CSS;
- CSS/tailwind - well it would probably take less typing to do it just in CSS, the site does not seem to be that much componentized to benefit from tailwind.
I would generally caution against doing toggles with CSS. While it can be done, it often has surprising effects, and can be difficult to make properly accessible (for example in the case of opening the navigation, I don't believe it's possible to set the correct aria tags to indicate that the toggle is a button that is showing/hiding another element on screen).
Instead, for a brochure site like this, I'd rather have the links just always visible, because this is the reference site for Ruby and I imagine a lot of people find them by searching "Ruby", coving l clicking the homepage, and scanning for the link to the docs/downloads/etc.
Alternatively, if the show/hide feature is really that important, right now I would (a) explore whether it can be done accessibly using the new invoker API, so you don't need JavaScript at all (with a JS fallback), or (b) just do it in JavaScript directly, but with an accessible default if the JS doesn't get loaded properly.
But yeah, the rest I largely agree with. There's a bunch of stuff here that would have been simpler, and arguably also easier, if they'd taken a slightly different approach.
> Similarly for header-navigation and theme-toggle
The theme toggle has three states. How do you model this with a checkbox?
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.
> 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?
Good question, especially since the Ruby site already does this by default. Perhaps the argument is that one of the two color schemes may be designed so poorly that the user may want to manually switch to the other one.
Because as a user, I want to change the light/dark of your site, not every set, and not my OS. If you don't have a toggle, you are making assumptions that aren't accurate.
I am assuming that if the user selected a specific brightness mode, they want sites they visit to respect that theme. Call me crazy but this seems like common sense.
I know some web developers think that that’s true, but looking at the average people I know, they tend to want different settings depending on the site. People don’t generally want computer-wide settings for darkmode.
This is true, also for people immersed in this world. Sometimes the dark mode of a site is ass, and it's better to set a preference for that site to use light mode to make it more usable.
It could be done with :indeterminate state (so key in a cookie would be absent or removed when switching), but I'd probably would do it with radios instead
Note that a checkbox's indeterminate state can only be set via JavaScript, so that lessens the elegance of a CSS-based approach.
I agree that using radios would be better. Or just prefers-color-scheme, which sidesteps the FOUT issue that often occurs when storing theme settings in localStorage.
It's possible to have a 3-states CSS switch/slider that controls site theme. Google it or ask AI assistant.
The decorative underlines under the headings on the home page are embedded as content (<img> tags)!!!
Amateur hour.
I say this with love, compassion, grace, and all due respect: Who gives a shit?
It's a website for web devs. Web devs give a shit.
Ruby isn't necessarily for web devs. Ruby is popular for all sorts of business line applications. In Japan is popular for lower level programming. You can do game programming via something like Dragon Ruby. Sure its very popular for Rails, but you don't necessarily need to do web dev.
Not long ago I was looking through programming language sites to figure out how to best introduce the language I'm working on.
ruby-lang.com stood out with a text in a big font:
Ruby is...
Followed by a paragraph about what makes Ruby special. I think that was an exceptionally simple and natural way of introducing something as complex as a programming language.
"Programmer's best friend" is precisely the wrong thing to do though (it says nothing and only makes the reader confused. Are we talking about a language or a pet? I'm not looking for a friend.). They took a step back with that.
For reference this is the old one, which is much better: https://www.ruby-lang.org/images/about/screenshot-ruby-lang-... From: https://www.ruby-lang.org/en/about/website/
The old one was better because it said something about what the language is and how it benefits the user. "Best friend" is not descriptive. "dynamic language with minimal syntax that is easy to read and write" at least tells me something about Ruby, its priorities, and value proposition. I'm very concerned about a language that claims it wants to be my friend.
Dunno, it's a comfy tagline. I never got into Ruby but it always feels to me like it's a really ergonomic and cozy language. Sure, the best friend thing is a stretch, but it's honestly a slogan. How many people land on this page with no knowledge of what Ruby is and will confuse it with an app to make friends?
It sure is a comfy tagline, but because it doesn't really mean anything you could say it about any language, and it only works if you already know what Ruby is. It's not that anyone would confused Ruby with an app to make friends, but it doesn't really say anything about Ruby at all. As other pointed out, the page doesn't even make clear that Ruby is a programming language.
I 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 artificial loading. It's not a webapp, it's a website.
1. https://www.ruby-lang.org/javascripts/try-ruby-examples.js
2. https://www.ruby-lang.org/en/examples/i_love_ruby
In this day and age, it is possible to have an appealing, responsive, lightweight website with no JS (maybe except for darkmode toggle).
> 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.
Sometimes people want things we don't need. It doesn't need Javascript but it allows certain nice to have features, like instantaneous page loads.
> it allows certain nice to have features, like instantaneous page loads
Right, but I do not think this is the case here
Home pages: Ruby 4.3mb, Python 1.3mb, java.com 2.1mb, raku.org 360kb, typescript 2.1mb
Yeah but them's highway miles. I have much less care about a site loading images than the stuff that makes the mobile nav work. Images are pretty!
For instance, here's Python's 144kB JS-powered homepage mid-load: https://imgur.com/a/OvYVAMS
And theirs doesn't even have any pretty images! That said, Ruby really ought to give those images a compress.
I like instantaneous page loads after the initial first page load, which is what the JS does here. Hard to do so without it.
I don't think that JS does any preloading. When I open the front page and I click somewhere it loads normally for me, and it downloads the whole page content, after my click (desktop, Firefox).
I don't see what JS code would provide this?
wat
Darkmode toggle can be (and usually is) achieved by CSS.
And the state of it persist across page loads or tabs?
No. It might, depending on what your browser does, but it's not in the web standard.
But you can have a button that saves your state when you enable javascript, and doesn't save your state (but still works) when you disable javascript.
edit: I think it is possible to save your state on the second click. So the UX is: you have 3 options with a slide. You click one of them, the page theme changes, and the option icon becomes a padlock. You click on it again, and the option is saved.
It seems to be a limitation that without javascript a single click can't change a switch and do something else--make a request to set a cookie. But you can do changing style on first click, then setting a cookie on the second. Here's a demo (written by Claude) (it doesn't work without server, just the HTML part) https://jsfiddle.net/r134vgo7/3/
Meta, but it's kind of ironic that the main Ruby language website shows a "0%" Ruby symbol with javascript deactivated, and doesn't even show the code examples, which are all just links to some sandbox anyway.
It annoys me so much when developers think they can do it better and link with JavaScript. Interactions (like opening a dialog) witj JS - yes. Navigating to sites/positions in-site - that is just dumb. So many pages break the "open in new tab" behaviour with this implementation.
Maybe it was vibe coded, considering that Claude is the #3 committer in the website's repo[1].
[1] https://github.com/ruby/www.ruby-lang.org/graphs/contributor...
Claude is on the list because some commits by users have "Co-Authored-By: Claude ...". Does not necessarily have to be vibe coded.
I don't know what others are complaining about here, it loads for me as fast as this HN, but looks nicer.
Loading percentage in the middle? I haven’t seen one of those since Micromedia flash days.
Macromedia!
I thought it would be interesting to try the showcase examples in Raku (since I am always saying how good Raku's imitation of Ruby is)...
Obviously Raku leans more to `{}` and `my $var` than Ruby - but otherwise I think it does a credible job. Obviously these are carefully chosen Ruby snippets to highlit its unique abilities in strings, "array math" and classes. On the string interpolation, I would say that Raku has the slight edge (and has the whole Q-slang for a lot of fine grained control). On the array math, I had to apply the (built in) Raku set diff operator ... so I guess that Ruby is a little more natural for this (rather quirky) feature. On the class stuff, again very close. Raku has much more powerful OO under the hood ... multi-inheritance, role-composition, punning, mixins, MOP, and yet is a delight to use in this lightweight way.For fun, I did the same for OCaml:
Ex 1
Ex 2 Ex 3 Obviously, OCaml is a much lower-level language than Ruby or Raku–notably, regex support is not as great, and we have to explicitly tell it how to print values of custom types. Still, I find its lack of syntax sugar makes it easy to read nearly any OCaml code I come across in the wild!Man. Haven’t thought about Raku for a while. Does it have a good web framework these days?
The leading web framework for Raku is Cro (https://cro.raku.org) . Cro has deep support for distributed architectures and middleware pipes and a nice templating language.
There are others, notably the more lightweight Humming-Bird https://raku.land/zef:rawleyfowler/Humming-BirdAlso, if you want a more opinionated, HTMX centric web application library, then https://harcstack.org was used to make the new https://raku.org site
See https://rakujourney.wordpress.com/2025/03/30/the-harc-stack/
that’s a name I haven’t heard in a while
Refreshing and delightful! I know how the home page looks doesn't reflect the programming itself, but this design really makes me want to try Ruby again :)
> I know how the home page looks doesn't reflect the programming itself
It does reflect what the language creators pay attention to. Way back when, when I was undecided between learning Python or Ruby, after visiting countless resources I noticed Ruby websites in general looked way nicer and clearer than Python websites, so I picked Ruby. Now, years of experience with both languages later, I have zero doubt that to me that was the right choice at the time. I would’ve been frustrated with Python to no end.
I no longer need either language regularly, but given the choice again I would not hesitate to go for Ruby.
All that said, I do agree with some other comments on the thread regarding the disappointing reliance on JavaScript here. Should just be static.
I wonder why Sandi Metz is missing in the testimonial section. One of the most influential persons in software analysis and design in the Rubyverse.
Sandi is also "moderately retired" -- hasn't done a speaking engagement in 5 years -- a blog post in longer...
Sometimes it's nice to just let people rest and get on with life.
Had the same exact thought. That DHH was included and Sandy was not really surprised me.
DHH is the lead developer of the most popular ruby web framework, Sandy is the author of a mildly popular book. Not knocking her work, but DHH is magnitudes more influential.
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, is a living organism!), instead of being frozen in amber for a decade like the last version!
[flagged]
[flagged]
[flagged]
[flagged]
Not sure if you got the memo but we aren’t cancelling people for their political views anymore.
That’s not really a thing anymore.
Just because you don’t agree with his views doesn’t make it “not a good look”.
In fact, the ability to think outside of his cultural bubble and go against the grain is something that makes him great.
I mean, you're allowed to think an ethnonationalist has a consistent and reasonable worldview. That's absolutely ridiculous but you're free to think it. Nobody's cancelling anyone.
But having DHH as a face of your programming language, a language that's supposed to have a "warm community", doesn't really make any sense, and it will obviously drive people away.
Being critical of MENA migration is not hateful speech.
Hateful speech is stating: you are from a MENA region therefore you are x negative trait.
Being critical of migration is just being critical of migration, which is allowed. His defence ("suicidal empathy" etc;) comes from the situation in the UK where people are being arrested en-masse for "hate speech" for referencing acts of terror[0].
You can dislike what he says, but hateful carries a more specific meaning (to me, at least).
[0]: https://nypost.com/2025/08/19/world-news/uk-free-speech-stru...
He did imply that brown people are rapists, and that transpeople bad. So he also fits your definition of hateful.
In "As I remember London" he also says that crime increases when there are more brown people.
I think he backed his citations, and just because migration from MENA regions (a historically entirely different culture) are “brown people” doesn’t make it invalid. Mexicans are also brown people and so are Spanish people in some definitions. Yet somehow he’s not talking about them. If you look closely he’s criticising the kids gloves that the authorities are handling the newcomers that leads to a worsening narrative for everyone- lets not forget that there are victims in both camps here.
We should be able to criticise migration without everyone saying it’s racism otherwise you loosen the definition of racism so much that everybody becomes a “racist” eventually and it stops having a sting
He did not back those up. He provided anecdata about a single "Pakistani rape gang" story, but the actual statistics say that child sex crime "gangs" are predominantly white [1].
You're allowed to criticize immigration, but if you only ever cherry-pick anecdotes about immigrants of a certain color and creed, and also refuse to correct your statement after you're made aware of the actual facts, you're most likely a racist.
DHH is also not criticizing immigration per se, because he's including non-white native brits in his category of undesirable Londoners. You can't deny that that's racism. These are people who grew up as part of the British culture, they just don't have the right skin tone.
[1] https://web.archive.org/web/20251003224438/https://assets.pu...
I appreciate the thoughtful response and the commitment to facts. Racism has no place in these discussions. Let’s examine the points with nuance, drawing from the cited report and context. On the Home Office Report’s Statistics The 2020 paper states that group-based child sexual exploitation (CSE) offenders are “most commonly White”.[0]
However, it highlights major data limitations. Ethnicity was often unrecorded or incomplete. Police forces supplied partial details only. The report notes that “the academic literature highlights significant limitations to what can be said about links between ethnicity and this form of offending”.
It also cautions against conclusions due to “data quality problems, the way the samples were selected in studies, and the potential for bias”. A 2025 audit by Baroness Casey confirmed this. Ethnicity went unrecorded for two-thirds of suspects. Better data collection is now mandatory.
While the report leans towards White predominance overall, it acknowledges high-profile cases “have mainly involved men of Pakistani ethnicity”.(also in[0]) It does not rule out over-representation in specific subtypes. This invites careful interpretation rather than dismissal.
On Cherry-Picking Anecdotes and Corrections: Selective stories can mislead. Yet DHH often cites aggregated data from European reports, such as Denmark’s figures on higher crime rates among certain immigrant groups. He praises selective immigration from compatible cultures and commends Denmark’s integration policies. This points to policy focus, not inherent bias.
If presented with the report’s full nuances and unmoved, that warrants critique. Given its caveats and recent calls for improved data, the debate remains open.
On Non-White Native Brits and Racism; Implying Britishness ties to skin tone is wrong. DHH’s remark about “Brits being a minority in their own capital” refers to the “White British” census category, at 37% in London per the 2021 census. This tracks ethnic shifts officially.
Non-White British citizens, many native-born and fully integrated, are undeniably British. If his phrasing suggests otherwise, it needs clarification. His posts emphasise rapid changes from mass immigration, not rejection of integrated individuals. Many non-White Brits voice similar concerns on resources and cohesion, without racism. Criticising policies can be valid if evidence-based and non-dehumanising. Targeting one group without balance risks bias. DHH’s stance seems data-driven on integration, but scrutiny is fair.
Thanks for the source though.
[0]: https://assets.publishing.service.gov.uk/government/uploads/...
You say non-white British citizens are fully integrated undeniably, but somehow you still determine DHH to be data-driven, even though he implies they aren't, by tracking the "White British" ethnic category.
You even mention this, although for some reason do not comment on how it's clearly racist and misleading.
So I have to conclude you're either waffling, or you're pasting ChatGPT output without parsing what it means. Because if you apply your own logic, you would come to the conclusion that he's using far-right talking points to further far-right, racist views.
edit: I thought I recognized that name, you've replied to me previously with LLM-ish output. You're the weirdo Malmö guy with racist irc chat logs (this you? https://darkscience.net/quotes/#123). I mean granted, their ten years old. Men fan pinsamt ändå. Och med eget namn också, Jan Harasym. Inte vassaste kniven i lådan, va?
So, in order to show a single download link it needs to load an animation with visible loading progress even on a gigabit connection. It takes a few seconds to appear. All to show a scaling animation that can be achieved with a couple of lines of CSS.
Same for absolutely static code examples that take a few seconds to load and shift the content away.
Why?
You are a rare species, on the verge of extinction.
Unfortunately, most people today probably don't care about what you're talking about. (I do, but I've decided not to comment on it anymore, because it would probably drive me crazy :)
The site is for developers and most of the rare species are developers.
The designer fail to target their audience.
Ruby is not targeting those kind of developers though.
It's C/C++ developers that typically prefer a no-fluff approach.
As polyglot developer, I am also for a no-fluff approach and vanilajs for the win.
One of the reasons Next.js is attractive to me, is exactly they have rediscovered why so many of us have stayed with SSR.
> no-fluff … Next.js
Hmm. We can agree to disagree on the definition of fluff.
Sure, if you ignore the SSR and SSG part, which sadly most nodejs stuff lacks.
Additionally, Next.js should only be used when SaaS product vendor doesn't allow for any other option, which sadly is the case when making themselves sellable to magpie developers, while riding VC money until the IPO takes off.
I rather deliver, than do yak shaving, but at least can deliver only HTML and CSS if I chose to.
> couple of lines of CSS
This is bit too much to ask. Just check the source it is swollen with Tailwind.
Interesting, never seen "swollen" used to describe code bloat, but it creates powerful imagery now that I read your sentence.
Tailwind maps directly to CSS (well, it is pure CSS) and doesn't require a loading progress for a one-line animation: https://tailwindcss.com/docs/animation
Sure but if someones duplicates 50x this:
> flex-shrink-0 transition-transform duration-300 hover:scale-105 w-[160px] h-[144px] 2xl:w-[200px] 2xl:h-[180px]
just to avoid CSS, not sure they would bother with CSS animation.
wow that loads slow
I like the design and content. Being able to immediately try a language online is huge
But there has to be a way to load that content in a progressive manner. Loading a static version first and then hydrating the content if you need interactive actions
It's as fast as HN for me.
If you break out the Lighthouse perf score it's more visible. It's between 2 and 3 orders of magnitude slower than HN for me.
Nice! There is a Japanese feel to the lead graphic, their prevalence of cartoon imagery, that one might not recognize without having traveled in Japan.
Is the design debate public? I'd imagine it would make great reading.
The top right character definitely looks like Matz!
Is there a manifesto out there saying that one should build with html and only if needed add css then svg then js?
It seems this site doesn't work so well without JS.
I think this is the first time I've seen a website where the download button, which is just a link, requires JavaScript to render.
The site looks great visually but the technical implementation is disappointing. Here's what's wrong:
1. 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.
I don't get the people who complain about the website not working with disabled js. Maybe I miss something and a large part of users disable / have js disabled in their browsers for some reason? Why the target audience of the ruby, probably primary web developers, whould do that? Or is this a some kind of secret handshake so community accept you (to build a website that can work with no js)?
Back in the 2000s in the web standards development community there were multiple web development strategies called "progressive enhancement", "graceful degradation" and "unobtrusive javascript":
https://en.wikipedia.org/wiki/Progressive_enhancement
There were a lot of practical reasons for that: The browser landscape was much more diverse, different browsers had different support of standard Javascript, some browsers didn't even support JS and some people still kept text-only browsers like lynx/links in mind. Also browsers were not evergreen, so a large part of the audience could be on some older versions. Another thing were sometimes brittle network connection, especially over mobile. Depending on JS could in the case of corruption mean non-functioning websites.
For a lot whose exposure to web development and the discussions abound that, that reason will be stuck in their head, even if in the last decade of React ets the "best practices" will have changed.
There is also an aesthetic thing: There is a thing of beauty in simply curling an url and piping it into grep or such to get the thing you need, instead of having so have an headless browser. In my mind that is still how the web should work.
It's become a bit of a shibboleth to have js disabled, and brag loudly about how that breaks much of the Internet. It's a weird form of nerd signaling
It's a common philosophy for developers with standards of robustness and accessibility to not hard depend on js for things that don't need js to function.
> Why the target audience of the ruby, probably primary web developers, whould do that?
In my experience, it's mostly web developers who care about this in the first place.
> mostly web developers who care about this in the first place.
I’m not sure what you mean by this. We care about our users and how they use our websites. JavaScript is everywhere and has been the de facto frontend standard for the past few years. Supporting no-JS is starting to feel like supporting a new browser. As much as I’d like to, from a business and product point of view, the numbers are just too small for us to even consider it.
I didn't imply that all web developers care about it, but that most of the people who care about it are web developers. I won't deny that it's still a minority.
I can understand the aspiration to have the system that can be run from the lowest level out of box tools, but then, I am doing frontend for almost a decade and this is porbably the first time I'm seeing such attention to this specific 'no js' use case, as in this thread.
Maybe I'm not reading enough webdev forums. I agree though that things that don't required js should be written in no js way.
Very form over function, with JS for everything, including static content, and bad performance. This signifies what’s wrong with “modern” webdev.
So much better. The website was looking like abandonware, which was not helpful in projecting ruby as an actual thriving ecosystem.
I see that this coincides with Ruby 3.4.8 release[1]. I wonder we will get another Ruby release on 2025-12-25, since Ruby has made a Christmas day release for 13 consecutive years[2].
[1] https://www.ruby-lang.org/en/news/2025/12/17/ruby-3-4-8-rele...
[2] https://www.ruby-lang.org/en/downloads/releases/
yeah it will be ruby 4.0
It looks great, but it's missing the one thing I want most in the site - the ability to select the version of the language documentation in some way other than editing the URL directly. I use ruby-lang almost exclusively for the documentation.
I also wish the documentation search parameter were saved in the URL. This would allow people to create a custom Chrome search engine like @ruby and dramatically speed up doc searching.
The Lighthouse report is telling. It scores 100% for Best practices and SEO, but 54% for Performance. Pages like these used to be caricatures of the modern web, but are now acceptable. DHH's statement doesn't help either.
I dreaded the thought of scrolling down because I knew I’m gonna stumble upon his face.
the only thing his statement was missing was thank you for your attention to this matter
Honestly, the synthetic Lighthouse tests would be great but for the fact that they're using Google Fonts. It's like the only major thing in their critical path.
Ruby is GOATED. You can say what you want but Ruby coupled with Rails is the most productive web stack period.
Why you might ask? - Omakase Stack - high level is good for business processes - modern concepts without JS ecosystem churn - great testing capabilities - great ecosystem - highly effective stack for LLMs (conventions)
Is it fast in Benchmark Games - not by any means. Will you be able to finish projects and make money with it? Absolutely.
[dead]
I'm glad to see they didn't use wordpress.
I find this distasteful:
Do it properly with quotes you lazy people :)EDIT: typical ruby (on rails) code: saves a few characters, breaks readily (Hint: consider "New Orleans")
The number of times Matz is mentioned and depicted on the homepage is offputting. MINASWAN feels too close to WWJD for me. I can't think of another programming language community that does this, and I'm including Wolfram in that assessment.
In C++ we just constantly bash the committee for its bad decisions and pretend we would've done better than Stroustrup.
Seems like a more grounded and healthier approach to programming languages.
The old site as a comparison.
https://web.archive.org/web/20251113164224/https://www.ruby-...
That's certainly less fancy and looks outdated, but it's a lot more functional.
Outdated meaning not flashy, but the layout is great. Here's what this is, here is are news, here's all the resources you need to get started.
Very nice, my nature-lang references the old ruby design, now maybe I can reference the new one.
Feels like base camp website.
Haven’t seen a loading progress spinner on a landing page in a while. The Ruby website now loads almost as slowly as Ruby on Rails boots up.
Awww... I really love it, not that it wasn't good before, but really nice to see refresh.
Well well well. Now can we stop arguing about ruby death? It is even got a site redesign! What a fresh look. Previous design was from 2005?
The visual refresh is great, but the technical implementation is disappointing. Code examples are static text fetched via JavaScript instead of being in the HTML. With JS disabled, you get a frozen "0%" loading screen.
This is ironic because Ruby has always emphasized doing things "the right way" and developer happiness. A language website should be a poster child for progressive enhancement - especially one that champions elegance and proper practices.
Still, huge improvement over the 2005-era design. Just needs optimization work to align the implementation with Ruby's philosophy.
I loved the old website. It was one of the few "good old things" I used to check out when I got nostalgic. What a waste...
Lol, it does not load when JavaScript is disables. I wonder if Ruby still sticks to Free Software principles.
Looks like base camp website.
Bad branding community wise to quote DHH on the frontpage. Will immediately turn away many. He isn’t worth wasting the reputational loss that comes with printing his words.
I'm outta the loop; what did DHH do or say to invite the wrath of the Kraken?
He acknowledges that mass importing Muslims into the UK is killing the country.
For some reason there’s a large swath of people who really don’t like people saying that.
I assume you are quoting the Great Replacement theory, which is a whole bunch of far-right nonsense. Or maybe people extrapolated his statements to that, then the Kraken was unleashed.
The irony of the inclusive imagery above DHH's head.
DHH praising himself in the testimonials, funny.
On my iPad, without scrolling, the screen shows almost nothing, just a download button and some text that, I think users will ignore. I think that’s a waste of valuable screen estate.
Also, apart from a quote from David Heinemeier Hansson the home page doesn’t even mention that ruby is a programming language.
For comparison, the following all mention that above the fold, with a short phrase indicating what you would want to use the language.
- https://www.python.org/ has “Python is a programming language that lets you work quickly and integrate systems more effectively. Learn More”
- https://www.perl.org/ has “Perl is a highly capable, feature-rich programming language with over 37 years of development”
- https://www.php.net/ has “A popular general-purpose scripting language that is especially suited to web development. Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world.”
- https://www.swift.org/ has “Swift is the powerful, flexible, multiplatform programming language. Fast. Expressive. Safe.”
Funny how these statements seem to preempt alternative descriptions, misconceptions or criticisms.
Python is pretty well known as a data, analytic and machine learning oriented language, and they lean into a more broad characterization.
Perl might be described as dead/dying, and they characterize its development as ongoing.
PHP might be described as a web scripting language, and they characterize it as general purpose and broad.
Swift might be described as an Apple platform a language, and they really want us to know its multi-platform.
That’s not funny; it’s good use of the most prominent part of the site.
A site (re)design starts with determining who’s your audience, and what you want to tell them.
These sites will want to serve both existing and new developers.
What they want to tell them will be different for the two groups, but the existing ones won’t be chased away by a short description aimed at newcomers, but newcomers can easily turn away by the lack of such a description.
As to what to put in the description: it sort-of is an advert, so you often don’t exactly say what you are, but more what you want to be.
https://www.swift.org is a clear example. They definitely want to tell everybody that Swift is multiplatform, giving cloud services, command line tools and embedded development more prominence than iOS apps.
I think they do that particularly well, much better than this ruby site (https://www.ruby-lang.org/en/)
For example, on the swift site, they claim ‘embedded’. If you click on that, you get examples for various platforms such as Raspberry Pi and STM32 (https://www.swift.org/get-started/embedded/). That allows you to verify that claim.
In contrast, this Ruby site makes claims such as 'Easy to write, easy to read. Natural syntax like spoken language’, 'Do more with less code', but it’s not easy for users to check whether that’s true.
[dead]
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
Please don't fulminate or initiate flamewar about programming languages – of all things – on HN.
https://news.ycombinator.com/newsguidelines.html
Really? I thought GitHub and Shopify used it. Hard to imagine billion dollar companies choosing an unserious language to power their businesses.
[flagged]
What happened in 2017?
They lost interest in Ruby
Also Fyre Festival
I did. It just wasn't cutting it for me. Technology wise you can do so much more with Rust and recently Python (3.14+).
[flagged]
> somehow, the Ruby community [...] think it's acceptable to have a standard implementation that does neither AOT nor JIT native code compilation
Ruby have YJIT, which is a production ready JIT compiler that generates native machine code. But it requires enabling via flag "--yjit" rather than running by default.
Why? I think it's primarily to avoid build time dependencies on Rust and prevent unexpected overhead for users. This keeps binary light and avoids forcing Rust installation on users, especially for those who run interpreter only, where YJIT adds no value.
Note that including YJIT also bloat binaries by 5 to 10MB (Rust static lib + code cache structures) for source builds and complicates cross compilation since Rust targets vary by architecture (focus x86-64 and arm64, not all platforms).
Also, Rails 7.1+ enables YJIT by default, so JIT (to native code) in Ruby is being utilized when actually needed.
Do you often rant like this based on completely incorrect info? Could save yourself some time and downvotes by doing basic research first.
Ruby has had YJIT for some time and being deployed and used in production, from Github to Shopify.
The current experimental JIT is ZJIT. And the fastest Ruby JIT Runtime is TruffleRuby. ( I wish JRuby gets more love )
Putting DHH right next to Matz must be some kind of sick joke
Quickly followed by folks talking about a warm and welcoming community. Which in fairness, is true! DHH is the counterexample. Platforming him in 2025 seems nonsensical.
Why is platforming him in 2025 nonsensical?
Because he said things that some people on the internet interpreted as mean, so therefore he’s mean and we should never associate with mean people.
Ah yes, the "fuck your feelings" reductive response.
But no, what I meant to get at is that DHH's ego is radioactive. RailsConf tried to open their keynote to having Maybe Perhaps Someone Else Talk Sometime and DHH's response was, as it were, [off the rails](https://world.hey.com/dhh/no-railsconf-faa7935e). RailsWorld started the next year and, happy to have DHH keynote, took off. RailsConf swiftly died.
If you're running an ecosystem with a vocal community, is that a fire you want to play with?
The guy that started Rails wants to keep giving the keynote.
I’m having a hard time seeing the crime against humanity here.
platforming him at all is nonsensical if you want to claim to have a kind and/or welcoming community
So your claim is, that he is not a kind person. Were his blog posts that inflammatory?
His posts, his statements, his treatment of other people, yes, he advocates for things which cause harm to others. The term is stochastic terrorism. He creates a welcoming space _to people who are accepting of his bigoted ideology_ which gives some nice publicity, but is not creating a kind and welcoming community.
This is just straight-up unappealing, really gaudy, if that's the right word. Otherwise I can't put it into words well.
I really wanted to like Ruby, but the ecosystem is just... broken.
Comparing to Python, where virtualenv is de facto default, and pyls works by default, the experience with Ruby is not that great.
New website looks like a website for a startup project that will be closed in 2 years.
What is broken in your mind? What things did you have a "not that great" experience with? There are de facto standards and defaults in Ruby as well.
Well, for starters, I never got LSP to properly work with Ruby at the same level as other languages, i.e. so it's possible to browse the standard library.
Which LSP are you using? I'm using both solargraph and ruby-lsp and both works fine by me (in neovim).
Although those who really care about LSP support usually will use RubyMine IDE instead. Some of my colleagues are going that route, and they're mostly coming from Java (or similar background)
I'm not really "using it", I'm just trying every now and then, and I keep encountering errors, hangups, and lack of functionality. Now I've tried ruby-lsp, and it just sits there on "Starting Ruby LSP...\n"
Couldn't even install Solargraph, once it errors out with 'Kernel#require': cannot load such file -- yard, other time it installs, but "solargraph scan" fails in runtime with "missing gem date" error.
Sorbet doesn't even work in VSCode, some bugs are over 5 years old.
But yeah, downvote my original post, because apparently all of the above is obviously my fault.
RubyMine was paid until recently, now it's free only for non-commercial use. It's also not really suitable for small scripting.
Historically, one insanely huge advantage of Ruby was that it was pre-installed on macOS'es, but I think they've stopped doing that since some macOS version.