Not reading out loud, but I've caught myself a few times on reading and not processing that, because I was thinking about something else. Like I still did the reading, but straight to /dev/null of my brain
I've never claimed that anything about telegram's encryption is "heavy", because I don't even know what they use, I just said what "heavy" usually means
> In this context
In this context it's marketing bs for people that only seen action movies where hackers quickly cracked encryption. I'm sure whatever telegram uses is not that ridiculously easy to crack
Heavily means the key is large so it takes longer to crack, but also longer to encrypt/decrypt, so the service is more costly to run and slower. At least I've seen it used that way
It reads like a rambling of a mad scientist, but I think simply adding pictures would make this feel absolutely normal (in the crowd of other blogs featured on hn)
I put aluminium foil over a bowl of pizza dough, as it grew the top touched the foil and in a few spots tiny holes appeared in the foil. I wonder if it was carbonic acid or what
> Wouldn't it be easier to add old hardware support to LLVM/GCC instead?
No, in fact it's much, much harded. You have no idea of the scope. I have no idea of the scope. Nobody does. There are obscure machines we've never heard about and there are C compilers for them. Targeting and supporting them from modern toolchains is a fool's errand.
> Imagine a film-noir movie script, where AI Detective's "I know Mickey couldn't have done it because" monologue is hidden, versus their terse dialogue "Too early to say."
That's an idea. Bladerunner+noir like film, AIs hunt somebody on the run, an old human detective tries to catch them first (to save them or to kill them first, whatever's your propaganda). We're shown AIs constantly rambling scenarios and bruteforcing leads. Our old detective guy on the other hand barely says anything, spends most time drinking, smoking and talking to people, but somehow stays ahead.
Kinda, more output tokens usually correlates with better benchmark scores. Ideally LLMs would keep that in their thinking section, then draft a response (what they write currently), then output something short. It'd consume even more tokens, but we wouldn't see that text
> but because in 2015, using Go (often) connoted a certain approach, a certain type of engineering, a certain constellation of values
So called "The vibe". And the vibe emanating from Rust is sometimes unbearable. Like claiming the main feature of the project is that it's written in Rust.