Urgent.News

What's breaking now, across thousands of outlets.

Tech

Discord is rebuilding its desktop app in Rust to fix its memory problem

Microsoft is finally doing something about Windows 11's abysmal performance on lower-end systems, and third-party software developers are following suit. Discord's CTO has recently confirmed that the popular messaging platform is soon getting a brand-new desktop client. Unlike past web-based versions, it should deliver much better performance thanks to the... Read Entire Article

Discord is rebuilding its desktop app in Rust to fix its memory problem

Discord, a popular messaging platform, is in the process of rebuilding its desktop client in Rust to address its memory issues. The company's CTO, Stanislav Vishnevskiy, confirmed the move, stating that the new client, codenamed "Discord Phoenix," will deliver better performance. Vishnevskiy explained that the company began using Rust in 2018 for various parts of its infrastructure and products.

However, converting the entire app to Rust will take time. Electron-based apps, like Discord's current client, are known to be memory-intensive, requiring their own copies of Chromium to function. This results in higher memory usage compared to native alternatives like C or Rust. The new Rust-based desktop app will replace the current Electron-based app and React Native mobile app, while retaining Discord's native UI on mobile devices.

A beta version of the new desktop client is expected to be released soon, although no specific timeline has been provided. Discord's focus on improving efficiency is timely, considering the increasing demand for chips and RAM in data centers and the growing scarcity of DDR4 and DDR5 PC DRAM products.

Written by urgent.news from TechSpot's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at techspot.com →

More in Tech

Why Node.js HTTP backpressure must count bytes, not string length

In Node.js, string.length counts UTF-16 code units, not bytes . When Node's HTTP OutgoingMessage buffered a write, it added data.length to the counters that drive backpressure, so multi-byte response…

  • Node.js string.length counts UTF-16 code units, not bytes
  • HTTP OutgoingMessage buffers data by adding data.length to backpressure counters
  • Fix counts bytes instead of code units to accurately detect backpressure

How to build a secure MCP server with OAuth 2.1: lessons from a CRM connector

To let an AI assistant work with real business data over the Model Context Protocol (MCP) , the server needs two things done properly: authentication (OAuth 2.1 with PKCE, so the AI client never sees…

  • Implement OAuth 2.1 with PKCE for secure MCP server authentication
  • Treat access token as user session for row-level security
  • Implement read-only tools and clear error messages for AI models

Recharge Retries Run. The Question Is What Happens Between Them.

Stores running subscriptions on Recharge inherit a working retry engine, and that inheritance creates a particular blind spot: because attempts are visibly happening, the team assumes recovery is…

  • Subscribers often miss initial receipt correction for failed subscription
  • No information when subscription cancels after retry sequence ends
  • Recharge platforms benefit from tailored retry strategies and audits

More from Thursday 5 November →