537 Ricing Windows in 2020

Many people like their things to look nice. I am one of those people. I like things to look nice all the time. One of the things I like to look nice is my PC's desktop. I have to look at it constantly, so it might as well be pretty.

What is 'ricing?'

Ricing is the term used to describe the process of making a desktop environment look nice. This usually involves at least several steps, including installing a window manager, a theme, custom icons, and making the terminal look nice. Windows, however isn't meant to have every single part of it tweaked and customized, so we have to make some concessions.

Note that many ricers think that ricing is about making their computer more efficient for their workflow. I disagree. I believe that improved workflow is a sideeffect of good aesthetic, and my personal aesthetic is based in functionality. Also cyberpunk.

What does this guide include?

This guide aims to be a resource for entry level ricers to ricing their Windows 10 environment.

Because cross-compiling binaries for Windows is easier than building natively

I want Microsoft to do better, want Windows to be a decent development platform-and yet, I constantly see Microsoft playing the open source game: advertising how open-source and developer friendly they are - only to crush developers under the heel of the corporate behemoth's boot.

The people who work at Microsoft are amazing, kind, talented individuals. This is aimed at the company's leadership, who I feel has on many occassions crushed myself and other developers under. It's a plea for help.

The source of truth for the 'open source' C#, C++, Rust, and other Windows SDKs is proprietary

You probably haven't heard of it before, but if you've ever used win32 API bindings in C#, C++, Rust, or other languages, odds are they were generated from a repository called microsoft/win32metadata.

Could an LLM end up being the core part of a dangerous computer worm?

How would we neutralize such a thing if this happened?

Some virus and worm background

https://en.wikipedia.org/wiki/Timeline_of_computer_viruses_and_worms

There is a hilarious story from https://users.cs.utah.edu/~elb/folklore/xerox.txt about an early computer virus called robin hood and friar tuck. This was basically just two programs running on a UNIX system that would look out for each other and reboot the other process if it was killed. It's interesting to note that since computer programs run thousands of times faster than humans, a human can't type kill -9 robinhood then type kill -9 friartuck in time. The computer is faster so it always wins if you try this. To defeat this you need to take a different approach than speed.

	"""
	I do not provide support for this unless its an actual error in the code and not related to your setup.

	You'll need:
	- Vapoursynth (this was written & tested on R53 with Python 3.9.6)
	- pip3 install pathlib anitopy pyperclip requests requests_toolbelt
	- https://github.com/HolyWu/L-SMASH-Works/releases/latest/ (Install to your usual Vapoursynth plugins64 folder)
	- (if using ffmpeg) ffmpeg installed & in path

	How to use:

	/*

	LaTeX inspired PDF Export Theme for https://obsidian.md
	Made by @phibr0 on Github

	Tested with Obsidians default Theme and the California Coast Community Theme

	Please don't share this File with others, instead share this Link: https://www.buymeacoffee.com/phibr0/e/42263

	*/

	As noted by @murdats below, there are more URLs than just these 1440 ones, depending on the argument values
	that are hashed (as the filenames below are MD5 hashes of a few arguments: red/blue pill color, HHMM time, etc.)

	You can read details about the algorithm used to generate these URLs here:

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

	---

	00:00 https://thechoiceisyours.whatisthematrix.com/generated/v7/high/d43725991d28ffcab04aa716762cf6af.mp4