Live data from Hacker News

Ruby website redesigned

ruby-lang.org

131–140 of 224 posts

Re: Ruby website redesigned

#131
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.

Re: Ruby website redesigned

#133
post #126
post #103

Earlier quoted context omitted.

> 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…

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.

Re: Ruby website redesigned

#134
post #132

Earlier quoted context omitted.

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"?

Re: Ruby website redesigned

#135
post #126
post #103

Earlier quoted context omitted.

> 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…

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.

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.

Re: Ruby website redesigned

#136

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.

Re: Ruby website redesigned

#137
post #39
post #36

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

Re: Ruby website redesigned

#138
post #80

Earlier quoted context omitted.

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?

platforming him at all is nonsensical if you want to claim to have a kind and/or welcoming community

Re: Ruby website redesigned

#139
post #74
post #19

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.

Re: Ruby website redesigned

#140
post #132

Earlier quoted context omitted.

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]
Post reply on HN