yumiris
Joined 5 years ago
Joined 5 years ago
Whilst a lot of unRAID's functionality can be achieved with a bit of tinkering and reading, its UI does save a lot of time and keeps things very simple. For example, I have yet to figure out a way of achieving GPU passthrough on an Optimus laptop without my hair going grey -- a part of me feels like unRAID might simplify it, despite it being an OS for servers rather than laptops.
One thing I'd absolutely wish for is ZFS support. I haven't looked into how ZFS's licence might interfere with its integration, but if integration is possible, it would be magnificent.
Nevertheless, unRAID is splendid at what it strives to do and buying a pro licence for it was absolutely worth it!
If we immerse and let our feelings of wonder and awe prevail, it will be difficult to forget such feelings even if the visual memories change over time.
I've learnt this one from my other half: she rarely takes pictures because focusing on pictures detracts from actually living in the place. She takes pictures as a sort of "index" for where we've been: a quick of us together with the location in the background, maybe one or two snaps of beautiful sights, and so on. It's pretty rudimentary, because ultimately, the vivid memories are preserved within us rather than the photographs.
Though I won't deny that the fear of not capturing everything can get to me at times, thus I end up taking one too many snaps. I think that's a fear many people deal with when they take an inexplicable amount of photographs of the same thing!
I combine it with KeePassium on iOS and Resilio Sync for synchronising across my main and mobile devices. (Syncthing doesn't offer an iOS client, sadly, hence the choice of using Resilio)
I use one .org file to declare all of my configurations, and tangle them together into the aforementioned files. This keeps things pretty portable, and makes up for the unintuitive readability of many dotfiles.
It can also work for rudimentary shell scripts and other single-file goodies; however, scaling it to proper multi-file programs proves to be difficult, especially when multiple developers are involved.
The solution is to - like your maxim implies - reverse the paradigm, by treating technology like it was initially designed: a tool for us to use with intent.
Even the apps and websites which have been optimised for engagement can be valuable. The value is what we make of it, just like how the websites make value out of us.
Advocating for quitting technology unfortunately becomes more and more of an impractical advice, as technology is further ingrained into our lifestyle.
What matters the most is being mindful and honest with ourselves. The moment we lose sight of how we use something, it starts using us.
It seems like your book focuses on a similar mindset. I've stumbled upon it before, but now I'll definitely be giving it a read! :)
At the top of the "family tree" of distributions, you've got "root" distributions such as Slackware and Debian. They branch out into specialised distributions such as Ubuntu Server for servers, Kali Linux for pentesting, and so on.
With this in mind, it's probably easiest to start with choosing a "root" distribution, and optionally choosing a derivative as necessary if a root distribution isn't specialised or convenient enough for your needs.
For example, if one wants stability and hardware compatibility, one can go straight with Debian. If they want a layer of user-friendliness and official support from many applications, then they could pick Ubuntu instead of plain Debian. (This is a subjective example!)
Considering there's hundreds of distributions, having some criteria such as high popularity and thorough documentation might be necessary to narrow down the list of choices.
DistroWatch is good enough for giving you an idea of each distribution's purpose without opening dozens of search tabs.
Of course, one could also choose the option to perpetually hop from distro to distro every other day, if feeling adventurous (or anxious to make a choice) :P
Brandon's passion and dedication deserves all the respect and appreciation - it's wonderful to see the endeavour reaching such new heights!
Of course, it very much depends on the context - technical documents may not need images as much as a travelling blog would. That's why it's important to use plain text as necessary, rather than always. The same applies to any format, including images and even videos. It's about balancing the usage of different formats, plain text included.
With this in mind, it's certainly recommended to start with plain text, but if plain text doesn't cut it, it's much more practical (and beneficial for the information) to just add an image. Ideally, one should always diversify how they store and present a piece of information, if they can afford to do so.
There is a tragic irony in sacrificing the potential fidelity of information in hopes of making it universally accessible.
Its wiki does a fine job at being a pretty good resource for documentation, too, and both ArchWiki & Gentoo Wiki work well as fallbacks.
With regard to Alpine Linux on Docker, the install count[0] of the base image should give an idea (over 1 billion!).
[0] https://hub.docker.com/_/alpine
Edit: clarity
There are other things to consider: our attachment to other people's opinions, perceiving failure as a lesson and investment towards our success, knowing that perfect is the enemy of good, and so on. But that will naturally come when we remove our ego from our work and not give it power.
A step towards overcoming it is to realise this fear and begin using technology as tools, like they were originally intended. This is, of course, easier said than done; however, with time, we can overcome this habit by using our technology with intent.
The biggest obstacle is not the technology, but ourselves. We often find reasons and justifications to continue this habit. Fundamentally, it's a case of self-victimisation and illusion of necessity. "It's too hard to quit", "I will learn new things", "I need to catch up with people", and so on.
I'm still exploring this topic and there's a lot to learn! What I've written above is likely just a (possibly misguided!) part of the whole equation. I'm happy to discuss this with anyone and understand the nuances of this problem, and hopefully a more effective solution.
Coincidentally, I've written about this topic in more detail a few days ago: https://blog.miris.design/attention-atrophy