For those interested in using AES with reduced rounds as a PRNG, it is covered in the paper "Parallel Random Numbers: As Easy as 1, 2, 3" by John Salmon et al.
Thank you, that's what I was interested in. Not sure why I got downvoted, it was a legitimate question as I didn't know what parts were adversely affected.
If you look up a data sheet for any 7483 variant, it is immediately notable: the first lines are something like "4-bit binary full adder" and the description says "…accept two 4-bit binary words" If you skip to the next paragraph, you’ll see they are onto transistors. Ideally the author could show a data sheet, but there may be reasons they can’t.
I found the material that followed to be a clear exposition of the fundamentals – this is as somebody who has tried to learn electronics over the years but nothing ever stuck. This did a better job than anything else at a pace that is about right for me.
But YMMV and I personally relish being in a room full of people who are smarter than me.
> We designed our initial solution as a distributed system using serverless components (for example, AWS Step Functions or AWS Lambda), which was a good choice for building the service quickly.
The message seems more that they outgrew AWS lambda but that lambda was a good choice at first.
> The post literally says that they could hit only 5% of the expected workload with their server less architecture, so IMO it is still quite negative.
Emphasis on "their server less architecture". Sometimes good tools are used poorly.
For example they describe a high throughout workload, and each workload spread through a bunch of lambdas that handled bite size bits of the workflow. Also, they managed the workflow with step functions. Just imagine the number of network calls involved to run a single job, let alone all the work pulling data to/from a data store like S3 into/out of a lambda. I'd guess the bulk of their wall time was IO to setup the computation.
Of course you get far better performance if you get rid of all these interfaces.
Well they do work for Amazon they can't say lambda sux. Monolith is way faster to develop especially the CI/CD part so no if they started with monolith there would be no downside.
I’ve been asking questions about F# after a while of using OCaml. I’ve found GPT-4 to hallucinate syntax that doesn’t exist, such as being able to do open <modulename> in a function. It’s actually something I assumed too, because you can do this in OCaml with "let open <modulename> in", but you cannot do this in F#.
Despite this, it’s still been a lot more helpful than searching, is mostly correct, and is my go-to resource.
Had to admit I came to the same conclusion when I read this part of the readme:
> The NC license permits "use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution is use for a permitted purpose regardless of the source of funding or obligations resulting from the funding."
But on reading the license, personal noncommercial use is fine too. It would have helped me if that info had been in the readme!
https://www.thesalmons.org/john/random123/papers/random123sc...