Stenobird

Episode

Hopp with Costa Alexoglou and Iason Paraskevopoulos

Podcast
Rustacean Station
Published
Feb 27, 2026
Duration seconds
2563
Processing state
processed
Canonical source
https://rustacean-station.org/episode/hopp/
Audio
https://dts.podtrac.com/redirect.mp3/audio.rustacean-station.org/file/rustacean-station/2026-02-27-hopp.mp3
JSON
/v1/public/podcasts/rustacean-station/episodes/hopp-with-costa-alexoglou-and-iason-paraskevopoulos
Markdown
/podcast/rustacean-station/hopp-with-costa-alexoglou-and-iason-paraskevopoulos.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/rustacean-station/episodes/hopp-with-costa-alexoglou-and-iason-paraskevopoulos/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/rustacean-station/hopp-with-costa-alexoglou-and-iason-paraskevopoulos.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

The creators of Hopp discuss building a low-latency remote pair programming tool designed to eliminate the productivity friction of standard video conferencing. They detail the technical transition from using WebKit to a custom Rust-based WebRTC implementation to achieve high-performance screen sharing.

Topics

  • Rust
  • Tauri
  • WebRTC
  • Remote Pair Programming
  • Low Latency Streaming
  • Software Architecture
  • Iced UI
  • WGPU
  • Open Source Development

Highlights

  • Main idea: Hopp addresses the high latency and poor quality of generic tools like Google Meet for developer-specific workflows
  • Technical pivot: Moving from WebKit to a custom Rust WebRTC implementation to bypass browser limitations and access raw stream buffers
  • Architecture: Utilizing Tauri for the UI layer while offloading heavy operations like screen capture and input simulation to a dedicated Rust core
  • Failure mode: Relying on standard web engines leads to inconsistent CSS rendering and design compromises across different operating systems
  • Practical takeaway: Using the Iced library and WGPU allows for high-performance, Rust-native UI rendering for the video stream components

Chapters

  1. 1:00 The Problem with Generic Tools: The friction caused by high latency and lack of remote control in standard video conferencing tools.
  2. 7:10 Why Tauri?: Evaluating cross-platform frameworks and the decision to use Tauri for the application shell.
  3. 10:20 Handling High Latency: Managing edge cases like low-bandwidth connections and simulating mouse/keyboard events.
  4. 20:00 Bypassing Browser Limitations: The technical necessity of moving away from WebKit to a custom Rust WebRTC implementation.
  5. 23:20 Accessing Raw Stream Buffers: The advantages of a Rust-native approach for processing incoming video data.
  6. 36:25 Linux Distribution Challenges: Navigating the fragmentation of the Linux ecosystem for application distribution.
  7. 39:35 Future Roadmap and Enterprise: Plans for SSO integration and migrating the UI to Iced and WGPU.