perth

What about Python? It doesn't yell at you for having unused variables which is nice for actually developing the software.

My main gripe with Go is it doesn't seem geared toward figuring out new things, or letting people hack and experiment during development.

The most insane thing about Python is how you can override single methods in classes and use the class like normal. One time I was working on getting FIFO working on Windows, and none of the Python built-ins were set up to handle any random process writing to a named pipe that wasn't within the same Python instance. So what I did was I took the closest implementation Python offered, which was in the multiprocessing module [1], and overrode a single one of the methods to do what I wanted it to do. The module still handled all of the cleanup so I was confident there weren't any memory leak issues, and I was able to make a simple change to the flags it was passing Windows to allow for the functionality I wanted. A language that has a hackable standard library itself is insane and I don't think I've seen it on any other language. In addition, I've found the C/C++ bindings for Python wonderful and intuitive to work with. The setup takes no effort at all and it "just works", batteries included, via ctypes.

https://github.com/python/cpython/blob/main/Lib/multiprocess...

Whenever I see Go I think of this:

https://news.ycombinator.com/item?id=16143918

Not sure how true this is, but I've heard that Sony's PlayStation division is taking a hard hit from scalping, since they sell the consoles at a loss and scalpers don't buy games. So I wonder if this trend of selling consoles at a loss will continue in future generations.

Sure thing. The links are summarized research btw, you can get through them all in 2 minutes each.

from https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7771841/

"The challenge for modern vaccinology is to be able to provoke all the requisite steps leading to immune system activation in vivo, and to provide a non-virulent, harmless type of a given agent capable of generating a strong and adequate immune response tailored against specific viral attack (Moser and Leo, 2010). Thus, some questions arise regarding the development of the vaccine (see Table 1 for current development state of COVID-19 vaccines) that will be administered to billions of people at risk of COVID-19 infection."

|

v

"As mentioned earlier, ACE2 is the route of SARS-CoV-2 infection. However, this receptor plays a vital role in both innate and adaptive immune responses by modulating the antigen present antigen cells that interact with T cells to initiate defense initiatives (Bernstein et al., 2018). This receptor of transmembrane protease acts in the conversion of angiotensin 1-8 (Ang II) to angiotensin 1-7 (Ang 1-7), prompting diuresis/natriuresis, preserving renal function, and attenuating cardiac and vascular reformation (Vickers et al., 2002; Santos et al., 2008; Zhang et al., 2010). ACE2 also has an important role in the nervous system, and disruption of this receptor can trigger neurological disorders (Kabbani and Olds, 2020)."

I read this as: depending on the immune response the vaccine creates, it can cause potential damage to various organ systems

from https://healthcare.utah.edu/healthfeed/postings/2021/07/bloo...

"In rare cases, antibodies that the body produces as a side effect of the vaccine lead to uncontrolled activation of platelets. This causes both low platelet counts and blood clots to form in unusual areas. VITT is not associated with the Moderna or Pfizer-BioNTech mRNA vaccines. "

I read this as: the vaccines have the potential to cause clots, but this isn't proven for Pfizer and Moderna vaccines

In terms of the tissue tests in lab by Pfizer, I wasn't able to find the paper I that read on that, so I don't have hard proof of that.

I got the vaccine with knowledge of the risks after researching it. The issue is a lot of people did not have knowledge of the risks since it was not in readily available places which caused widespread distrust in the vaccine.

Added source links to my post from links I pulled from Google Scholar. Not all are perfectly relevant but in terms of potential known but not discussed impacts I suggest [3] from February 2021 or [4] from January 2021 to have a look at which discusses the potential for heart and lung issues from the vaccine, alongside the need for booster shots, which were noted during the development before the mass deployment.

In terms of my visit, all I can really say is I got the vaccine at the Cleveland Clinic in May 2021, I don't really have any hard evidence of what happened during my visit other than my vaccination card.

Also in terms of the clotting I'm surprised you haven't heard of it? (not Google Scholar links, it's just that it's on many news sources from a quick Google search)

https://wexnermedical.osu.edu/blog/blood-clots-covid

https://www.nature.com/articles/d41586-021-02291-2

https://www.yalemedicine.org/news/coronavirus-vaccine-blood-...

https://healthcare.utah.edu/healthfeed/postings/2021/07/bloo...

Realistically the risk is that everything surrounding the vaccine is and was extremely suspicious. I've never had a vaccine before where the nurse urged me to keep moving my arm for the remainder of the day. Realistically the clotting of the vaccines was a real issue due to the poor testing, and I'm not sure if it's still a problem because I haven't heard about it being talked about for a while. In addition, there were potential risks known about the vaccine via research financed by Pfizer for months after it was released that were not present in the media or on any waivers for months after the potential interactions began appearing in lab tests, and the information was not effectively delivered to people who got the vaccine or considered the vaccine. I've seen the heart issues mentioned by people in the comments, what I haven't seen is that Pfizer financed lab research on samples of lung and heart tissue and found a potential for interaction that was never told to anyone until it became a problem.

Then we can talk about how the vaccine companies got immunity from being sued if people had any problems down the road from it.

[1] September 2020: https://www.sciencedirect.com/science/article/pii/S002432052...

[2] March 2021: https://www.futuremedicine.com/doi/full/10.2217/fca-2020-018...

[3] February 2021: https://faseb.onlinelibrary.wiley.com/doi/full/10.1096/fj.20...

[4] January 2021: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC7771841/

^ Not all optimal links but they are what I pulled from a quick search on Google Scholar regarding the subject. All date prior to wide discussion on potential issues caused by the vaccination.

Turns out being too lazy to clean up spider corpses after I killed them actually was like putting out heads on pikes as a warning to future spiders entering my home.

An epic thing you can do with PDF though is show an image of the font you want to show, and have a super common font like Helvetica hanging out behind it, so the end-user doesn't even need to render the font, it's just an image.

Chocolatey requires scans on _most_ uploads to the service. Under a certain threshold it only gives you a warning that says "this package had x detections".

Here's FAR manager which for some reason has some hits on virustotal

https://community.chocolatey.org/packages/Far

It calls a series of open source tools that result in producing a pdf with text embedded behind an image overlay, where the image overlay is the original pdf. It was a while ago where I really looked into this but to name a few:

ImageMagick to convert the pages to images

Tesseract-ocr by Google to transcribe the text in the images, which puts it’s output into singular pdf files

Pdfunite to stitch together the pdfs back into a whole file

I’m sure I’m missing a few, iirc it can call a tool that straightens the pages as well.

EDIT: Messed around and remembered the stuff:

where a.pdf is a 2 page PDF:

>convert a.pdf a.png

makes a-0.png and a-1.png

OCR's each image:

>for x in {0..1} ; do tesseract a-$x.png a_ocr-$x PDF ; done ;

combines them into 1 PDF:

>pdfunite a_ocr-{0..1}.pdf a_ocr_combined.pdf

Beware connecting GPD devices to your home or corporate network:

https://old.reddit.com/r/gpdwin/comments/8qfvuh/warning_new_...

https://old.reddit.com/r/gpdwin/comments/n5u1sy/yep_malware_...

Cultivation of Cannabis Sativa with low THC is legal in 46 US states afaik with the 2018 farm bill. So you can say growing weed is legal in most places.

Thinking about it a bit, there are physical solutions EVGA/NVidia can take that don't rely on introducing DRM components into the software. One that comes to mind would be stamping a red embossed serial number into the plastic around the entire chassis around the card. It wouldn't look very nice but it would be nearly impossible to remove and sanding it down would look extremely obvious that it was a stolen card in any product listings.

I mean doesn't Microsoft already phone home a unique GUID identifying the hardware in your computer that it ties Windows key activations to? And since Microsoft owns Canonical, probably in Ubuntu as well (on the defaults)?

Transporting GPUs in 2022: https://www.youtube.com/watch?v=oGZLYx8StWk

Yeah. I suppose this functionality isn't everyone's cup of tea. The cool thing about Wayland though is somehow it makes the windows still look crisp and good while making them the same size. With the canonical hack to xorg, they always looked blurry and gross. The gnome wiki had this to say on it:

"On a Wayland display server, each connected monitor will have a scale that depends on the DPI. A scale affects the scale clients draw surface contents when they are visible on said monitor."

So it seems like it actually modifies the drawing at the application level rather than rescaling it like an image.

Try to set two different DPIs in that.

Basically:

You have a Microsoft Surfacebook, Chromebook Pixel, or Macbook with retina display, let's say at 300 DPI, and you try to plug it into a monitor that is 70 DPI. The buffer will not be possible to adjust to properly handle both monitors because 1 is 300 DPI and 1 is 70 DPI. This is because xorg is internally designed around the philosophy that every monitor will have the same DPI. There are tricks and hacks that teams, specifically I've seen the canonical team pull this off, where they can "trick" xorg into displaying properly with some minor visual artifacting. The last time I tested this was with Ubuntu a few years ago, back when Wayland support was "experimental" and I had this exact sort of setup, and Wayland was easily able to pull this off 100% better in every way because it is not designed around this limitation.

Well it doesn't rely on using a giant buffer for multiple monitors so it supports hidpi scaling. Have you ever tried hidpi on xorg? It's a mess, even on Ubuntu where they tried their best to clean it up. The xorg apps from the compatibility layer still suffer from it, probably until they update to Wayland.

Sidenote: Google tried to use xorg for ChromeOS and ended up writing their own UI system for hidpi scaling among other things when it didn't work

Some relevant links for those curious about other people hitting into this:

https://www.foell.org/justin/simple-hidpi-monitor-scaling-wi...

Gnome team:

https://wiki.gnome.org/Initiatives/Wayland/XWayland