dmt314159
Pointers are replaced by 128-bit capabilities containing what operations are valid, a 64-bit base address and a size. These capabilities are unforgeable, so trying to play with "unused" parts of 64-bit pointers simply won't work.
FreeBSD & Gnome are running on hardware after minor source-code changes, along with a significant proportion of FreeBSD ports collection.
As well as ARM, Microsoft is interested: https://www.microsoft.com/en-us/research/project/portmeirion...
"the ticks can attack en masse and drain young animals of blood so quickly that they die—an execution method called exsanguination"
https://arstechnica.com/science/2018/08/us-invaded-by-savage...
it can be interesting looking in nameserver logs for hosts making successive queries for variations of FQDNs based on their search paths, and/or A vs AAAA lookups.
some responses treat as serious, others consider clickbait
https://news.ycombinator.com/item?id=20592774 https://news.ycombinator.com/item?id=20582004 https://news.ycombinator.com/item?id=20565024 https://news.ycombinator.com/item?id=20561136 https://news.ycombinator.com/item?id=20554229
They only directly control one lever in the economy, interest rates augmented by QE-purchase of company bonds in Europe & US.
In retrospect, they've been caught in a downward spiral of interest rates because politicians have been unable to add pro-growth policies.
Unfortunately the "wealth effect" of shares in the US, even after Trump's unaffordable tax-cuts, has been channelled towards shareholders (via dividends & buybacks) rather than wage increases or capital investment.
Something's wrong when companies can't find worthwhile ways to spend money investing in their own future, but instead direct profits and BORROWINGS into share buy-backs.
I do suspect one of the factors encouraging buybacks is that executive remuneration is often based on the share price. I've tried searching but haven't found anything suggesting executive remuneration excluding the effects of buybacks on share prices.
Both of the projects also generally required knowledgeable people as they're in specialist areas.
Like any implementation of NTP, NTPsec needs to work at the protocol level, but I don't know whether it was practical for the NTP project to accept the degree of change in it's codebase that the NTPsec people wanted. In an ideal world the fork could have been avoided and a more vibrant community of developers would have happened.
https://www.sqlite.org/famous.html
notably Airbus, which may be (one of) the companies
"At about that same time, some avionics manufacturers were expressing interest in SQLite, which prompted the SQLite developers to design TH3 to support the rigorous testing standards of DO-178B.
The first code for TH3 was laid down on 2008-09-25. An intense effort over the next 10 months resulted in TH3 achieving 100% MC/DC on 2009-07-25. The TH3 code continues to be improved and expanded."
Apart from the modules included in the DateTimeDistribution, there are many others as returned by https://metacpan.org/search?q=DateTime
My favorite use DateTime::Format::Baby;
my $Baby = DateTime::Format::Baby->new('en'); my $dt = $Baby->parse_datetime('The big hand is on the twelve and the little hand is on the six.');
"The inet_pton() function does not accept other formats (such as the octal numbers, hexadecimal numbers, and fewer than four numbers that inet_addr() accepts)."
or see https://hackaday.com/2016/09/25/rubidium-disciplined-real-ti... https://deltafabri.wordpress.com/2015/03/08/under-60-ns-an-a... I'm not sure the TAPR clock block is still available
several modules are listed on https://www.microsemi.com/product-directory/timing-synchroni... both for a rubidium oscillator & a Chip Scale Atomic Clock https://en.wikipedia.org/wiki/Chip-scale_atomic_clock and from Jackson Labs http://www.jackson-labs.com/index.php/products/csac
some links on https://www.raspberrypi.org/forums/viewtopic.php?t=212429