2,801 karma · joined February 2, 2019
For decades, the academia mafia, through impenetrable jargon and intimidating equations, have successfully prevented the masses from adopting this beautiful paradigm of computation. That changes now. Join us to learn why monads really are monoids in the category of endofunctors (oh my! sorry about that).
[0] Insert your favourite natural language
Since this is a Git repo, I'd go with `git ls-files '.rs'`.
What I'd really, really prefer is to be able to program the device with the same ease as developing a local Linux application. If I need a UI, I'd rather that be a web front end, and not something that needs GBs and GBs of special IDEs and other bloatware. That way, we don't need specialised "apps" for each and every thing: any service that already has website, should work as it is. Just point a browser at it.
And how do I tweak an "app's" UI if I must, rather than beholden to it? That's right: web extensions.
Until FF pulls a dick move, at which point we sell all our possessions and go live in the mountains.
Economists knew this phenomenon well before, though: https://en.wikipedia.org/wiki/Veblen_good.
Now, this Apple ad appears to be boasting as if battery that lasts single day is a generous offering. Perhaps it's adjusted for a heavy user. Still, I don't get the impression that we aren't getting actual improvements on battery life.
I've been listening to the podcast for years. I don't think the format counts as a 'discussion among experts'. It's more like Melvin asks prepared questions individually to each expert--a hub and spoke model. The experts rarely talk to or debate each other, although they often agree which each other. Melvin largely controls the narrative and direction, which I think works better. Guests do get to free-wheel at the end of the podcast, however.
#vibecoding
My rough understanding is that it's the user-space emulation part of a virtualization solution. I.e., when the kernel traps the virtualized process, saying 'nope, you can't do that here', the control falls back to user space handler in QEMU saying, 'hey, the kernel said I can't do that there; can you sort this out?'. And this back-and-forth games keeps happening during the lifetime of the virtualized process.
As Dr. Sheldon Cooper said, "if you don't tell them, how would they learn?".