This really irked me when I found out because I spent longer than I care to admit diagnosing why a script I wrote seemingly did nothing.

I'm not sure if it's different now but when I had just installed anaconda python, and ran a script the usual way (`python foo.py`) it just did nothing (not even open the store page).

My memory might be a little hazy but I think not even changing PATH order of precedence made a difference. I had to find a sub-sub page in the modern settings app to disable the magic store hook.

I agree with some others here: I'm fine if I'm suggested a solution to a missing command but when that hook overrides a valid installation I have a bit of a problem :|

I read this in high school and now I am working on my phd in computer architecture. This is definitely not a coincidence. I love how well it explains the low-level workings of computers.

Definitely would recommend!

I’m not quite sure I understand your discontent.

You assert the author displays a “willful misunderstanding of the differences between FPGAs, GPUs, and ASICs.” What differences did the author misrepresent? And is it fair to call it “willful”?

From what I can tell, the ideas should be taken at a 10,00ft view: Verilog as an interface to (computational) FPGAs is not good enough because it’s inaccessible to domain scientists in other fields (where CUDA and similar are). The way I read the post was the author is framing a research question: “how do we design a new abstraction for FPGAs to do for them what we’ve done for GPUs?”