I follow Lina on mastodon, and it's just funny to me that cutting edge Linux video driver development is live streamed by a Japanese cat girl vtuber.
mrkite
joined 2 years ago
I have hooks that reformat on write, so I use :w constantly. So :wq is easier.
Think his tombstone has :q! on it? I love vim, I've used it daily for 25 years now.
I have a Sun Netra X1 sitting on the floor that I've been meaning to get rid of. One thing to keep in mind with the Netra and Sun Fire servers: they have a System Configuration Card in the back which holds their MAC address, NVRAM settings etc.. don't buy one with it missing.
Even worse. Auto generated comments just copy the how and not the why. If the code has a bug so does the comment.. and if you fix the bug but not the comment somebody else might change the code back to match the comment.
I remember the 90s when both mac and windows crashed on a daily basis. When was the last time you saw a legitimate BSOD that didn't involve hardware failure? When was the last time you had to reset the PRAM on your mac just to get it to boot?
Are you me? I do the exact same thing.. only I also made a Makefile to do all the stow commands for me.
I think I kind of dislike the generalization on generation.
There's a lot of pitfalls in that direction.. but there's also no denying that there's an entire generation of people who grew up equating using computers with programming computers.
Our Apple IIs and C64s booted into BASIC. That was the interface you learned. Just using the computer literally involved programming, even if it was tangential. My grade school "computer class" where we learned how to use a computer, was focused on programming the turtle to move around the screen with LOGO. I remember a time when "repeat" was the longest word I knew how to spell because of that class.
Basically, you have to go out of your way to learn how to program today, involving downloading specialized software etc. In the 80s, you were ankle deep in programming just by turning the computer on.
I'm still holding out for a kit version. Maybe someone will make an open source clone.
As comprehensive as that is, they don't explain why we use 2's complement for negatives, and that's a shame because it's a really intuitive answer when it's explained.
For the following, pretend we're dealing with 4-bit numbers.. 0000 to 1111. Just to keep the examples sane.
With 4 bits, we can represent 0 to 15... but let's add negative the dumbest way possible. Just make the high bit negative, so 0000b-0111b is 0 to 7, and 1000b-1111b is -0 to -7. We have 0 and negative 0, which is weird but let's ignore that for now. Does this system even work with basic arithmetic? Let's do a sanity check. If we have a negative number and add 1 to it, it should get closer to 0. -4 + 1 = 1100b plus 0001b = 1101b or -5. That's the opposite of what we want.
So to fix our problem we just need to reverse the order of the negative numbers. We can easily do that by inverting all the bits. 0000b-0111b is still 0 to 7, but now 1000b-1111b is -7 to -0. Does the math work? Let's see: -4 + 1 = 1011b plus 0001b = 1100b or -3! It works!
You'll find ones-complement actually works quite well for arithmetic. So why don't we use it? You'll recall we ignored the fact that there is a positive and a negative zero. Let's address that now. The two zeros means comparisons are a pain. 0 != -0 without a bunch of extra logic.
It's a simple fix. What if we shift the negative number line over so the two zeros are the same? Simply add 1 to the number after inverting. 1111b (which was previously -0 in 1s complement) rolls over to become 0000b, which is 0! 1110b (-2 in 1s complement) becomes 1111b and we'll call it -1, and so on. It even gives us an extra number because 1000b represents -8, which we couldn't represent in 1s complement.
And that's why we use 2s complement, and now you'll always remember why and how it works.
It's probably an emulator. All the kits you can find online run raspberry pis or similar. I would totally be interested in a TTL logic-based replica.
Therein lies the biggest lie in development. There is no career path. I've been programming professionally for 25 years, and in all 25 of those years my primary function was to write code, because I turned down any promotion that would put me in management and away from doing what I love.