Yeah, this is what bothers too much. Retina displays for low density content? We could've remained at 800x600.

365Slop all day every day all around

This is awesome. If you made a book or video-course that takes this level of high level explanation and translate it to the technical and then mathematical level, I would buy it in an heartbeat.

This is what I think is missing in most AI (broad sense) learning resources. They focus too much on the math that I miss the intuitive process behind it.

I would really like to see how you implemented DI at the language level. Even at high level document or README file somewhere.

I think Dang is saying that you don't need DI. DI is a way of having some generic code be able to call some specific code when needed. If your whole stack is specific you don't have that problem - instead of the DI call site, you just call the function! Much simpler.

Yes, exactly.

I'm also interested in hearing more about this!

In my own game scripting scheme, I use implicit argument passing, like a cancellation token to async calls, and a rendering context used for immediate mode esque rendering.

This resonate so much to my relationship with Rust. Also with Go. I'm having hard time learning Rust's advacend concepts because of its syntax.

Strangely enough I find Lisp's parentheses much more attractive.

Just answer this question: do you get a compensation for showing me something that I did not click for?

Man I thought some teenage girl was fawning over her crush.

I sure don't want to be led by these little girls.

Sometime I wonder how much overhead all these security features take in terms of performance.

I would really like to see a benchmark with and without security measures.

It's not really possible to make a direct comparison, given that a big chunk of the features are baked into the silicon, or are architecture-level choices.

It’s technically possible, but it would be difficult and likely require breaching an NDA. A bit pedantic, perhaps, but it’s out there.

Apple makes available on a highly controlled basis iPhones which permit the user to disable “virtually all” of the security features. They’re available only to vetted security researchers who apply for one, often under some kind of sponsorship, and they’re designed to obviously announce what they are. For example they are engraved on the sides with “Confidential and Proprietary. Property of Apple”.

They’re loaned, not sold or given, remain Apple’s property, and are provided on a 12-month (optionally renewable) basis. You have to apply and be selected by Apple to receive one, and you have to agree to some (understandable but) onerous requirements laid out in an legal agreement.

I expect that if you were to interrogate these iPhones they would report that the CPU fuse state isn’t “Production” like the models that are sold.

They refer to these iPhones as Security Research Devices, or SRDs.

These devices still have all the security features.

The ones I remember most affecting performance were zeroing allocated memory and the Spectre/Meltdown fix. Also, the first launch of a new app is slow in order to check the signature. Whole disk encryption is pretty fast today, but probably is a bit slower than unencrypted. The original FileVault using disk images was even slower.

> Whole disk encryption is pretty fast today, but probably is a bit slower than unencrypted.

Isn’t whole disk encryption nowadays done in hardware on the storage controller?

It's not whole-disk encryption, it's file-level encryption which is better. (more security guarantees)

Zeroing allocated memory is complicated because it also has performance benefits, since it improves compressed swap.

Yep, I would like to see the success/failure ratio. That would give me a good idea whether this VC funding fantasy is a number game, intentional success or just plain old luck.

The last I checked your body was given to you without any of your effort.