I can assure you it’s not “automated” or anything like that. I usually prefer to see an excert of the post that caught the poster’s attention, or any info in that realm really.
For me it’s interesting because nowadays we have frequently too much information, not too little.
If the majority of the title (and body) is the name of a company or organization, I get cautious.
zlib-rs => crate replacing non-rust zlib firefox => where the replacement is happening trifecta => the foundation sponsored to develop the replacements
Maybe I’m influenced by the fact that I pre-knew all of the above. But as I wrote, it’s quite ironic choosing this perfect title in particular to complain about 😉.
On the topic of low(ish) level dependencies getting incrementally replaced with Rust rewrites, a Google employee did a presentation on the same topic recently.
I can assure you it’s not “automated” or anything like that. I usually prefer to see an excert of the post that caught the poster’s attention, or any info in that realm really.
For me it’s interesting because nowadays we have frequently too much information, not too little.
If the majority of the title (and body) is the name of a company or organization, I get cautious.
zlib-rs=> crate replacing non-rust zlibfirefox=> where the replacement is happeningtrifecta=> the foundation sponsored to develop the replacementsMaybe I’m influenced by the fact that I pre-knew all of the above. But as I wrote, it’s quite ironic choosing this perfect title in particular to complain about 😉.
On the topic of low(ish) level dependencies getting incrementally replaced with Rust rewrites, a Google employee did a presentation on the same topic recently.
Makes sense now! Also, the post itself is good! (Pre-knowledge of the terms possibly helped you, yes.)