Chronic fatigue syndrome has long been known to often start with a viral infection (for example: https://pubmed.ncbi.nlm.nih.gov/21756995/). Other issues can arise as a consequence of viral infections as well (e.g., thyroid problems). I don’t think this is well known amongst the general public, even if it is known in the medical field. This may be a reason why people are surprised about “long-covid” as if long term effects are something unique to the SARS-COV-2 virus.
Readit NewsDead Comment
Deleted Comment
hvocode commented on People also suffer 'long flu', study shows bbc.com/news/health-58726... · Posted by u/mrfusion
hvocode commented on I bricked then recovered my reMarkable 2 operand.ca/2021/09/27/how... · Posted by u/greenhathacker
My only regret about this device is that it seems to lack full disk encryption on the device or any meaningful privacy (encryption) for documents stored in reMarkable Cloud...which is all of them if you want to use features like Screen Share (f.k.a. LiveView). ReMarkable should not be able to access contents of docs backed up from my device without my password or recovery key, but AFAICT, there is no such protection whatsoever against internal threats.
Other than that, I love my RM2, just can’t use it for as much as I’d like because of the above.
I’m in the same boat. Due to security restrictions of my employer I can’t use cloud services to store work related stuff. I was really bummed when I discovered that a lot of the interesting features of my RM2 require their cloud service. I’ve dug through the GitHub repos of RM2 hacks and open source tools that are available, but it still feels like I’m missing out.
> I haven’t explicitly thought of myself as pursuing “metamodeling” in the past (and I only just invented the term!).
No knock on the author and his rral accomplishments but it’s a well-established term [https://en.wikipedia.org/wiki/Metamodeling] for example. Much of my career has been metamodeling for certain kinds of analytical applications.
Reinventing known things and claiming that they’re novel is sort of his shtick. That said, he often does do interesting work - it just takes quite a bit of patience (which many people don’t have) to wade through the fluff and self-congratulating to get to the interesting technical meat of his writings.
hvocode commented on Structural pattern matching in Python 3.10 benhoyt.com/writings/pyth... · Posted by u/chmaynard
Once my favorite language by far, Python is starting to became too cluttered. Very few of the additions to the language in the 3.x branch are worth it IMO.
I remember that in the early 00's people called it "executable pseudocode". I bet nobody would use now that expression for modern Python with decorators, comprehensions, walruses and the like.
Part of me wants to disagree since some of these features make my code shorter, but I have to agree since they commit a sin of language design that I dislike - implicit magic. Decorators are useful because they can help you shrink code by letting the decorator generate boilerplate for you. The code gets smaller, but now it’s harder to know what’s going on since you need to know what magic happened behind the scenes due to the decorator. It feels very much like issues I ran into when I used C++ meta programming libraries - my code shrank, and at the same time my understanding of what it actually did also shrank. Same with the walruses - my code gets smaller because now there’s some implicit stuff happening.
Comprehensions are a little less magical - if anything, they are more explicit. If I want to create a list where each element is generated by some function over another list, I just say it. Doing so with loops is obscuring what I wanted to say in the first place. The problem with comprehensions isn’t so much the comprehension, but the obtuse ways people can use them to eke out performance by avoiding explicit loops.
I’m all for things that are closer to what a programmer means, but less keen on features that entail obscuring details that may come back to haunt the programmer later (I see this most often with decorators).
Deleted Comment
hvocode commented on I Got a 'Mild' Breakthrough Case npr.org/sections/health-s... · Posted by u/dsr12
I’m getting a little tired of articles or chats with people where you get the impression that people think the vaccines will create some sort of covid-proof bubble around them. This is the only explanation I can find for people acting surprised that vaccinated people get sick. The whole point was to prime the immune system so that when exposed, the likelihood of extreme effects would be drastically reduced. That’s it.
(E: I don’t get why people downvote this - all of the benefits of vaccination are precisely due to what I describe. Lower likelihood of individual bad outcomes, which reduces burdens on healthcare, and ideally, reduces community spread by reducing the amount of virus that replicates in an individual and can be passed on. This is why I was one of the first in line when I could get the vaccine. Perhaps daring to critique people with unrealistic vaccine expectations is unacceptable?)
hvocode commented on Open source applications for macOS github.com/serhii-londar/... · Posted by u/yesenadam
I can see Windows maybe just going to a linux base. But the important part for them to open source would be details for .exe executables. This is something I see them not open-sourcing. You'll be able to run .exes on linux, but only if your on the 'Windows' distro. That is at least my take.
The details of Windows executables are all well documented and open - it's very easy to parse a windows executable and run it. The part that's missing to run it without Windows is the implementation of system calls and system libraries. Without those the executable will run into dependencies that you are missing. This is the whole reason for things like WINE - the executables are easy, but the runtime environment that Microsoft hasn't opened up is hard.
hvocode commented on Open source applications for macOS github.com/serhii-londar/... · Posted by u/yesenadam
There is nothing FOSS about macOS that I personally find appealing. The future of macOS is strictly into direction of further closing and limiting. SIP is monstrosity, Brew is hell under Catalina. There are awesome people who basically hack and find a way to port things, but comparing this with true FOSS OS is naive.
Pinch of salt is not needed, the golden days when we had real MacOS are long gone.
Someone asked strange question: Does an app being cross-platform diminish its value to the user? Nope. Several times no. Example: Affinity Designer is cross-platform and thank to this my production workflow can live without "active scanning" from some corporate overlord.
Too much Apple brainwashing is going around, too much.
I'm not sure it's a question of FOSS OS vs non-FOSS OS. Working with MacOS has always felt similar to working with other non-Linuxes -- it's different. When OSX first came along with Rhapsody, while it was a form of UNIX it was definitely painful - stuff rarely built out of box, and there was lots of breakage. It surprises me when people talk about how wonderful OSX used to be that they forget how absolutely painful it was for the first few years of its existence. There was a brief period between 2005 and 2013 when stuff worked reliably (the "golden age" you refer to) - and it wasn't a matter of OSX becoming more open. It was just popular, so OSX was a first class citizen in most configure scripts and the OS didn't really put up any barriers to using it like a Linux with respect to the Linux security/permissions model.
The added restrictions of recent times (e.g. SIP, the move to a non-GNU build toolchain, hard read-only restrictions on the OS region of the filesystem, etc) aren't so much a FOSS issue as them just adopting conventions that aren't present on the Linuxes. The breakage of packages and porting efforts feel very similar to when we used to have to worry about how a package would work on HP-UX, Irix, Solaris, and the various systems that were all similar but not quite identical. That was never a function of FOSS or not - it was just a function of not being all the same.
I find it very frustrating that people try to treat OSX as a Linux - it's not, and it never will be. If you want to support macOS, then support macOS - don't try to bash Linux-isms onto it since they will always feel like a hack since it isn't and never will be a Linux. If that's important to you, there's an easy solution - use Linux. I do that - I have my MacBook that I use as a Mac, and for the stuff that's simply too awkward to use natively there, I just ssh to my Linux workstation and carry on.