Recordings of the GNUstep online meeting of 2026-08-08 are online
Please see https://mediawiki.gnustep.org/index.php/Monthly_Meetings#Past_Meetings since YouTube Links are not allowed in this subreddit
Please see https://mediawiki.gnustep.org/index.php/Monthly_Meetings#Past_Meetings since YouTube Links are not allowed in this subreddit
The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).
It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)
We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!
Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please
The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).
It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)
We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!
Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please
The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).
It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)
We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!
Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please
BARCELONA, Spain, July 30, 2026 — Today, Openchip is introducing BER10, a sovereign chip built to give Europe’s most critical sectors control over the technology their most sensitive data runs on. It is built on one of the world’s most advanced manufacturing process and delivered in just 2.5 years.
SPEAKER:
Daniel Thompson, RISCstar Solutions
This session was a part of the Software track at the RISC-V Developer Workshops held at RISC-V Summit Europe 2026 in Bologna, Italy.
WORKSHOP DESCRIPTION:
Join Daniel Thompson from RISCstar Solutions for a hands-on workshop exploring the powerful RISC-V Vector (RVV) extensions. You’ll learn the core concepts and design principles behind RVV and we will also compare them to the SIMD approaches of other architectures.
SIMD programming can dramatically accelerate performance across a wide range of compute-intensive tasks, from machine learning and signal processing to cryptography and beyond. The session will then dive into practical techniques for converting optimized C code from other instruction set architectures (ISAs) into RVV-based implementations. We’ll highlight key differences between fixed vector-length architectures on other ISA platforms, and RVV’s more flexible vector-length agnostic (VLA) approach.
Don’t miss this chance to sharpen your skills, push performance limits, and get hands-on with the future of vector computing.
RESOURCES:
https://drive.google.com/drive/u/2/fo...
00:00 Intro: The Kremvax Prank
01:56 Soviet Hardware and the PDP-11 Clones
03:07 Unix Behind the Iron Curtain
04:05 MNOS and DEMOS: Two Rival Projects
06:00 The KOI-8 Encoding Trick
07:21 Perestroika and the Demos Cooperative
09:02 The Real Kremvax
10:16 August 1991: The Coup Begins
11:09 Three Days on Talk.Politics.Soviet
13:28 The Aftermath and the Rise of Linux
14:06 DEMOS Today and the Domain That Outlived the USSR
In 1982, inside the Kurchatov Institute in Moscow, a group of Soviet programmers started building their own version of Unix. It was based on smuggled BSD source code, running on hardware cloned from American PDP-11 machines, at a time when Unix itself was banned behind the Iron Curtain by Western export controls. They called it DEMOS.
This episode traces the full arc of that story: the pirated tapes circulating through Moscow's academic underground, the brilliant KOI-8 encoding trick that made Cyrillic text survive corrupted phone lines, the 1988 state prize awarded for adapting banned American software, and the birth of Relcom, the network that connected the USSR to the internet for the first time in 1990.
It also covers the strange, true story of "kremvax," a 1984 April Fools' hoax that predicted a Soviet node on Usenet six years before one actually existed, and how the real DEMOS team turned that joke into reality. And it ends with August 1991, when Relcom's engineers kept a single phone line to Helsinki open during the coup attempt against Gorbachev, becoming the only source of independent news reaching the outside world.
The open standard that quietly changed everything. In this episode of the Semiconductor Leadership Podcast, host Salah Nasri sits down with Krste Asanovic, Co-founder and Chief Architect of SiFive, to talk about how RISC-V went from a Berkeley lab tool to billions of shipped chips and why the biggest force driving its adoption has nothing to do with technical superiority.
Krste is Professor Emeritus at UC Berkeley, where he co-founded the Berkeley Parallel Computing Laboratory and co-created RISC-V. He received his PhD in computer science from UC Berkeley in 1998, held tenure at MIT, and returned to Berkeley in 2007 before co-founding SiFive in 2015 to commercialize RISC-V IP. He also serves as a board member of RISC-V International.
This conversation goes deep. We cover how RISC-V was never actually a research project, why software is king even in a hardware world, the business model shift that's really driving the x86-to-ARM-to-RISC-V transition in the data center, what China, India, France, and the US DoD all have in common when it comes to sovereign architecture, and why the jump from 64-bit to 128-bit address space may be RISC-V's most important opportunity yet.
Guest: Krste Asanovic, Co-founder and Chief Architect of SiFive
Host: Salah Nasri
And this on a Saturday at 10pm GMT! Sometimes even the whole site doesn't load.
I hope, they'll expand their servers' capabilities next week!
I am in Europe/Germany/Hamburg
On arrival of RVA23 in the datacenter space, Optimization guidance (Oilsm and Ovlt), Rethinking security with CHERI and Microcontroller diversity
GNUstepOfficial 2026 07 11
About the latest C950 core.
Not much comment needed for this one.
The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).
It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)
We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!
Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please
The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).
It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)
We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!
Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please
The monthly GNUstep audio/(video) call takes place every second Saturday of a month at 15:00 GMT to 18:00 GMT. That is 11:00 AM - 2:00 PM EDT (US) or 17:00 to 20:00 CEST (Berlin time).
It's a Jitsi Meeting - Channel: GNUstepOfficial (Sorry, reddit don't let me post jitsi links here)
We usually just talk (who wants it might share video too) and occasionally share screens. Everybody (GNUstep developers and users) is welcome!
Also see https://mediawiki.gnustep.org/index.php/Monthly_Meetings please
What's really happening inside Apple's WWDC AI strategy?
The common story is that Apple fell behind in the model race and had to borrow Google's Gemini tech to catch up, but the reality is more complicated, and it has less to do with who builds the best large language model than who owns the device it runs on.
In this video, I share the inside scoop on why Apple's WWDC bet could decide the first AI trillionaire, and why most of the coverage is watching the wrong layer:
• Why Siri is the face, not the strategy
• How App Intents turns apps into OS-callable actions
• What the Google and Nvidia deals actually signal
• Where the real AI bottleneck is shifting
For operators and builders, the lesson is blunt: AI value is moving toward whoever owns the trusted surface where agents touch real work, so own that surface or plan to pay rent to whoever does.
Chapters:
00:00 The three headlines hiding one bet
02:26 Every AI announcement, mapped
06:04 App Intents and apps the OS can call
09:40 Moving inference from cloud to device
16:18 Owning the default surface for personal AI