Vladimir Dementyev's wroclove.rb 2018 talk surveying Ruby 'cables' (tools for building real-time web applications). Reviews Action Cable's architecture (server, broadcaster, channels framework, clients) and its good parts (bundled with Rails, Rack-compatible, single Ruby process, easy channels DSL, capable JS client). Covers bad parts: WebSocket-only (no fallbacks), high memory use due to MRI limits and the GIL, poor broadcast latency under load (rocket's benchmark shows thousands-of-seconds latency with thousands of clients, even on a 16-core c4.4xlarge). Tells the real-life Calico/equestrian-shows platform story where switching from Action Cable (21 2×-Heroku dynos, hitting memory-quota-exceeded) to AnyCable cut resource use ~10x. Introduces AnyCable: replace the MRI WebSocket server with a Go or Erlang server that proxies Action Cable protocol to Rails over gRPC (HTTP/2 + protobuf) with Redis for broadcasting. Highlights zero-disconnect deployment and Prometheus metrics. Q&A explains why both Go and Erlang implementations exist (Go prototype due to no mature Erlang gRPC lib). Closes with LiteCable (Rails-free Action Cable-compatible channels framework, used with Hanami for IoT) and ongoing integration with Plezi on top of the Iodine web server.