I was suspicious as heck of this link, but I thank you for being benign.

After 362879 wrong answers you will pass. Or after 2,0922789888×10¹³ tries if it's a fancy 4x4 grid.

To produce 1 commit, I end up rebasing the damm thing at least 3 times. If there is an problem, it's at least 2³ times.

And you have bootstrapped an B compiler on that?

Reaper of the VMAs.

Technical debt means how much work it takes to update legacy solution to a modern solution. E.g. each time a new C++ standard is used, all code written with the old standard should be checked. The work time needed to do this is paying up the technical dept.

Now, if you are lazy, and didn't clean up the code, used the easy and sloppy solution, next time you have twice the work to be done. So the dept gets worse, if you do nothing.

I fckd up a git rebase -i today with git commit -a --amend...

Thankfully git reflog allowed me to assemble the branch again ... from pieces.

I almost posted comment about this but I had to keep it short. The Nvidia has an problem with their driver tainting the customers kernel/system which renders the customer in bad situation. (Of not being able to get support from kernel devs)

The proprietary taint is there for exactly for this reason:

• You load an proprietary module and all bets are off.
• For starters, you cannot tell there isn't a backdoor engineered into it.
• Even if the module behaves well, you now cannot debug the rest of the system any more, because all trust is gone.
• You cannot (at least easily) audit such system.

Nvidia solution to this is breaking the kernel license terms and acting like illegal smugglers in-order to access those sweet sweet GPL-only kernel APIs as lazily as possible. I would say that this is just arrogant and greedy way of doing software development. On top of this the kernel devs get all the blame for their vigilantly of trying to exercise their own license terms.

I think if nvidia would not be this arrogant and vile to the kernel devs, they would already have an proper kernel module that could co-exist between the GPL and proprietary code. If the proprietary code is implemented only in user-space/firmware they can keep their secrets: The user-space <-> kernel-space is an boundary where kernel GPL ends. Implementing such thing would not be easy, but I don't regard it being impossible: look at android.

In extreme: If the hostility continues, kernel devs just might be forced to go invent an corporate blacklist that goes against all principles of co-operation.

Others slightly more sane hw vendors, probably thought: fuck it. It is more profitable to push some FOSS code into the public than keeping the entire thing an trade secret. (I assume this results in the weirdly large firmware blobs that obfuscate and separate the actual hardware from the FOSS drivers)

EDIT: I read more about this issue. From proprietary code vendors viewpoint the current kernel is kind of "GPL or gtfo" situation. Linux kernel doesn't really have an internal stable ABI for modules/drivers. Implementing such thing would require (partly) dropping the monolithic design of the Linux kernel... Such interface would be then able to added to the GPL exemption of syscall users. This would open such big can of worms that it looks to be impossible.

Ison riskin on ottanut kieltämättä, kun on käynyt kiinni. Pahimmillaan voi saada syytteen, vaikka tarkoitus olisi ollut hyvä. :/

For hopping into the GNU/Linux, installing any distro in a Virtual machine or testing liveboot is an good way to to start. The first choice of distro has no meaning. My first was Knoppix on Win98 machine. Tried Ubuntu. Linux Mint got me hooked ~2014, moved to Arch Linux after Antergos. I'm still using Cinnamon DE.

Some "funny" realizations I have made over the years:

• Distros are just vast collections of the same software. The choice is simply what includes your subset.
• Most of the bad rep is missing in-kernel driver for device. Once AMDGPU got usable everything changed for me.
• You can "copy-paste" the entire system into different disk, plug it into another PC and it's like remote accessing the original.
• It will feel like learning a new language, every time you need to something new. This just fact of life.
• If you want to be "bad person": find the exact lines of source code and who wrote them. Then curse that person and the program.
• If you want to be mediocre: post an bug report. Maybe it is fixed asap or put onto "wish-list" and forgotten.
• If you want to be an amazing: donate code. Like actually write it. But be warned, the other users are also like vampires, really picky and demands are unreasonable for the time required. If nobody does this then the software turns into stone.
• By popular vote, some things have surpassed their black boxed counter part and there is no equivalent black box to be purchased. It has become free-software-only.

From above, the making of bug report/feature request is an introduction point into an amazing community behind the software you used. It is not an black box of faceless shareholders.

The occasional awareness tests for Linux users:

• When is the new kernel released? I must have the newest kernel.
• Update removed the floor you were standing on.
• The horror of installing anything on windows makes my skin crawl.
• The horror of accidentally pasting "rm -rf" into prompt and knowing it was yourself who pushed the button.
• No back-doors, unless you installed one.

This post is literally an pwns-list of users admitting what they use as password manager that may be stolen.

I encrypted an file, I put it on a device and mostly forgot it exists. Now if service locks me out I have go hunting.