What’s with the sense of entitlement towards jobs in HN?
Businesses will continue to employee you as long as they think it’s a net benefit to them. Their outlook can change at anytime and for nonsensical reasons.
I would suggest accepting this state of affairs. That might mean making sure you have savings, or up to date job skills. Refusing to believe this can happen to you because you have worked so hard or been so loyal will only lead to heartache.
We've built a world where you either get a job, or you are culled from the population. Culling is inhumane, so the only way to resolve that moral quandary is to guarantee jobs.
I know - the meaning is actually indisputable from all of the context, regardless of the precise phrase.
But, even so, it is also indisputable that many who consider themselves devout Christians, rich and poor alike, reach a very different conclusion about the meaning of this whole exchange. I can only imagine this must be motivated reasoning.
I found a thread showing some such rationalizations:
Interestingly, it seems modern day prosperity gospel sorts don't go for a reinterpretation of the camel, but for a reinterpretation of the word "rich".
This is only true for very simple single-threaded code. Once you’re doing anything the compiler can’t trivially optimize, you’re using libraries, getting left far behind by the Rust program, or both.
> Since most industrial software is in C and C++ an example would be more convincing.
Agreed- do you have any to back up your original claim?
> > doing anything the compiler can’t trivially optimize
> What does compiler optimization have to do with libraries?
One of the most common reasons to use a library is because it has optimizations you want to use. For example, performance-sensitive programs link against OpenSSL even if they’re just using a couple of hash functions because the SHA-256 function you copied into your codebase won’t have their assembly backend or use of processor intrinsics. Repeat for string searches, pattern matching, all kinds of math, etc. where people have written libraries with pricessor-specific assembly, SIMD intrinsics, etc.
> Plenty of C and C++ programs are multi threading using a system api like pthreads.
Yes - and the long history of bugs related to that is why many stayed single-threaded because it was more work than the author had time for to make the code thread-safe. Rust’s “fearless concurrency” talk isn’t just marketing but a reaction by people with a lot of experience in the area realizing just how much more they used concurrency when it was easy to do correctly rather than infamously hard.
When C programmers do crypto they also use OpenSSL, but more for security than performance. Do you have an example of a rust library which is a better substitute for commonly hand written C?
> fearless concurrency
Not related to the topic of discussion about performance gains of using libraries.
