_rtld_global_ro

niche.com have public data, for example NY suburbs public school teachers' pay are pretty high[1], though I still doubt it will be the same as sr swe, then again those are totally different type of jobs, with the former being much more stable and has a pension.

[1] https://www.niche.com/k12/berry-hill-elementary-school-syoss...

Given Intel's AVX extension could cause silent failures on servers (very high work load for prolonged time, compare to end user computers), I'm not sure it would be a big win for servers either: https://arxiv.org/pdf/2102.11245.pdf.

You can use 1031 exchange to avoid that.

Get ACA, should be a lot lower than $1200/month if AGI isn't really high (assuming unemployed), now if you want CORBA that could be a different story.

One of the best talk I haven't seen for quite a long time, thanks for sharing.

This restriction was not in place from the start, what happens to US citizens who have funds in binance_dot_com before this restriction? It's hardly clean in any sense.

It says I'm from US, they're not serving US customers, and I must identify myself as a non-US person, or I won't be able to transfer any funds at all. See this popup notice upon login:

``` Service notice Dear user, as we perform periodic sweeps of our existing controls, we recognize that you are trying to access Binance from a US IP address. Please note that as per our Terms of Use, we are unable to service US persons. If you are a US resident or citizen, please register for an account at our partner platform, Binance.US, where you can experience the same industry-leading trading technology as available on Binance. If you are not a US person, please complete Identity Verification to prevent any restrictions to your account. We thank you for your continued support and apologise for any inconvenience caused. ```

IMO this is just a terrible and shameless excuse to take customers money away, I'm surprised nobody have taken action towards them.

It's not the case for me, I can login but my funds are a lost cause I'd suggest you transfer them out while you still can. On a hindsight I have no idea why I'd used it, it shady as hell I hope US sue them to oblivion but I doubt it would happen in a meaningful way. (rant)

gentoo is too addictive, unless you want `emerge` as part of your routine

It's only true if the program is about to exit, for long running programs like daemons, ``memory leak`` is still a thing.

errno is thread-safe as it resides in TLS. Part of libc such as pthread is very hard, and so does the dynamic linker. The latter is supposed to handle TLS data as required by TLS/elf spec, which more or less requires a full thread/pthread implementation. As a result, it is rather difficult to break down libc, without writing the whole thing in the first place. golang might be an exception (no linkage against libc), but AFAIK it doesn't use TLS.

It's a pretty hard task to tackle libc (not just string functions, obviously), maybe for the same reason there're only a few libc implementations (support full dynamic linking).

It become more or less just a catalog, often times spent close to an hour just trying to find something might be interesting (not totally shitty), and that's pretty much it: couldn't find anything, just browsing their catalog, with time wasted.

shared library can be expensive as well, the dynamic symbol lookup could be a lot more expensive than people would assume.

Thanks for the correction

It's actually quite hard to do exit cleanups, even by putting functions into `.__fini_array`. The reason is because some signals (SIGTERM, SIGKILL) cannot be masked, when a thread/process (`task_struct`) got `SIGKILL`-ed, there's no way for application to run functions (including .__fini_array). Things can get more complicated when a thread calls `exit_group`, which is also recommended, cause all other threads in the same process group receive `SIGKILL`, hence none of the other threads are able to run any code after.