I’ve been working on Kafence, a small Rust library to explore strong consistency on top of Kafka Streams. When a service receives a write, if that partition is owned by another instance, the request is proxied to the right service. https://t.co/CCfMNr6lHj
#opensource#rust
El señor @Zerasul y yo estamos montando un discord de Almería para las frikadas y demás, lo interesados ya sabéis.
Todavía está bastante vacío pero poco a poco iremos añadiendo las secciones y todo eso conforme se vaya viendo que hacen falta
https://t.co/RSDyJenGCz
Do you work with @kotlin or @java ? I've been working on a **fast** language server for a while:
https://t.co/4HL9C7htrf
compiler free, orders of magnitude faster than current LSPs for these languages, and integrates nicely with @claude code
As someone who's been shipping LLMs since the GPT-2 days, this lecture on cross-entropy from a Stanford math grad is the closest thing to an ML PhD qualifying exam I've ever seen released publicly for free.
Everyone thinks language models predict the next word. They don't. They compress language. Once you see the math, you can't unsee it.
33 minutes. Bookmark & watch today.
Observations from writing Go again, exacerbated by agents but not unique to them. First, its far too easy to allocate and agents (probably people too) do it too often. For example, to "undo" work on error, its enticing to keep track of the work done but that's a mistake.
If an error case is rare (and they usually are), you should pessimize the error case and optimize the success case. Don't allocate unnecessarily on the happy path if its going to succeed 99+% of the time. Let the error case be slower.
On error, just redo the work but do the undo step instead of the apply step. This doesn't work if the apply step had a ton of side effects but it works more often than you think.
Real world example of that not in Go, but the Zig compiler: when it parses, it doesn't store any file/line/col info, because its a waste of memory when parsing succeeds most of the time. And memory is speed in modern CPUs since cache locality owns everything around us.
If an error happens, Zig just reparses the file from the beginning in a slow path that does collect error information.
That pattern is generally useful.
En Innovamat buscamos 2 Senior Software Engineers para sumarse a los equipos de desarrollo de producto 🚀
Es un momento especialmente interesante por dos motivos 👇
No te pierdas nuestro próximo meetup, de nuevo con la colaboración de @ProtonPrivacy https://t.co/7Gqwb6PcyS Tenemos unas interesantes charlas! Os esperamos! #iot#rustlang#leptos
@politrons@Python Thanks a lot for sharing your examples, snippets, investigations... I always learn from them and get some interesting points about PLs and functional programming toolset
Linux when? Linux now. 🎉🐧
For the last 6 months, our team and our open source community have been working hard to bring Zed to Linux.
As of today, we've released our first, official, stable build of Zed on Linux!
https://t.co/WbptRrpkQw
We collaborated with @mainmatter to bring this new event to Barcelona! We'll have some amazing talks by @MatildaSmeds and @pgleb, and a final panel moderated by @algo_luca . Looking forward to seeing you all in the @AdevintaSpain offices! @rustlang
https://t.co/jnH5VKw32T
Día 30 de mayo: Tudy Gourmelen nos hablará de cómo portó @PyTorch dataloader a Rust y @robertohuertasm nos mostrará cómo crear y desplegar servicios y web apps con #wasm y @fermyontech Spin.
¡Os esperamos en las oficinas de @AdevintaSpain!
https://t.co/PITksEirf8
Looking for some virtual conferences or meet-ups that are interested in hearing a bit more about @arrow_kt and functional programming in #kotlin
Possible topics are functional microservices, FP in Kotlin in general, comparing FP in Kotlin with other functional languages, etc
@antonarhipov It’s funny that Android overtook Kotlin so rapidly, but it came from a hard need in the Android world.
I remember using AutoValue, RetroLamba, etc just to get some modern feeling in Java 7.
Now people seem to associate Kotlin with Android do easily. Lets change that 💪