Ramen

Many apps ask for permission to use your GPS position and other sensor data, even though they don't need it. Most non-technical people don't understand what that means and will just allow it.

Personally, I still like these defcon sound bites, even though I've heard them plenty of times. They are part of the atmosphere that the stream wants to create.

> Even in a release build, the compiler has not optimized out the stack. As we execute more and more operations, the stack gets deeper and deeper until it inevitably overflows.

I am a technologist. But I am seriously concerned about the ecological consequences of the training and usage of AI. To me, the true laggards are those, who have not understood yet, that climate change requires a prudent use of our resources.

I don't mind people having fun or being productive with AI. But I do mind it when AI is presented as the only way of doing things.

It's hard for me to assess the effort needed here, but I guess that the GrapheneOS implementation will be 99% like the regular Android implementation. Supporting both systems does not seem to be that unrealistic.

> We have to use some kind of attestation mechanism per the eIDAS implementing acts.

What does this attestation need to prove? Is this only about ensuring that private keys are managed by a secure enclave or a TPM?

> we have support for other OSs on our list (like, e.g., GrapheneOS)

I appreciate that, even though I am really not enthusiastic of eIDAS. But time will tell. Thank you.

Once that is established, it is easier for politicians to push for newer laws that add more features to reveal even more information. Politicians can propose any unrealistic law they want. But it is much easier for them, to convince a necessary majority, when there is technical infrastructure already in place. "We are already doing X, why don't we just also do Y?". Or: "Country A has already X, why don't we also do X?"

See also Rich Hickey's remarks on AI: https://www.youtube.com/watch?v=MLDwbhuNvZo

It seems like a small thing, but Clojure's choice to open up for other types of parentheses made seeing the structure of lisp programs much easier. This helped me understand how code is data and how macros are functions that can transform both code and data.

An important design philosophy (which is also hinted at in the trailer) is "simplicity". Clojure is designed to give you the tools to build simple solutions to the problems that you want to solve. It approaches mutability, which is one of the key sources of complexity in programming, with immutable data structures. It's a really clever way to do functional programming where your data is copied a lot but the copies are lightweight.

I don't write Clojure any more these days. I'm mostly doing Rust. But it is true what Eric Raymond said: Lisp has made me a better programmer.

Also: XKCD 224 and 297

Is it time for vanilla.js to shine again with Element.setHTML()?

https://developer.mozilla.org/en-US/docs/Web/API/Element/set...

It's a bit unfortunate that several calls to .setHTML() can't be batched so that several .setHTML() calls get executed together to minimize page redraws.

But that's why you do multiple testing correction

It makes more sense for application developers to think about the unnecessary complexity that they add to software.