This post contains resources of RISC-V that I need at hand.
Specifications
Projects
Other
I’ve hacked on RISCV for 3,5 months, and some thoughts have developed.
I think that #WebAssembly was a wrong design choice for #web and instead #W3C should have gone with a real micro architecture. #RISCV provides answer for this.
Benefits:
WebAssembly is in the end really bad implementation of a great idea overally. Forth i interpreter was cool when JVM came out.
Here if W3C and browser vendors dared to take step back, it would result a stable innovation in the web for decades forward.
Transforming RISC-V to WebAssembly is ofc possibly but I don’t see it as an end solution, as all the crappiness of #wasm gets in the way, and e.g. benefit 6 would not even exist.
git submodule foreach --recursive git reset --hard
git submodule foreach --recursive git clean -f -d -x
I don’t like the policy of #buildroot in that you have to subscribe to the mailing list, in order to be able to send bug fixes. Not possible, when you try to proactively limit the incoming #email flow to the minimum.
#remindertomyself when editing #email with #aerc use CTRL-j and CTRL-k to move between header fields and the message body. I’ve got stuck to the CC list a few times and have sorted it out by killing the whole process, so this is definitely an improvement :-)
The key for finding out how to fix this was man aerc-tutorial
. I was cursing for a while because man aerc
was not giving me the answers, until I realized that there is another man page!
#notetomyself on #macos:
defaults write -g NSWindowShouldDragOnGesture -bool true