I suspect that, programming in Rust is so onerous, that Rust programmers must take lots of breaks and troll Go threads so they feel less bad about themselves.

Or maybe they're just waiting for something to compile?

To be fair, I remember thinking the same thing when Go was new. HN was pretty dominated by everyone apparently switching to Go (if you were to believe the general attitude anyway) and how Go was the clear path in the future

Not that it is or isn’t and clearly Go does things really well in some problem spaces but yeah, this seems to be a common theme for all young languages

I do think some members of the Rust community Take it waaay too personally, which I never saw in general when Go was the hip thing. That I agree can be very obnoxious

Same with Nodejs, and same with Ruby when the Rails craze. That's us devs.

Oxidation Factor: Inversely proportional to the amount of time before a comment brings up the superiority of Rust.

Go has a pretty high oxidation factor.

Oxidation (noun): the act or process of shoehorning Rust into a comment thread

Well it's pretty relevant when considering a new feature for a language to consider prior art is similar languages (the key similarity in this case being the compilation model), no?

No, it's not relevant. There's no considering being done, the feature is being shipped. Please stop with the Rust spam.

Your comment itself should be codified. Maybe it’s just another growing language with a large community that itself is dedicated to improving the language. Rust is newish, and changing rapidly so it’s a good candidate for comparisons between modern languages. It helps that it’s designed completely in the open so the sauce can be seen.

Not to pick on you or even the other child comments but the amount of people that complain about a language being compared to a modern equivalent is funny. What about every other thread on HN where the same thing happens? It’s alll turtles just enjoy the discussion

Nah, there's something unique about Rust zealots in this respect. nicoburns comment is completely off topic, and it's extremely obnoxious to see this kind of thing over and over again from the Rust community. And I even like the language!

There is certainly a low how Go community rejects proposals, criticism, comparison and a healthy chunk of its users.

Generic compile time evaluation is an interesting feature, better than magic comments in my list. Though in this case it is compiler built-in [1].

[1] https://doc.rust-lang.org/src/core/macros/mod.rs.html#1122-1...

The Rust promotion has unfortunately changed lately. I've noticed too that they not only tell everyone how great Rust is (which is fine) but started bashing other languages (which is sad and not doing any good for the public image of Rust).

Rust is from enthusiasts for enthusiasts. If the Rust community wants it to become more real / main stream, they need to look at how the Go team focuses on supporting devs for getting things done correctly with long term stability.

If you prefer I can provide examples on how Windows, macOS/iOS, Android resources work for their native language SDKs, or how Java and .NET embedded resources work.

I'm actually interested… (I'm quite limited to Apple's bundles) would you mind writing a blog post ? :)

No time to write blog posts, but I can provide you the links to the documentation,

Java Resources - https://docs.oracle.com/javase/8/docs/technotes/guides/lang/...

Android Resources - https://developer.android.com/guide/topics/resources/providi...

.NET Resources - https://docs.microsoft.com/en-us/dotnet/framework/resources/

Win16 and Win32 resources - https://docs.microsoft.com/en-us/windows/win32/menurc/about-...

UWP resources - https://docs.microsoft.com/en-us/windows/uwp/app-resources/

C++ helpers for Win32 resources - https://docs.microsoft.com/en-us/cpp/windows/resource-files-...

Given that you mention bundles, Java's resource management shows the influence of Objective-C in Java's design.

The Rust community does have an uptight attitude, as if Rust's success or lack thereof is a matter of life and death. This can be seen in general with languages which haven't achieved wide-spread success yet.