Or Stockholm Syndrome

You’re not wrong, but not everything needs to scale to 200+ servers (…arguably almost nothing does), and I’ve actually seen middle managers assume that a product needs that kind of scale when in fact the product was fundamentally not targeting a large enough market for that.

Similarly, not everything needs certifications, but of course if you do need them there’s absolutely no getting around it.

In case you’re still interested in this type of resource, here’s another one I just learned about: https://google.github.io/comprehensive-rust/

It’s by the Android team at Google, and while it doesn’t require knowledge of C++, it seems to be intended to bring devs up to speed on the concepts required for using Rust in Android and Chromium.

Wow, I definitely should have google that myself before asking, but thank you for explaining and calling out that data point.

I honestly think that shows that it was in fact a bad idea to assign TLDs to countries. Having a country code acronym with a popular tech meaning is essentially just luck of the draw, so they’ve basically just arbitrarily given a few small countries a valuable resource to sell. I guess that benefits those countries, but I doubt “quasi-random fundraising for small countries” was ever the intent.

But do they actually have autonomy, give that random companies can use .io and .ai? Or did the British Indian Ocean Territory and Anguilla approve all such uses of those domains?

Why top-level, though? Why not amazon.in.com?

Obviously this isn’t specific to Rust, but frankly it’s bizarre to me that ICANN chose to tie top-level domains to country codes in the first place. Languages might have made sense, but a major feature of the internet is that it’s less beholden to political boundaries than most of the physical world is.

Yep, learned it recently from a list of things that are, surprisingly, named after real people. Deb and Ian eventually got married but are now divorced.

It’s so out of date that Deb and Ian are no longer together

(…this is actually true, not just a joke)

But “drop-in replacement”? That’s a strong and specific claim.

I do actually think that WebAssembly will enable something - maybe Rust, but more likely something simpler - to eventually dethrone JS in the browser. I also do think it seems beneficial to have your client and backend in the same language.

… the issue I have is people lying and saying Rust is a drop in replacement for js

I am genuinely curious whether you’ve actually seen this claim before, or if you badly misunderstood or are simply exaggerating a claim about Rust being a good language for web servers, or if you simply made this up as a straw-man. I can’t imagine anyone who knows what they’re talking about using those words I that order.

But how does the alternative solutions compare with regards to maintainability?

Which alternative solutions are you thinking of, and have you tried them?

Rust has been mentioned several times in the thread already, but Go also prohibits “standard” OOP in the sense that structs don’t have inheritance. So have you used either Rust or Go on a large project?

The O’Reilly book Programming Rust is very much targeted at C++ users, even if it isn’t explicitly marketed that way.

I read the first edition, which predated async Rust, so I can’t comment on how the second edition handles that topic. But the handling of everything else was, I think, excellent.

🤷 That wasn’t my experience, and I used it as my primary dev environment for four years.

It doesn’t go through a translation layer, though. WSL 2 has a whole separate kernel. You can even use GUI apps with Wayland.

For what it’s worth, WSL 2 with VSCode is actually great. Almost all the benefits of Linux (I still miss true tiling window management), with fewer weird driver issues.

That said, I generally just use whatever my company wants me to use, and I haven’t worked somewhere that let us use native Linux boxes since 2014.

Modev says they’ve been using C for 25 years, and used Rust for several years as well! Their whole schtick baffles me.

I also hope that some of the people reading this realize that OP is also the person posting all of the “stop trying to suppress C” posts.

Every technology that gets used frequently enough facilitates maladaptation to its faults. 😑

I’m no expert, but isn’t running in a VM strictly better than running on raw metal from a security perspective? It’s generally more locked down, and breaking out of the virtualization layer requires a separate security breach from gaining access to the running container.

Rust feels like entirely the wrong target for that sort of criticism, especially regarding “energy and resource intensity”. Rust is well-known to be comparable to C in its efficiency.