this is more focused for sure, but it lacks the enthusiasm of the original. if i was trying to do this for work, i would appreciate how quickly it gets to the point. however, it no longer reads like this is something you're interested in. it reads a bit wooden. i get that would happen after you've been told to correct your style though.
to be clear, the original article doesn't need to be rewritten. for the future though, when you want to tell the story of how you got something working, include your reasons for doing something a certain way. if you need a self-inflicted complication, that's not really a part of it (unless it's funny)
your writing overall is good! it's just a matter of information priority.
here's a tip, dunno how applicable it is but i use it when writing technical documentation:
for each step, explain to yourself why you're doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.
this guide, and the previous one, have a lot of weird superfluous steps. like, why use a command that includes nvim and then ask people to change it instead of just saying "edit the file"? why symlink systemd stuff to your own home directory?
the info is good, but having to separate the actually useful stuff from things that are specific to your config makes it less useful.
this! i got my first vista experience on a laptop with a Turion and 2GB of RAM and it was really smooth. bit too chunky for my taste ux-wise but it was solid. first bluescreen i got on that machine was after installing W7.
then the GPU melted its own solder after a few years and that machine was relegated to server duty.
when moz first bought pocket and the extension was included by default, it was before they open-sourced it. this was in the NPAPI days when plugins could do basically anything on the host system. that shit got disabled the moment it touched my browser. same as the drm blob.
llamafile is not really "effective". it's incredibly impressive, but it's the opposite of effective. it's a collection of a bunch of hacks reliant on coincidences in OS design, and works by basically recompiling itself on the fly to work with different architectures.
if you want effective, run llama.cpp compiled with actual optimizations for your platform.
she was the face of the occupy wall street movement, but her views back then were more ancap than anti capital. while working for google she tried to petition the us government to shut itself down and hand the reins over to the tech industry, with google's ceo as president.
the base of the APE library that powers llamafile is called cosmopolitan libC, iirc in direct reference to the old soviet term.
to give credit she's mellowed out a lot in recent years.
our uni had mandatory chemistry for all engineering degrees, even industrial economics and computer engineering, so naturally a lot of people had to re-take it. the registrations weren't done processing for weeks, and during that time you had to assume you were in, or you'd be hopelessly behind. that lecture hall was filled to the brim the first few weeks every semester. people were sitting in the aisles, on the stairs, in the window sills, two to a chair... it was insanity. i really hope they fixed that.
i'm glad you found it useful, best of luck :)