MadhuGururajan

yo the people railing against this must consider themselves geniuses. It's like people have a hateboner for rust.

Have you considered maybe that this was expected regardless of what language you do it in? It's a rewrite and that's definitely going to miss several decades of changes that have made the normal version good.

You have to measure the time it takes for the rust version to get to the same level as the non-rust counterpart.

Consider also you actually can't switch off your brain because of memory guarantees. You have to work on other important things too.

Also keep a count of CVEs that the rust version generated and decide if the current port is better or a failure.

because it is a difficult endevaor and earns glory, praise and filthy money if you get it right?

maybe the donor is generous and wishes the problem to be solved for more than one laptop. The benefits compound and for example avoid e-waste.

staging sucks anyway. Never catches bugs.

you say that but they're already thinking a step ahead and assuming meta left a backdoor or CVE at the behest of 3-letter agencies.

What's facebook's business plan? Right, surveillance capitalism.

My understanding so far is:

if business logic assumes a set of preconditions before a particular piece of code that the language/runtime/os satisfies.. then it's an immediate assert. Any kind of IO, memory creation and OS operations fall into this carefory.

However if the business logic assumes something in its own domain and that assumption does not hold then its better to handle that instead of crashing. Ex. being you expect a queue to have at least one element in some pipeline and if it is empty then return saying nothing to be done.

Edit: don't assert/crash if your application is single process multithreaded unless you want your friend from accounting asking you why their stock ticker crashed just when they clicked a button in the coffee shop module of your app. Use some thread exit mechanism.

i pronounce it as cauchy

I wonder how it would look with excel sort

Check if systemd has any clues:

1. journalctl -b > systemd-logs.txt
2. grep -C3 -i "error\|fail|warn\|fatal\|can't\|cannot" systemd-logs.txt

put it on codeberg and github.. just to have a backup.. doesn't need to be public facing.

or they just place a block of cheese near by as a shelf or counterbalance for the chopping board for the actual ingredients.

you mean more propaganda.