https://en.wikipedia.org/wiki/Grizzly–polar_bear_hybrid#Anci...
39 karma · joined June 15, 2022
https://en.wikipedia.org/wiki/Grizzly–polar_bear_hybrid#Anci...
When they're too comfortable around humans, it's a dangerous situation and unfortunately requires open carrying a .357 or 5.7 outside. Animal control won't relocate them until they cause a problem. If someone won't defend their family's or their own life, that's their responsibility and lack of preparedness.
But seriously, I miss Pythonline, gopher, finger, IRC, and sunsite.
If women's razors cost more than men's or generics, the rational decision is to skip pink.
Memory issues can be caused by the PSU, motherboard, the CPU, or the memory itself. Personally, I always run memtest86 and memtest86+ for 2 days on any new components.
Out-of-date but pertinent: https://cr.yp.to/hardware/ecc.html (c. 1999-2006)
Other risks: https://defcon.org/images/defcon-21/dc-21-presentations/Schu...
The mitigation of bitsquatting requires ECC in network gear also. Furthermore, ECC isn't just about the memory type but having integrity in data buses, caches, storage, and network protocols also.
Home system is 96 thread, 512 GiB (16 x 32GB ECC Registered DDR4-3200), numerous SSDs and HDDs running RAID.
Pedigree gets noticed as a social and business scarcity signal, and ease of opportunities and expectations ensue. "It must be good if it says 'Mercedes'!" (just don't check the used car ratings for that model not built in Germany)
What I noticed was pedigree dulling or "overload" amongst high performance individuals from relative overachievement backgrounds like EE/CS and MD IITians + Ivies. At that point, they're "Mike", "Bob", "Venkatash" and the titles and diplomas are hiding in the corner somewhere. The ideas and work were central over an antithesis like: "How can you help my personal-professional brand get another book deal, startup funding round, and TED talk?". One time, a new software development manager came in and drove 5 developers into resigning by trying to micromanage and impose ", Ph.D." authority (a type who belongs MENSA and brags about it) on them. Sigh
The smartest successful people I've known are/were decent people. The latter might have something to do with it. I've seen enough gloriously cocksure, arrogant individuals set themselves up for hubris like Theranos.
There are managers who refuse to listen to their own people. This is where MBB consultants come in: talk to everyone, listen, and deliver fancy brochure-level template presentations with data and input from their own employees. It's the same or variations of recommendations that are listened-to because they cost more.
Also, an ignorant of the politics and business generalist business expert can more easily notice if there is anything amiss by entering as a novice with fewer vested interests.
(It's the sad and cynical exploitation of tribal, nativist nationalism containing aggressive, neofascist, pining-for-the-past-more-than-usual, and anti-intellectual sentiments.)
Personally, I prefer goat brains, monkey testicles, and the shrunken heads of vanquished enemies.
What most LSPs do is approximate it rather than worry about perfection and deliver nothing.
Alternatives: if you don't mind your eyes bleeding with C++-verbosity and tracking liveness yourself, there's Rust. Sure Go looks cute until you have a million users emailing you trivial questions they should've asked a group.
And if you want something similar to Crystal but with even stricter and more granular semantics than Rust with an even smaller community. there's Pony. It was built around the Orca GC. There's Nim too. Finally, one can use Haskell to built that critical payment service and maintain absolute job security. Meanwhile, the Erlang/Elixir OTP stack stays performant, although no one is quite sure how to package, deploy, and manage its lifecycle properly.
With enough effort and care, a frictionless experience can be made with a TUI should some "Jetbrains" come along and try to make a commercial product out of it.
What takes appreciation is the differences between a DOS game executable and a modern hyperscale backend app server fleet. gdb-server ain't going to solve many problems on 500k boxes.
0. Human diurnal local time
1. Universal time similar to 0. but without local offsets - UTC (UT1)
2. Universal monotonic time (within comparable gravitational reference zones) - TAI
These already exist. There is nothing to add or remove, but to do things differently that have already been recommended rather than sticking with insane traditions for another 25 years wherever possible. UTC (UTn), GMT, are insane for timestampping.
Use TAI essentially everywhere and calculate it later as UT1 or local time. If you fail to do so, you risk discontinuities and security vulnerabilities. This is why you should and must use TAI64[N[A]] rather than UTC because UTC is not monotonic. You can get UT1 from TAI by downloading LS tables and doing the math yourself. It is rare to find UTC-centric code implemented correctly.
This isn't rocket science, it's first principles of recording data that doesn't vary nondeterministically in forward time.