Congratulations to Charles H. Bennett (@IBMResearch) and Gilles Brassard ( @UMontreal) on receiving the 2025 ACM A.M. Turing Award!
🔗: https://t.co/UQ5C1K1kVT
The Alliance for Open Media announced #AV2 the next-generation open #video#codec at the same time as it's 10th Anniversary!
@videolan who has pushed for open culture on multimedia since 25 years, was happy to be at the party at @IBCShow#OSS#VLC
I think the most underrated announcement of today's @kotlinconf was kotlinx.rpc
This should theoretically let you do react-style server components (or shall I say - Server Composables)
Here's a quick preview of how that looks like
#Kmp#kotlinconf
https://t.co/J3Xnv6RKtq
Our newest episode of #ADBPodcast covers micro optimizations and writing custom tools.
Tune in to hear the latest from our hosts Tor and Romain! → https://t.co/s4I51yNdRo
Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isn’t a “git gud C++ is hard” issue and it damn well isn’t an DEI one.
Our new series ✨Compose tips for Delightful UI✨ is out! With @riggaroo and myself kicking it off 🙃
Episodes are short & to the point, focusing on the practical, easy concepts that can help your app shine and sparkle! ☀️
https://t.co/Dj9AP70iut
Kotlin developers, your expertise is needed! 🚀
Join the Kotlin EAP Champions program and work with @JetBrains to refine Kotlin 2.0. Earn recognition for your contributions and help shape the future of coding. If you’re interested, start here:
➡️ https://t.co/LeilX6fnZg
France has over 40,000 castles (and châteaus) - more than any other country.
These are the most breathtaking 🧵
1. Château de Pierrefonds, Oise (14th century)
💡 IntelliJ IDEA Tip: you can enable language specific syntax highlighting on any String by annotating it with @Language("<lang>") or commenting with //language=<lang>.
Especially useful when used with Java 15+ Text Blocks
📢 Kotlin 2.0.0-Beta1 is out!
ℹ️ This release focuses on stabilizing the new K2 compiler, which will soon be enabled by default in Kotlin 2.0.
Give K2 a try and please report any potential issues: https://t.co/H6WaTenZag
Debian fixes for high severity curl vulnerability CVE-2023-38545 (and low severity CVE-2023-38546) are available!
You have likely seem the news around an upcoming curl vulnerability, which was rated as high severity by the curl's author itself.
Kotlin + Documentation = 💜!
Discover how the @onwriterside team is using Kotlin to create DSL for docs. Leveraging Kotlin’s strengths, IDE support, and the inherent extensibility of the DSL, they’ve made documentation a dynamic, integrated part of the development process.