skylabmelody

My suggestion is straight from the C++ guidelines by Bjarne Stroustrup and Herb Sutter (ES.102: Use signed types for arithmetic), for reasons that you don't seem to grasp.

I would suggest to never use unsigned int for values that will involve any sort of calculations on them (health, damage, speed). This is considered bad practice due to overflow and should be avoided, with the exception of values that are used for UIDs, indexes, bitfields, mask and flags.

Quite incredible that the aviation industry haven't introduces sticks with force-feedback despite video game industry having them for about 30 years.

Probably because it's a patent lawsuit minefield.

By "dual input system" I was referring to the fact that both pilots can apply input into their sticks or trim wheels simultaneously resulting into inputs cancelling each other out or de-synchronizing.

I don't want to minimize pilot errors but I can't stop thinking this dual inputs system easily ranks in the top 5 of the worst design ideas in history.

Probably just behind the MCAS.

Thank you for the Bitsummit coverage, glad to see that the spirit of Sanqua magazine still lives on.

Once you know roughly how ChatGPT works under the hood (see ChatGPT API), most of these claims on ChatGPT seems to emerge from us humans being easily tricked by our own anthropomorphism.

VCs have plenty of billions let's have them do the bail-out this time around.

Really getting quite tired of the misuse of the word trope.