You sound exactly like the tens of doctors that misdiagnosed my aunt (who passed away through euthanasia after her symptoms got too bad to live with late last year).
I understand that the symptoms of ME/CFS might be similar to being obese/depressed or housebound, but the problem is that doctors often jump to that conclusion too quickly and don’t take efforts to diagnose ME/CFS leading to situations like my aunt’s. She was also obese and depressed and has been struggling with those symptoms for about 30 years and has constantly been misdiagnosed the entire time because doctors didn’t figure out that those were symptoms of ME/CFS and not two unrelated conditions coming from two different diagnoses.
Thanks to long-covid putting the symptoms of ME/CFS on the forefront lately, there’s finally been some much needed research into the disease and people like my aunt finally get the diagnosis they should have been getting many years ago.
My main question here is mostly why so many people still rely on axios for their fetch implementation.
Native fetch has been a thing in the JavaScript world for so long, and the DX gains to using axios over it are miniscule. The only thing I can think of is axios instances, but you can easily write a tiny wrapper for fetch that would do the same.
This is a genuine question - if you still use axios, why exactly?
People tend to forget that React != React-DOM (i.e. HTML).
React is just a framework for declaratively defining components and reactivity, the end result can be whatever you want. That’s what react-native is for mobile apps, and as another commenter pointed out, in this case it was using React Native for Windows[1], which apparently calls native Windows APIs in the background.
I like to jump on the MS hate train as much as the next guy, but React itself is not the reason the start menu is bad.
Agreed and it's an important distinction to bring up. There are some pretty cool projects that use react like that, e.g., vicinae [0]. And one can implement a different renderer for react, here is a tui renderer [1].
Notice the word „decriminalize“, not „legalize“.
It’s about not throwing people already struggling with addiction in jail but rather offering safe alternatives (counseling, safer use, etc.).
The government‘s not passing out drugs in the street, like US media likes to suggest.
It’s simple, you use innerHTML if you know for sure where the input comes from and if it’s safe (for example when you define it as a hard coded string in your own code).
You use setHTML when you need to render HTML that is potentially unsafe (for example forum posts or IM messages). Honest question, which part of that isn’t clear?
Not to say it is the quip but I have had buggy builds with bun that requires sticking to esbuild, I think it was bundling prettier with many plugins into a single JS file.
I always do that sort of thing in Docker so never considered it could be a Linux-specific thing, maybe so.
That and losing the ability to connect displays via USB-C is what’s keeping me from switching sadly.
I love what the Asahi team is doing and I’m confident they’ll get it figured out. I wish I could do something to help, but this type of programming is far beyond my skill level so there’s not much I can do other than donate here and there.
I understand that the symptoms of ME/CFS might be similar to being obese/depressed or housebound, but the problem is that doctors often jump to that conclusion too quickly and don’t take efforts to diagnose ME/CFS leading to situations like my aunt’s. She was also obese and depressed and has been struggling with those symptoms for about 30 years and has constantly been misdiagnosed the entire time because doctors didn’t figure out that those were symptoms of ME/CFS and not two unrelated conditions coming from two different diagnoses.
Thanks to long-covid putting the symptoms of ME/CFS on the forefront lately, there’s finally been some much needed research into the disease and people like my aunt finally get the diagnosis they should have been getting many years ago.
reply