I do start with a Hello, followed by whatever I have to say in the same message. In addition I also annotate with an `<async>`/`<urgent>` at the end as appropriate.
> a good starting point would be removing any work accounts from your phone.
+1 to this.
I recently did this and found it enjoyable; I followed this advice from mentors. Disconnecting from work made me happier & I get to spend more time with my family. I enjoy my stress-free weekends and live in peace.
The exact quote that made me nuke all work accounts from my mobile:
Your ${COMPANY} can replace you in an instant; Your family & loved ones can NEVER replace you!
I actually, for real, have a slide deck about starting an empire. I did it as a joke for my friends, it's formatted and phrased as a startup pitch deck, but an invasion is required for one of the milestones. So you never know!
You'll see! :)
(seriously though, even if you are not planning any invasions in the foreseeable future, you need to think like an attacker to successfully defend against attackers).
What if you know you /can/ learn how to do that but make a conscious choice not to take on that ability? Then what if you know you can but rank that ability as being too far down the list in terms of its benefit to you, your family, your neighbors and the human race to supplant time spent learning X or doing Y. For whatever you feel are a good values of X & Y?
This more "not invading AND you can't" rather than "because." Seems like a reasonable thing to me.
"I decline to shoot anyone with a gun and I can't." That seems like a position taken by some large number of pretty reasonable people in a many contexts that seem, at the very least, justifiable.
The day you decide to play Crusader Kings 3 or a grand strategy game.
It requires some lateral thinking to figure out how can your dynasty conquer the entire British island, subduing the Scots, the Norwegian, the Saxons while being at war with France and you're just a lowly Irish duke with a crippled heir.
In my humble opinion, Rust should not be faster than C; C is the closest we can get to the bare-metal without writing assembly.
In my opinion, in the discussion after this talk folks did mention some pointers of why this was achieved. Although, for the same driver, there is a 2.6% drop in perf when used with 3 disks.
Rust could in some very specific cases be faster than C (assuming all other things equal) for the same reason of Fortran: it can disallow aliasing so the compiler could theoretically exploit this to generate faster code
When two pointers point to the same place they alias each other (it's alias as in two names for the same thing, but it's a verb as well as a noun)
Rust's &mut borrow is like a pointer guaranteed to be non-null but also guaranteed to never point to memory that can be accessed by another borrow. Or in other words, &mut can't be aliased by other borrows. If you ever try to alias a &mut borrow, the program won't compile.
C's restrict is kind of similar, but it's far less used than &mut. That's because if you violate aliasing restrictions of restrict, it won't generate a compiler error, but will cause UB!
Anyway in Rust, a &mut has exclusive access to a piece of memory, and the compiler may theoretically make use of this fact in optimizations. However, LLVM isn't yet as good as it could be :( first, I think it doesn't implement yet the real good stuff that GCC has (I found this https://internals.rust-lang.org/t/fyi-ibm-is-working-on-llvm... from 2020 but I don't know the state of it), and worse, what it currently has is very buggy, so sometimes the Rust compiler is forced to disable it :(
An analogy would be like of the editor. Think of this tool as the editor that one uses. It does not matter to git what editor one uses; similarly, it does not matter what diff pager one uses :)
Yes, you can turn it on without having any side-effects for others.
Good that its back!