I don’t doubt that some places care about a 1MB size difference. After all, some embedded systems with limited storage need every megabyte they can spare.

There are only going to be edge-cases where the binary size will really cause headache. Individual projects probably won’t worry too much about a size difference if it’s less than 10-20MB.

Some of the notes highlight that performance differences in specific tests were due to AVX-512 support. I’d like to see a post going into detail about what challenges the libraries (or their dependencies) went through to get that integrated and how much of an increase came from it.

we use different search engine so you didn’t find this particular hit

Tangential due to personal curiosity, but which engine did you use? I was testing via Google while logged in. Most of my development at work and at home uses Python with some Rust once or twice a month. I just realized that when I’m searching I usually am not looking for books to purchase but instead trying to find answers in forums or Stackoverflow. Perhaps the reading material was not presented as Google was trying to personalize results to match my search habits.

I was a bit cranky

As was I, and I apologize for that since it triggered all of this.

I’m quite fed up with the attitude that it is someone elses obligation to spoon feed you with knowledge that exists right under the nose

I suggested it in response to someone else’s comment, but I believe part of the issue is a lack of a polished collection of material aimed towards newcomers from particular languages. By that I mean there’s definitely volumes of “good” material, don’t get me wrong, but learning from them individually doesn’t necessarily help with understanding how to think and plan things out with a Rust mindset.

In my own journey I’ve found many guides, posts, and videos that help you get launched into writing basic code. However I struggle to discover ones that go beyond the code to plan and anticipate pitfalls you normally may not encounter from another language. I brought up static lifetimes because halfway through coding a multithreaded project I’ll get an error about this or a struct being partially moved. At which point I would need to refactor things somewhat to make the compiler and borrow checker happy, but mentally it didn’t make sense as to how to correctly do so with what I sought to achieve.

A community-compiled collection of resources that guides you in your journey from Novice to Expert would probably help stem the tide of requests people make for getting into Rust. The official YouTube channel has some interesting videos from conferences but nothing that walks you through proficiency. And the forums, as far as I can tell, don’t have something pinned for users to point towards when someone asks the same thing.

Perhaps if people are asking to be spoon-fed when a lot is available, we should be asking them if they’ve tried to search and why they need help looking for more. Maybe it’s not laziness; perhaps there’s something specific they can’t quite find that helps fill in the gap of their understanding, and we should work towards making those resources easier to discover autonomously.

I didn’t say they were bad. I was pointing out that:

1. Blaming a user for not hitting the same results on search engines is a flawed argument; my search did not present the book that was linked in the original comment, even while using the title of the book as the search phrase. It instead was a mix of forums, social media, and YouTube tutorials, all of which do not have the same depth as a good book.
2. The material presented in some of the “Rust for C++ programmers” videos and posts focused more on direct translation of syntax. This is good “first step” material to make the user more comfortable, but again they didn’t cover the common pitfalls that a C++ developer will encounter when they’re still approaching Rust with a C++ mindset.

That said, the guide you’ve shared was in fact on the first page of my results, and is definitely a good example of the type of content that is available. What I think should take place is a compilation of similar guides and books to be posted either in the Rust forums as a pin or a YouTube playlist in the official channel, perhaps even with a small list of suggested crates to review the source code of as pristine examples.

There are lots of guides, tutorials and documentation.

is one I found using a tool called search engine…

Strange. That’s not what I get when I search for “Rust for C++ programmers”. I get flooded with anecdotal accounts/posts from people on Reddit and YouTube talking about their love or hate towards Rust.

Then there’s 3 hour-or-longer videos about Rust which target C++ devs directly. Two are from 2022 and 2019 with one from 2023. Only the 2022 video starts from basics with features that a C++ dev would actually need to understand, like ownership, borrowing, and references. One jumps right into multithreading ideas by discussing mutex. The other jumps into how everything is made “easier” because the compile does borrow-checking instead of having the developer manage it.

These videos probably aren’t bad, but they don’t touch on the larger “gotchas” that C++ maintainers will be scratching their head at, like explicit lifetimes, inevitable headaches with error handling, and reference/target mutability. Some of them are a good start, but they mostly focus on just technical features. It’s difficult to find a resource that helps you learn how to plan out your project early on so you’re not refactoring later due to the topics mentioned earlier.

And to be honest, if you are unable to use them to learn rust, maybe your c++ skills isn’t that impressive either.

And this is why 6% of non-Rust users have cited the community as a barrier of entry. Immediate pettiness and hostility rather than trying to get the best resources into the hands of newcomers.

Oh most certainly. I attended BYU Provo and there was a lot of effort from students to allow the sale of caffeinated soda on campus, but the belief was that the university was holding out only because a large number of alumni might stop donating if it were to occur.

(This was more recent though.)

The culture amongst members can and often will have items that seem to go against or misinterpret official doctrine. I don’t disagree that the church would need to reiterate the doctrine to clear that up for people. What I personally don’t know is how often is appropriate for such corrections to take place. If you correct them too often they may choose to not seek out answers themselves but instead wait for a leader to explain it to them, which runs against the teaching of proactive scripture study.

Ok, I should stop there. Starting to nitpick human nature as though I’m any better (and we know that’s not fucking true in the slightest, lol)

One assumes that a god would be able to formulate a standard that can be applied cleanly, to everything, and communicate that clearly to his prophet.

The issue wouldn’t be the god in question, but instead the people.

Consider the fact that Moses was given the Ten Commandments for all the Israelites to follow. They’re incredibly simple and straightforward. Yet there still was a division in how these were observed, which was documented well in the New Testament.

The two most notable (outlined in the New Testament) are the Pharisees and Sadducees. The Pharisees can be summarized as a group which added man-made rules or guidelines on top of the established doctrines. Certain stories, such as Christ healing a man on the Sabbath, demonstrate that the intention of a commandment can be forgotten by people who choose to observe by the letter of the law. The Sadducees can be summarized as a group which chose to observe only doctrines that are written. Both groups, however, largely ignored the foundation behind the 10 Commandments.

Christ explains it as simply as can be. Love the Lord above all else, and love they neighbor as you do yourself. The 10 Commandments were already straightforward to begin with, but the two greater commandments set the standard you suggest such a deity should be capable of doing.

Even still, as simple as they can be, the issue often becomes that some people want to be told what exactly they can or cannot do, while others want to justify their actions on the basis of technicality.

All of this to say, the doctrine for the LDS church is based on the idea of obedience towards God. It doesn’t matter why He says to not drink coffee, just that He promises you’ll be blessed if you do. So by virtue of the two greater commandments, loving God means following His instructions. And that alone should be reason enough to do so.

(Mind you, I disagree with how this is often put into practice, as a lot of guilt-tripping occurs for those who choose not to follow these teachings. At its core, these actions are antithetical to Christ’s teachings and examples, which are to love all unconditionally as we are all sinners in the eyes of the Lord. But again, the issue lies with people, who aren’t perfect, rather than the doctrines put forth.)

Like with caffeine specifically they have a long history of forbidding its use and then suddenly they reinterpreted it the way you’re suggesting.

I had to think about this. I can’t seem to find any articles in a quick search where church leaders (a Prophet or Apostle) explicitly forbade its use. I have, however, found many excerpts where leaders who do not sit at the head (Quorum of the Seventy, BIshop, etc) have made statements warning against it or even flat out saying that members should not ingest it.

Given the structure and lack of corrective statements coming from above, I would attribute the confusion to local and regional leaders being overzealous by including caffeine explicitly in their teachings. Some have worded things in a manner I would find accurate, such as “high-dose caffeinated energy drinks” or “excessive soda consumption which results in high caffeine and sugar intake.” Others though explicitly call out caffeine as an “evil,” describing experiences with caffeine withdrawals or members deciding to not ingest alcohol, nicotine, nor caffeine. These mentions seem to have drummed up confusion primarily in the 80s (a lot of “Letter to the Editor” publications from this period seem to have been back-and-forth arguments among members, lol).

Initially I didn’t think the history is as “long” as you claimed, but then I realized that the 80s was just forty years ago, and with some results of the topic dating as far back as the 70s, it would mean it’s been an intra-member debate for almost half a century. And half a century is practically a lifetime 😖

Yeah… unfortunately, confusion about this particular subject exists because members often look for the underlying justification on things and then extrapolate from there.

(I’m going to paraphrase and shorten things a lot here so we don’t have to dive into definitions and technicalities. Bear with me.)

The doctrine brought forth about this is what’s referred to as “The Word of Wisdom,” which was a short outline of what things were deemed as “harmful” or otherwise “unsuitable” for the body. The idea being that the Lord was promising to people that if they didn’t ingest these things, they would live a healthier life as a result. “Hot drinks” was mentioned and clarified a century later to mean “tea and coffee.” Furthermore, “tea” refers to black and green tea, and not necessarily herbal tea.

People, by nature, want to understand the “why” behind things. You also have people who want to understand where the line begins and ends so they can tiptoe it. Enter the rumor that since the “hot drinks” referred to “tea and coffee,” they both have not-so-insignificant amounts of caffeine in them. Obviously that must mean drinks like Coca-Cola and Pepsi, plus foods such as chocolate, must also be in violation of this, right?

Well, the issue with that is people think they’re applying “the spirit of the law” (meaning the larger picture behind it) when they’re actually applying “the word of the law” (taken at face value). The idea behind the Word of Wisdom is to take care of your body by having a balanced diet and not eating too much of a particular thing. Certain items were called out explicitly; if caffeine were the true issue, then it would’ve been called out instead. But it wasn’t, and there have been some clarifications to emphasize that caffeine itself is not the explicit reason behind it. (However the idea of “addiction” could extend to caffeine if someone were to consume large amounts of it regularly, but addiction or dependency can occur even to things like Tylenol when too much is consumed, so targeting it specifically is silly.)

So in short, it’s a mixture of misunderstanding and overzealous practice. Caffeine is perfectly fine. Just like anything else: make sure you’re not consuming too much of it.

Should’ve sold some copies of the Christmas Star Wars episode

Oh 100% that’s what they meant. It’s just something that caught my attention as it almost appears to be an oxymoron.

In practice, “microtransaction” can mean many things. A small price, a purchase of non-unique content, or even a small quantity of unique (non-base) content. So yes, upgrading to the “deluxe” edition can fall under that description. But calling the “deluxe” content upgrade a “micro-transaction” almost appears contradictory. So I had a little chuckle while pondering this before becoming upset at how broad (and expensive) said “micro”transactions have become.

deluxe edition as a MTX

I spent a few minutes analyzing this sentence alone. Admittedly I read the rest of your argument and respect your opinion. It’s just that this is stuck in my head.

Buying the deluxe edition through a micro-transaction? My mind wants to classify this as an oxymoron. Admittedly a lot of microtransactions aren’t really micro by any stretch of the imagination but this just stands out.

Nah I didn’t read your original comment as minimizing it, but rather saw it as someone who might not be from the USA. It sounded like genuine shock to how life-saving meds could just be flat-out denied for somebody.

Let’s say you get diagnosed with a treatable autoimmune disorder. Treatment isn’t cheap, so usually someone who recently got diagnosed and referred to a specialist to perform care will find that their insurance denied approval for prescription of medications and supplies needed.

The insurance companies will want the doctor to re-submit while providing documentation of the diagnosis (as proof) and an outline of the treatment plan. The insurance company can say “your plan states six months of injections but we will only approve for three.” At that point, the patient is stuck with a three-month plan because the cost of treatment is too much to pay out of pocket and the doctor won’t go forward with a six-month plan unless the patient pays in advance for the three months that wouldn’t be covered.

Another example is rare disorders where the medication may cost hundreds of thousands of dollars. Insurance may decide the cost is too high and deny coverage for the prescription.

Finally, there are instances where more common issues (such as diabetes) may have the insurance artificially limit how many doses of a drug they decide to cover. If a person has a special case (like needing to take twice the amount due to tolerance or it being based on the person’s weight), insurance may deny it because it exceeds what they believe the average person should need.

All of these are examples where someone is stuck waiting for what is essentially life-saving medication just because insurance doesn’t want to pay out, or doesn’t care that you have a special scenario that requires some exceptions for it to work properly.