Comments by "" (@diadetediotedio6918) on "What Color Is Your Function | Prime Reacts" video.

  1. 23:00 And if freezing your current thread to obtain the value makes your language not colored, then C# is also not, you have the .Result that will block until it gets the value
    7
  2. In my humble opinion, there is a very objective and clear reason for the function colors problem to exist, what are we losing when we move from that reason to an environment that doesn't "color its functions"? When we're in C# for example, you know when you need an async/await, and yes that spreads throughout your program, but you also <know> when you don't need an async/await, and we know that there are restrictions on what it can be done in functions of this type, we know the potential problems they leverage, at the end of the line all functions in all languages will have a color, what cost are we paying for languages that hide colors from us?
    5
  3.  @ThePrimeTimeagen  I can also see why it sucks, but at the same time a part of me understands why they exist. It is that, fundamentally, asynchronous functions are different from synchronous functions, when you write synchronous code you are writing something that will be processed linearly and directly by the processor, you can trust the memory that is on the stack, you can trust that nothing in the program will happen out of your control for that specific context (assuming we're not using threads of course), there may be a number of specific considerations. When a function is async, however, we're dealing with something that is essentially constantly moving around, which will need to be paused and resumed, you can't rely on your stack memory (unless it's copied entirely, which incurs other costs, and the different solutions lead to Pin on Rust), you can't count on the consistency of direct execution, you won't be absolutely sure which thread will execute your code (if we're dealing with async in a multithreaded environment like C# ) and you won't even know when (since that's the purpose of async in the first place), there are a lot of considerations that need to be made when using it (and I also understand that this is part of the tediousness of writing asynchronous code). Of course, that said, I've suffered a lot with function colors, nothing more annoying than realizing that you want to have a "lazy" code in a corner and that to do that you need to mark 300 functions above (hyperbole), I think that in that sense, C# at least manages to partially solve this with the possibility of blocking until you get a result, it wouldn't make a difference in terms of usability if, for example, the entire C# core library was asynchronous, because you can always use a .Result and block until having the result (not that it is the most performative or safest approach, of course, but sometimes it has its purpose to unify the worlds).
    4
  4. This is for PHP devs
    1