Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
Mine is that the useState hook is an actual plague on the entire React ecosystem. Regardless of your opinions of React, if you wanna use something then use it right.
Not the oc, but honestly just random shit, like:
Linq.
Async and await are both in python or rust, but still via anexternal provider afaik (like Tokio).
Explicit interface implementation (default trait implementation for the Rust fans)?
Nice source generators and what you can fo with them (kinda like aspect programming).
Idk if python or js support pattern matching or proper low level or no GC coding.
I also enjoy my langauges to have an end of statement character like
;instead of the horrible visual mess python is.Type safety of compile and runtime type checks lol. In C# if you say your module requires int parameter, noone will be able to call it passing None/null/string/date.
Pretty much hit the nail on the head to be honest
AKA - We have Monads at home…
Rust is really missing something like do syntax. It’s half-way there with the semicolon and question marks, but it’s missing an idiom for .map_or_else and to generalize the thing to work with a trait.
Thats not the linq purpose. Though it is technically a monad, its purpose is not hiding side effects or managing an async flow, or managing nulls/errors, but query, filter, map data from an enumerable.
If you use Linq as a replacement for Option, Either or Maybe you’re doing something wrong.
Yeah, exactly, it’s a replacement for List.