3 ms·
> If nobody was happy, then the new site wouldn't have been deployed. This is an incredibly simplistic view of how projects work. On any large project, there a
by steveklabnik 8y ago
> If nobody was happy, then the new site wouldn't have been deployed.
This is an incredibly simplistic view of how projects work. On any large project, there are a number of objectives, with different priorities. And there are a number of factors, some public, some private, as to why projects end up the way that they do.
I am the person who implemented the original i18n support. It took me a year of effort to get it shipped. I do care about this. That's not incompatible with what's occurred.
> "nobody really cared, because English is their primary language, thus they aren't affected at all"?
Even if English is a primary language, that doesn't mean we aren't affected. For example, not shipping it means that I have to be embarrassed and apologize when people on the internet point out this shortcoming. Not shipping it can limit growth, as you point out. There are tons of ways.
> I don't understand why the deployment could not have waited until the translations were completed.
The original way of doing i18n was completely untenable. Doing it a better way takes time and effort. That's before the translations are actually made. That work has been ongoing since December of last year. It's getting pretty close now, with a lot of movement recently.
- intertextuality 8y agoSo aside from you, nobody on the team cared about i18n enough to actually get it implemented before deployment–it wasn't a priority. Got it. Sucks that you're embarrassed but it looks like an organizational failing to me. I would never "upgrade" a website from having i18n to not having i18n. > Doing it a better way takes time and effort. New method or not, deploying the website could have waited until even a few languages were translated. It's not like the old site was bad, what was the rush? edit; Nobody here is answering my question: why was it deployed with removed functionality? Why could the old site not have stayed up longer until a few languages at least were translated? You say things like "nobody was happy" but I'm wondering why it was deployed at all if nobody was happy. Is this a side effect of too many committees and deliberation? Why are we sitting here going "sucks that I have to explain this to people" when it could've just.... waited? Nobody would have noticed if the old rust site had stayed up for another year? two? and now I'm characterized as "mad" because I respond to HN comments. No, I just care about i18n, I'm just wondering why a website had to be deployed so badly that something as important as i18n was removed. Good for us because we speak English, am I right? edit 2; The reason I have written so much here is because I thought the Rust team was capable of quality, so I hold it to higher standards. For the website, it appears that I was mistaken.
- steveklabnik 8y ago> So aside from you, nobody on the team cared about i18n enough to actually get it implemented before deployment–it wasn't a priority. Got it. It's not a matter of care; it's a matter of time and stuff to do. There are a lot of people willing to get extremely mad about the website online, but few people who are actually willing to step up and do work. That's the limiting factor on getting stuff done.
- dang 8y agoWould you please not argue in the flamewar style on HN? It's not what this site is for, and it damages the curiosity that it is for. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- intertextuality 8y ago> but few people who are actually willing to step up and do work. That's the limiting factor on getting stuff done. That's why waiting is also an option. Feel free to excuse it however, but removing i18n here was a pretty big mistake on the rust team's part. For what? Rust 2018? I didn't contribute to the website, but I also didn't force anyone to change it either. > There are a lot of people willing to get extremely mad about the website online I'm not mad, I'm just disappointed. It's rare to see actual i18n for open source projects, and it's absurd to see it get removed arbitrarily when it does exist. I believe the Rust team is capable of delivering much better quality updates, hence my writing here. I'm also sick and tired of i18n being considered an afterthought by people who do have the resources to accomplish it to at least a basic degree. Also, just because something is open source doesn't mean "well why don't you just go do it then" is a valid argument. It isn't.
- steveklabnik 8y ago> I'm not mad, I'm just disappointed. Regardless of you, it's true in general. There has been a lot of heat, and it's damaged the ability to actually improve the site. > Also, just because something is open source doesn't mean "well why don't you just go do it then" is a valid argument. It isn't. It's not an argument. It's a description of reality.
- iopq 8y agoNobody liked the new site and there were a lot of complaints about the design. Why was it deployed before feature parity?