garaetjjte

>how to know what good/bad code looks like, and if it matches what you're truly asking for

And how you would know to do that, if you're not writing code?

Trivia: because IEEE 802.3 working group was formally in charge for standards of "local area networks with CSMA/CD", 1000BASE-T has half-duplex mode defined (which nobody implemented) as otherwise it would fall outside of working group purview.

If you think Steamworks is bad, you haven't seen Microsoft Partner Center...

How? Once they realized Cell isn't going to cut it PS3 just included Nvidia graphics chip.

In Win16 all instances of executable shared memory (that's why there's hInstance in WinMain). But that should be transparent to user if implemented correctly.

Except Excel, which wants to act like single application with multiple windows.

Why do you think Orange is using Uceprotect? It seems unlikely that big corp would use some weird unknown list.

No, these two elements are not related. Day/night switch is for panel backlight. Current meter indicates current drawn by rail switch motors.

"We bricked your board on purpose even though it actually might work fine" isn't good image either. Like, they know they are doing a bad thing!

They did eventually design their own clean-sheet instruction set for Z8000.

It's not secret to the administrator though, as they could know who was assigned what secret. I think it could work like: before voting, you go to an office where they verify your identity and let you randomly pick envelope containing unique number from a box. After voting all votes are published and you can verify your vote was counted, but nobody else knows your number.

>Pretty much the only use of "reversed subtraction" instruction on a 3-operand machine is to implement NEG and NOT

I would argue that if you have sign-extended immediates, "imm - reg" is more useful to have than "reg - imm", as second form almost entirely overlaps with "reg + -imm".