Using this sampling-based approach you get correct covariance modeling for free. You have to only sample leaf values that are used in multiple places once per evaluation, but it looks like they do just that: https://github.com/mattt/Uncertain/blob/962d4cc802a2b179685d...
Memory efficiency just for one. For most programs, and especially in the embedded space, 64b systems carry around (and process) a lot more zeros than 32b systems do. You can still do 64b math when you need it, but you don’t have to pay for it when you don’t.
Given that software is always too big, this can often be a product-making distinction.
32 bit is still very common for smaller CPUs that aren't in the "application processor" class.
They are cheaper because they use less area, and they're also more memory efficient because pointers are all half as big. On these CPUs you don't have 4GB of RAM so you don't need a big address space.
It's good enough for the majority of use cases and systems; even an eight bit MCU is sufficient for many cases. If you design a product, saving power and cost makes the difference.
As far as I know, webassembly only supports a 32 bit address space on all platforms at the moment. There’s a memory64 proposal, but it doesn’t look to be widely adopted yet.
That switch-case gets optimized and compiled down to logic gates by the synthesis tools. It'll be a different set of gates from the original netlist (which might also have used a more regular grid structure for this), but it won't be _that_ different. It's not somehow running this switch-case in software emulation on a different CPU instantiated in this design.
For all emails sent to/from any Seattle owned email address in 2017, please provide the following information:
1. From address
2. To address
3. bcc addresses
4. cc addresses
5. Time
6. Date
Is this really a reasonable request that the government is expected to answer? Doesn't this expose a bunch of private information about government employees and the people they interact with? I understand this post (and apparently the law) takes this as completely normal thing, but it seems really weird to me.
Some examples:
* exact times people are getting in/out the office (eg. the time in the morning when a person first answers an email from their boss)
* full information about holidays taken by all employees (eg. days/weeks during which no emails are sent)
* friendships or relationships (eg. any communication between employees that doesn't follow from the hierarchy or from team delineations)
* information from criminal investigations (eg. an investigator sending an email to the parking fine department probably means one of the cases they're working on is related to parking fines)
This all seems a huge privacy leak? Should this stuff even be called "metadata" if so much can be derived from it?
