• 0 Posts
  • 164 Comments
Joined 2 years ago
cake
Cake day: December 24th, 2023

help-circle

  • I feel like it is not wise to discard the opinion of a layperson with this reasoning. Sure experts have been working on it as their day job vs. Us just looking at the fruits of their labour. But that doesn’t justify the assumption that they are infallible. Don’t you agree in our own areas of supposed expertise we are often corrected or get inspiration from supposed laymen simply because we have been too myopic about solving the problem ahead of us?



  • brother you’re using the wrong thing. First of all you are using crypto that’s going to give you some memecoins that are obviously going to collide after 55 hours as what are you even doing not rugpulling the thing day 2?

    Second of all, I am pretty sure you should use “RandomUUIDIToldYouSo” module for non-colliding hashes. We all know THAT thing gets its Noise from our parents’ instructions on doing a specific thing that keep changing arbitrarily every time you ask.





  • 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.





  • 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.