Hacker News Reader

Comment by intertextuality | Hacker News Reader

That's a very dumb reason to ditch i18n. Waiting before it finalized wasn't an option?

As far as I can make out, the new website was considered a key part of the "Rust 2018" project, and so the maintainers chose to launch it before it was really finished (and without the planned period for user feedback), at the same time as the Rust 2018 release.

Evidently it wasn't quite such a key part of the project that they could consider delaying the new Rust edition until the website was ready.

In hindsight tying the website update to the new edition was quite possibly a mistake. The Rust core team has asked people to hold off on discussing the process or proposing major changes until they've published a retrospective on what happened (that was five months ago, and the retrospective is now "mostly finished").

Thank you for explaining it. I now finally understand why it was deployed with removed functionality.

That said, that is a completely idiotic reason to remove something like i18n. Unbelievable.

I wish I could say I don't understand how this got approved by multiple people, but the sad reality is that nobody makes internationalization a priority. It's completely normal to not have the other languages I use to not be supported, but I guess it stings to actively have it be removed.

Instead of yelling at people who weren't involved with the decisions and are only providing context, maybe go write a calm series of bug tickets explaining your concern, or better offer to and follow up on helping with i8n support?

So raising a point on a random internet post is now considered "yelling"? Interesting. Also, I called "that reason" dumb. Perhaps you're personally involved with the project, but please try to read things as they are instead of taking offense unnecessarily.

Counterargument: How about one doesn't remove stuff like i18n in updates? Or what about simply delaying the deployment until the i18n and other features are done? Or is removing support for other languages considered acceptable if the new, English only, website looks very pretty? [tone is of light sarcasm]

Counterargument #2: just because something is open source doesn't mean you can go "well, just open a ticket or do it yourself". No, how about people in general update things properly (or at the very least, don't remove translations)? I'm perfectly allowed to criticize removing important functionality like i18n. It was there, now it isn't, and I didn't make the choice to remove it. It's not my job to do other people's jobs for them just because I exercised my ability to criticize something. Otherwise I would be working on GUIs/UX for open source linux projects until I die. [tone is of exasperation in open source software development]

You might have misunderstood the sentence's tone.

Reply on news.ycombinator.com