Evening Newbs

Benchmarks mean nothing.

You’re free to suggest another method of comparing the two languages’ performance. This is the best we’re have, and Rust wins in every single benchmark shown there.

These aren’t the results of code written by an average programmer.

Citation needed.

I like Rust and all but we do need to admit it doesn’t magically solve all our problems.

I never said it did. I simply pointed out that it’s demonstrably faster than Swift.

Citation granted.

If it’s “barely a problem in practice” why did you bother to mention it like it’s an active performance issue?

This post is so full of inaccuracies that I don’t know where to begin. I’ll just mention the first thing I noticed: just because drivers are compiled with the kernel doesn’t mean they’re all loaded at runtime. modprobe exists for a reason.

Incorrect. If you aren’t using WifiManager, you don’t need ACCESS_WIFI_STATE or location permissions. ConnectivityManager gives information to know the connection type with only ACCESS_NETWORK_STATE, which is granted automatically on install without prompting the user to allow.

And besides that, you should really be checking ConnectivityManager.isActiveNetworkMetered() instead of the connection type anyway, since the user could be on tethered wifi, for instance.

You can determine if there’s an active Internet connection without checking the wifi info.