Hmm... this is weird thing to admit, probably should've guessed by my tone from 2 blogs earlier, I was on a roll on writing blogs until my free time was consumed by watching the world cup... my bad guys! anyways I wanna talk about my openbsd experience again, I mean I was thinking like "man openbsd is so cool, but I want some stuff that only exist in Linux like Wine and a cracked java minecraft client! XD". When it comes to hardware support and performance, the penguin dominates everything, but what Linux really misses and what every single Linux distro misses is a fucking usable operating system that doesn't give you a massive headache, look, hear me out for a second here, I guess. There are Linux distro that are called the beginner Linux distro of the "Just works" people for the majority of the people doing dumb shit in tech anyways not even learning the essense of using a computer in the first place... *sigh* this is the state of the- wait I'm getting offtopic... So like.. you know Linux Mint, easy to use Linux distro, uses Cinnamon DE (whatever) and their own set of utilities to maintain the system, normal system stuff, but a DE taking around 100-200 MB of RAM (RES, Resident Memory, AKA the "active" memory). It's pretty much feels like it, when you are thinking in terms of idiotic, normie like brain... like calm down and listen to me for a second! Well people back 30 years ago, who were the normies about tech at that time with the same "no time on my hand to learn programming" tend to atleast respect the aspect of computer systems and be knowledgeable enough about their surroundings so that they can make intelligent decisions, that simple. First, people knows how a computer works... right? Well no they don't, nowadays I mean, or... I mean I guess even back then, but not as much antagonizingly no. Well, the thing is, you don't really need to know how a computer works, that's honestly a waste of time... but wait, how are you going to operate a computer? AHA, that's the thing. You really don't even know how to operate a computer unless you know about it. That is why you are meant to learn the damn thing you- ok wait, that was my bad.

Ok well we are in this deep might as well. First thing you see a technology, and you are told to operate it. How are you going to operate it? first learn how to operate it. If you are going at it professionally you are gonna read the fucking manual of the damn computer itself if that thing existed in the first place :( but it doesn't so you have to get some kind of help or read a book by some author who is really good at operating computers and then you learn to do it as well. Hey you DID learn how to fucking operate right? And it is something that takes the first 3-4 months at the beginning of your training. If you are doing it professionally you after these much months should pretty much be more skilled than people who do these as a hobby in 3-4 years, but that's just that. Well first, you are to learn about a few things to operate and understand and maintain a machine that you use, this is PRETTY FUCKING IMPORTANT. First things you'll learn about IT in school would actually BE those things that people argue they never LEARNED, aaaaaaa- Well, you learn about RAM, CPU, GPU, PSU, and HDDs and SSDs and all that if you didn't you might actually be a fucking idi- Here's a quick sum up of these things that they teach kids in 3 years into ONE SINGLE PARAGRAPH, well here we go:

PSU is the Power Suppy Unit, simple, it plugs with your wall and draws power that it passes to the motherboard which houses the CPU, and literally every other components that will be connected, like RAM, GPU, storage units. The motherboard is the main part of a computer, which is basically a fucking electrical curcuit that contains transistors, capacitors and a lot of machinery magic. The motherboard exposes some IO, Input Output ports on the any goddamn side of the damn motherboard, mostly on desktops at the left. the RAM is a memory like a storage module, but it is volatile and is probably the most insanely fastest of storage modules, but well SSDs are kinda getting on that level though... but basically it is the storage module on the motherboard that is used for fast access of data, data passes in the RAM very quick and its also random, that is why it is named: Random Access Memories, great name right? next up is the CPU, basically the central processing unit, where the main processing happens. The CPU is basically the master of all components as it orders everyone what they have to do and stuff. At the beginning though, the control is upto the motherboard with the BIOS that lets the handle to the CPU after disk drive is found and there is operating system ready to boot. There is display to connect to see the boot screen pass by, that basically is done by the GPU obviously, its the graphical processing unit. the "disk" means a hard storage device module on the computer that stores your "hard" data... I'm not sure how to explain it, it is basically a data storage device that stores data that you can access on will, its called a ROM in IT, but what the fuck is ROM lmao, its clearly not ROM... but oh well. this hard disk stores the data that makes up your operating system with your data on it. The disk is partitioned into 2 or more to store the OS map. the disk's first few megabytes which is always reserved for the information the motherboard BIOS will read to know what the fuck to do with the damn disk. Like find the boot partition, and root partition. an additional EFI partition for modern systems. the EFI/boot partition contains the bootloader to load the operating system from the OS's BIOS, that loads up the operating system as programmed by the bootloader. The bootloader mainly loads the next most important thing from an operating system which is called the Kernel. The kernel is the 2nd layer on top of the hardware itself. The motherboard BIOS handles initiating all the hardware components and then passes on the controls to the Kernel of the operating system. There are a lot of kinds of hardware out there, and the kernel needs to be able to, for what it REALLY needs to be for, to support those hardware. It really should NOT support literally every single hardware for no reason... and then after that the kernel utilises a ramfs usually known as a initramfs to initiate the actual root system, then start services for the base system and pass on the user to the login screen which logs you in as a user in the system, unable to mess with the root system and ruin the operating system by mistake. This is where operating systems differ. but the general idea is that you get a DE, Desktop Environment, that has the application launcher that launches your work applications to start being productive... basically. That's how you get into a computer, and now you get a quick idea of what goes around in a computer, cool?

Well that was the ground up, lets talk about the operating system itself now. When it comes to operating systems, It is basically a user admin system that has worked for 50+ years period :o that's the Unix system, a legacy that was popular since the release of BSD. Most of the weird estoc operating systems of today like Windows and newer* Mac OS are basically just that... being hey the fact that Mac OS is actually still probably pretty unixy still. Windows however takes up 90% of the marketshare, right? I wouldn't know, I'm not a fucking idiot. Windows is the most horrible of operating systems from the bootloader, to the partition scheme, to the partition NAMING, to whatever else they re-engineered. This started of a backlash against AT&T Unix and Lawsuits... cool, lets not go to that actually, basically many other kinds of operating systems, some good, some weird some for the corporations and stuff, and that is where Microsoft started, it was a software business for other corporations. There was other operating systems that targetted for building servers. And there were operating systems to handle each and every kind of task. But being corporate-like, Microsoft won over the more targetted and more useful for the corporations because of their... of Microsoft's co-operation. Hey, if you are building something why not choose Microsoft and let us build it for you? or something like that, that's the corporate style BS, but oh well whatever. There are offices in the society for god knows what kinda work that goes on and helps the society and they need computers to help them print more documents on paper and pass around people and print more and print more and prin- I mean... Ted Nilson at the golden age of Unix had a foreboding of the correct ideas that ended up being right some not aknowledged yet still. Mainly the "Free text from paper", if you are going to give someone to read something, and they probably have a device on hand, why not just send the image or text over the internet or some kind of other radio. This is the idea of data being paperless, you don't need papers, a future where people will not need papers and printers, it would make the office, or the workflow much simpler and much more sane. things was DEC and terminals back then into digital stuff that boasted possibilites for graphical interface, and they did, there were possibilites of tools that could be made for even greater productivity. With people with huge ambitions but less resources to work with, they worked their brain to get to the assembly grind to write programs that would be useful to everyone. by 1995, we had those office programs like word, excel and whatever the fuck you probably have heard of. Running on those "slow" computers back then, and everyone using them. They were pixelated, but snappy and very useful for productivity sense. The idea is that software should do more work while taking less resources because you didn't have that resources back then, and that made programmers of that time the greatest programmers. There's a lot of legacy kind of code that is quite interesting to look at because it always has some weird quirks to eeek out performance out of less resources, which is something people back then were really good at.

Fix the wrong ideas. What do you want to use a computer for? what work do you need to get done? accounting? what kind of accounting? what do you ultimately want? have you done it manually by hand before? and you wanna recreate that procedure in a computer? and automate some parts? Hell, thing kind of thing you can even do on a 1993 computer. No kidding. The answer of course will not be given to you because of the corporate oriented this world is, people tend to think that way and they never learn how to fucking use a tool properly. First, you'd imitate the parts of the thing you do in accouting book in a text document you open up and start putting the things and still doing the calculations manually, because the calculations you need to do are not in a hurry, therefore you have the time to do it by hand. But if you want it to be quick so you can be productive and do more work beside it, then you'd need to automate column calculations, something like a tool that would calculate those values. In Unix, your answer is something most people will look at and tell you "that's a pain in the ass" while not knowing what they are doing is being done with 1/100000 the resources THE SAME DAMN WORK. These people buy new computers and powerful machines do simple tasks because they use these expensive ass programs... The answer is single-entry plain text accounting in seperators, then you will use some program to calculate, if you have a accounting book that accounts both expenditure and income, and you want to calculate the total income in this month, and the month is February, then you would grep in a Unix system, than pipe the data (you can take that literally actually) into a cut program that will extract the value, then pipe the resulting data into something like awk that you can organise and calculate the values. done! oh that was pretty easy! except that you don't know about grep, cut, and awk by default somehow, you are supposed to learn it but if you are like me and wanna get the fastest way to handle it, search what the actual thing you want online and find someone who already made the command strings in a shell script for you. Perhaps there's even program tools for aiding your plain text accounting. Similarly any other work, you need software to it. Mainly a work that you are going to finish with any kind of tool is a problem that you are going to solve with your brain. For that you need to struggle and learn how to get that work done the fastest way and also in the best way posssible, and Unix always has an answer for that. For any kind of work, you need a required software, but there could be a better software, and if it uses less resources and more efficient, there's no reason not to use it. Something like video editing becomes 100x easier in Linux only because of ffmpeg, you can even do everything with just ffmpeg but that's not really going to eek out any creativity, but when it comes to manipulating, trimming, croping, etc, the entire file, ffmpeg helps with that. Well and then you might use something like KdenLive, I guess, however professional movie makers use Davinci, only because of their color grading whatever stuff, sure. You'd wish there was something that does what Davinci does but might lighter, FFmpeg of course CAN do it, but its the matter of plausability, if you somehow learn and become a pro at ffmpeg-ing your movie, maybe? Well video editing with ffmpeg feels like you are using your own kind of editor, and you feel like you are building the video on a much higher level as well, higher technical level. that's what I felt like when I tried it, and I wanna try making something whole with just ffmpeg because it just feels like the kind of thing I might be able to use, but when I think about effects and whatever not, then again, maybe someone already has gone to that level and can tell you what's up with ffmpeg video editing itself.

Anyways, whatever I mean is that, work, hobby, whatever, that includes any technical aspects of tools, you are going to struggle. The struggle is important. Do not go against struggling because that is what makes us human. Every single time I want to do something, I research, struggle, fail, and solve the problem and find the most efficient answer that I can be happy with. And if you Unix-pilled like me, whatever you make is something others will see as genius because "it has no right to be this simple!" I like to keep it simple, honestly, simple in the technical level if that makes sense, people are not even simple on any way because all they learned is how to click buttons and type on a keyboard, and how to turn on a computer to launch programs to do whatever they are doing, not organise their files, simply, they don't know how to operate a computer, they are just lucky it works like they wish it to do, because someone else already struggled for them on that regard, and well most of those struggled result that people follows are stuff that you probably don't struggle much with and learn up the stuff in 2-3 weeks anyways, its part of your work, of course you wanna know how to do it. But you are not even intelligent even to notice that if your working effort is going in pointless directions and you wanna get rid of the inefficiencies.

You know what is the most hardest thing in the world to achieve? simplicity. Say you have to do a job, and you want to pick a method, you would want to pick a method that would be simplest and will not hurt your brain in the meantime. Your method at the beginning will have some nuances, and after sometime with added experience you will cut the vines of inefficiencies then, well achieve simplicity. But the work done probably could be the same, but what you have done is that you have done it intelligently, as expected of a human being and not someone who is corporate slave- a robot. The same person will feel pride that they atleast work and show it off or something to the others, and waste time rotting their brain. The thing is simple, achieving complexity is much easier than simplicity, it is what separates the intelligent and human ones to the stupid and robot ones.

This influence of abstractiveness in a job has killed the work nature. Every task is a problem for the worker to solve, let them solve it in their own way that still suites your requirement. If you can somehow do the same work people did back in the 90s and perfectly, you only ever need a antique machine, grab a Unix handbook, give a few months and you are on the roll of working probably the most simplest way that doesn't give you a fucking headache while you are working, and because you have more technical tools at your disposal at will and you have maximum interoperability you will be able to do any kind of work and also be really simple at it as well. Technical simplicity over non-technical complexity.

"Linux people do what they do because they hate Microsoft. We do what we do because we love Unix.", said Theo De Raadt This is what truly hit me home. And when it comes to operating systems and operating it, there's nothing better than OpenBSD, from the setup to the userspace and the feeling of using it just gives you the air of completeness. It is like a well made house, clean and made the right choices. But in this world an operating system like OpenBSD is just a house full of struggles, but the fruit from that struggle is something everyone will appreciate. OpenBSD is the first truly operating system that made me feel like a usable operating system. Because I have the sense of security, their practices and also you can say that OpenBSD is truly the minimal operating system because the entire specs you need to run this Unix system is literally 64... 64 MB of RAM, no kidding. While Linux stays around 120 MB on an install even on alpine with xorg, and no less than that. while OpenBSD sits around 24.. 24 MB. this is like a 100 MB difference, whatever even is goin on Linux I can have no idea honestly. It is just a bloated mess, from the kernel, to the userspace and it doesn't feel good to use that kind of operating system. I'd be fine with Linux all day long only if I had not known about OpenBSD and not have experienced it, now that I have, Most people in Linux waste their free time tinkering with Linux operating systems on their 2nd 3rd hardware and learn stuff, instead of using that time to probably read a book because tinkering is cool, but I honestly think being more producitve is even more important. Unix is multitasking machine, you are here to technically maximise your multitasking. Of course it is non-technical and not complex, embrace this struggling.

OpenBSD doesn't beat Linux in performance of course, but there's more to operating systems than performance. It is performance sacrificed for maximum locked down security. When it comes to operating system, the first and foremost aspect of it is "how secure it is" if security doesn't matter then forget about the damn operating system, Linux GTFO man, like nah, I cannot really bear to even look at Linux to be used on my laptop, that needs to be secured in case of theft and all that, and when like the SSD dies, because the drive is already encrypted, so that gives you that sense of security. OpenBSD code conformance and quality is a million times better than others, their standard libc being much safer to use. I really cannot find any complaints when using OpenBSD that I do when using Linux. ALSA being shit, and kernel being bloated, Glibc everywhere, GNU/Linux. Linux is not Unix, and can never be even if you try to achieve peak minimalism in Linux, you will be left with "But why does it still use 100 MB of RAM?" like yeah I get you... That's just how Linux is, a bloated mess. you could consider to reduce the kernel code and all that a lot but you know what. Fuck that. dealing with Linux sounds like a major pain in the ass in the aim of simplicity. Rather better to just OpenBSD, honestly, the base system is tailored, now do whatever you wanna on top of it. You will miss a lot of stuff you probably had in Linux, but that's fine becuase you have an actually much simpler and less headache of a system.

Then again I was a bit unfilled with openbsd, or so I thought when I hopped back on Linux, like Void linux, it sure feels like a really good Unix-like distro, but ultimately being linux, it is Linux-like, instead of truly Unix-like. So here goes to OpenBSD, the best operating system of all Unix operating system, probably and maybe 2nd to the truly unusable Plan9 though lmao, Plan9 is ingenius, but I'm not sure if it is really usable in this day and age.

That's it for today, be based in OpenBaSeD! I don't think I can ever leave OpenBSD, the Unix-pill is too strong.