Notices by 🇺🇦 haxadecimal (brouhaha@mastodon.social), page 2

@nixCraft It was inevitable that a browser developed by a company with a business model consisting almost entirely of advertising revenue would do this, but when you dangle shiny new software in front of most users, they don't spend much time thinking about the deeper ramifications.

You can't keep dancing with the devil and ask why you're still in hell.
– Kynna Claire

@arstechnica The lists already exist! They're in the billing system. They don't want to admit that what they're actually opposed to is transparency.

I will be available for consulting starting at the beginning of May. I mostly do embedded and low-level stuff. Skills include programming in C, C++, Python, etc., FPGA development in VHDL and Verilog, and network protocols including the IP etc. and Bluetooth Low Energy.

It's unfortunate that the world standardized on integer overflow not giving an error. Error on integer overflow should have been the default behavior, with programmers having to explicitly choose wrapping without overflow when that was desired.
Of course, that would also have required explicit signed and unsigned arithmetic operations, because overflow (and underflow) differ for signed vs. unsigned.
Now the no-overflow-error behavior is entrenched in C and C++.