Oh Oh !!! Today is the 8 bit register overflow day....Happy 8 bit register overflow day to all 16bit registers..

While I was working on a university project with my team, a teammate asked me why the window of the program in my screen was bigger than in his. I simply answered him that his screen was a FullHD one that had a 1920x1080 resolution, while mine had a lower resolution, and he was like "Noo! This isn't a fullhd screen, it's not so sharp".
So I showed him the "1920x1080" sticker right below his screen, and him again "Yeah, it could have this resolution but definitely it's not a FullHD screen".
- Ok, as you say...

The same guy two days ago was talking about creating a GUI in C.
I told him that C was the wrong language to build programs with a GUI, although there's some very old libs that allow you to do that in 16bit.
And him again: "Ok but Linux (distros) do that and the UIs are great!"
- Do you think that all the fucking Ubuntu/Mint/any distro code is written in C??

The funny thing is the arrogance with which he says all these bullshits.

P. S. We are attending the 3rd year of Computer Engineering.

We are so fucked up at our company:

While the support for our client hardware is running out, our operation departement has just found out that Windows 7 is no longer supported on new HW. Well, that for itself is not bad, but we have a really old tool for reporting our daily work. And because that mo*fu*ing piece of customized software still runs in 16bit mode, it will not run on Win 10 anymore.

Alternative solutions are too expensive, so I see that we will have to port that crap somehow from 1997 to 2017 ourself 😲 Replacing is not an option because there are a ton of Excel sheets connected to the database, even the company balance is made with that data (and also in Excel). At least it is our CEO which has built that crap. So he has to pay for his twenty year old sins!

A few weeks ago a friend was teaching me about 16bit numbers because we were making one in C# with a function, but he said we need two numbers for the function to work.(so as an example were gonna use 0, 2)

Now I didn’t understand how two numbers were supposed to make one. And my friend could not explain it to me. So I researched the topic all day and the epiphany happened I realized I was looking at it all wrong. I shouldn’t be looking at it as 2 decimal numbers but 2 binary values or two binary arrays forming one byte array with a length of 16.

!rant
Did any of you decompiled 16 Bit DOS program?
I need some help.

So this semester we're being taught C/C++ which now seems to me like a distant memory from high school days.
The professor decides to use visual studio for something as trivial as variables and pointers and as I went through the syllabus, it won't get any harder and will stick to this simple stuff.
As much as I find VS awesome, when there is a simpler approach available, why go the tougher way?
The same could easily be achieved from a ~15 compiler or even that 16bit compiler we used in our high school that couldn't even use mouse as an input. Am I over thinking this? .-.

I needed to align instruction execution to a 64bit boundary, for custom CPU architecture that I'm building. Basically the ISA had 3 types of instruction lengths; 16bit, 32bit, and 48bit. The core did 64bit fetch from the Instruction Cache, the issue was that if an instruction was in between two blocks of data I needed to fetch two blocks. That would impact performance a bit. So I had to modify GCC sources of the ISA that I'm using. So instead of doing it the right way, I just did it the lazy way and modified the GCC backend to print

.p2alignw 3, 0x00ff, 4
.p2alignw 3, 0x00ff, 2

On each 48bit and 32bit instruction to generate NOPs. And it did work lol.