Readit NewsBitfield packing rules get pretty wild. Sure the user facing API in the language is convenient, but the ABI it produces is terrible (particularly in evolution).
but it's not a short term deal. funny enough, there's a cohort of bonds that never even made one payment. They are called first payment default bonds. There is a cheekier nickname for them, but it escapes me at the moment.
Cyclical companies are easily burned by investing in infrastructure right at the peak. It happens all the time with little mining companies, and I think DRAM manufacturers are sort of the mining companies of tech.
Am I crazy for wanting this to be in Full ECC RAM modules suitable for composition into many device factors with hope that we'll finally go to reliable memory for all markets as a result?
That way anyone and everyone should be expected to have an ID and depriving someone of that ID or their use of real ID could be made a crime similar to unlawful detainment.
That's not even considering the increase in exposure to radiation outside of the Earth's atmosphere (absorbing materials) and weakened at distance protective EM field.
But for anything where your data is important isn't ECC memory still critical for a NAS in this day and age?
E.G. a Steamdeck is or smartphone are both relegated as toy devices that are not for serious computing.
ECC DDR5 boots insanely fast since the BIOS can quickly verify the tune passes. This is even true when doing your initial adjustment / verification of manufacturer spec.
Wouldn't you like to STOP the insanity of "picking" a plan every year (or more) and also end the billing nightmare by just making it all single payer (the government of the people, for the people)?
There is some interesting proposals on short term allocations, being able to specify that a local allocation will not leak.
Most recently, I've been fighting with the ChaCha20-Poly1305 implementation because someone in their 'wisdom' added a requirement for contiguous memory for the implementation, including extra space for a tag. Both ChaCha20 and Poly1305 are streaming algorithms, but the go authors decide 'you cannot be trusted' - here's a safe one-shot interface for you to use.
Go really needs a complete overhaul of their Standard Library to fix this, but I can't see this ever getting traction due to the focus on not breaking anything.
Go really is a great language, but should include performance / minimise the GC burden as a key design consideration for it's APIs.
JSON's just a nightmare though. The inane legacy of UCS2 / UTF16 got baked into Unicode 8, and UTF16 escapes into JSON.