Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "separate drives"
Friend: Hey, can you fix my laptop? The hard drive is almost full.
Me: (Looking through his folders) Maybe it's because of this. Why do you have 3000+ files in your downloads folder? Maybe I should delete some of this.
Friend: No no, please don't touch the downloads folder, I have some very important documents there.
Me: Why don't you move them to a separate folder then? You should organize the ones you actually need and delete the rest. This folder is a complete mess.
Friend: No no, the problem is not the downloads folder, there must be something else. Can't you just uninstall some programs to free up space?
Me: I could, but I don't know which ones you actually use.
Friend: What? You should know!! You studied computer science for this!!
Me: First of all, there is not a single class in the whole 4 years of university called "How to uninstall programs and free up space on 128GB hard drives of shitty €400 computers". Second of all, I don't know why you were expecting me to find a magic button on your laptop that immediately frees up all the space in a hard drive without actually deleting anything. That's not how computers work, you know.
Friend: Hey if you didn't want to help me you could have said so in the first place.
SICK AND TIRED OF READABILITY VS. EFFICIENCY!!!!!!!
I HAD TO SEPARATE A 4 LOC JSON STRING, WHICH HAD AN ARRAY OF A SINGLE KEY-VALUE PAIRS (TOTAL OF 10 OBJECTS IN THE ARRAY).
ITS READABLE IF YOU KNOW JSON. HOW HARD IS TO READ JSON FORMAT IF YOU GET YOUR STYLE AND INDENTATION PROPERLY?!?
SO I HAD TO
BREAK THE POOR FREAKING JSON APART TO A FUCKING DIFFERENT YAML FILE FORMAT ONLY SO I CAN CALL IT FROM THERE TO THE MAIN CONTROLLER, ITERATE AND MANIPULATE ALL THE ID AND VALUES FROM YAML BACK TO MATCH THE EXPECTED JSON RESPONSE IN THE FRONT END.
THE WHOLE PROCESS TOOK ME ABOUT 15 MINUTES BUT STILL, THE FUCKING PRINCIPLE DRIVES ME INSANE.
WHY THE FUCK SHOULD I WASTE TIME AT AN ALREADY WORKING PIECE OF CODE, TO MAKE IT LESS EFFICIENT AND A SLIGHTLY BIT MORE READABLE?!? FML.5
I was supposed to be asleep four hours ago. But I have to say, screwing around with linux distros on antiquated machines I've acquired over the past two years is much more fun. The oldest computer I have with me today is actually the most recent addition to my collection: an HP Pavillion from 2002. It's got a Pentium 4 2.6, and is currently still running XP, though not for long. Thinking of turning it into a little cloud/web server for entertainment purposes.
I might just harvest the hard drives from it and put them into the other Pavillion I have (it's about 3 years younger) to have more storage in one device. Maybe I'll make them both separate servers, one for cloud, one for web hosting. We'll see.
Sorry for the ramble, I usually ramble to my girlfriend, but she's asleep, so I figured I'd dump it here.
Back to doing research.3
I swear GNU/Linux is the pure definition of a badly designed OS/Kernel
1) The separate file system. Of all things, all the set standards Linux uses exFat which can only be read by Linux. Not NTFS, not FAT32, you know, the common ones.
2) Unintuitiveneness and inefficiency of workflow. Linux is extremely inefficient, especially the cli versions, where one cannot perform several tasks simultaneously.
3) It's MESSY. The use of a Terminal is incredibly uncomfortable, because the text is tightly spaced, and in monochromatic in root. When looking at a large chunk of text, my eyes hurt on a deeper level than physical.
4) It's the most retarded way to handle drives. Why not assign drive letters and names? Why is it dev/sda1 dev/sdb1. If I have two drives of the same capacity, I cannot differentiate between them. How am I supposed to know which is my system drive and which is my portable hard drive that I'm formatting? And this stupid disk utility fdisk. What the fuck is that? Why is the command o wiping the device? Why is t selecting a partition? What the fuck?
5) Stupid naming system. Most CLI commands have deliberately stupid and hard to remember names. Also the prefixes to them such as -x -c or -v, say nothing to me. Reading through the manual in white, tight monochromic text is impossible.
6) Error messages that don't make sense. How am I supposed to know what "Error! [err=/dev/null, arch="27xE39Tmx849D" result="success"]" is supposed to mean? A search will cut down the error and I will find nothing.
7) General hype towards it being "focused on developers". It's not. It's really not. As a developer myself I find it absolutely painful to write code on Linux. It's sluggish, requires it's own set of IDEs and software packages.
People say "Oh you can't write and compile code on Windows". Yes you can. Windows has the exact same set of compilers as Linux, like gcc and gpp. Windows has a versatile and powerful command line. It's hidden from a regular user, because its actually user friendly, and is made for people, not aliens. The fact that you have to download a package manager first to access new ones is what flies over many peoples heads.
Go on start a wreck in the comments40
A weird thing happened when I tried to install linux mint on my PC.
Although I installed it on a hard drive (I have another hard drive for windows), my bios tells me that Linux would be on the same hard drive as Windows?? I can assure that it's not the case, as I plugged out the linux drive and grub couldn't boot Linux anymore, just windows. Plug back in, linux bootable. Ok fine?
When I installed linux I panicked for a moment, as I thought I had it correctly installed separately, instead it would have become a dual boot, according to the bios?6