proomt

Search

Search posts, papers, and topics

All posts

LobstersThom Holwerda2 min readintermediate

An actively maintained and updated Motif fork actually exists

Summary

A community‑maintained fork of the Motif X11 UI toolkit (https://github.com/thentenaar/motif) has released five versions in its first year, incorporating long‑stale upstream fixes and Gentoo patches. The original Motif project on SourceForge has been inactive for over two years, but this fork aims to keep Motif and related X11 components alive, hoping to eventually support a niche desktop environ…

  • Motif’s official upstream is effectively abandoned; the fork is the only actively maintained source.
  • The fork pulls in dormant upstream patches and Gentoo contributions, showing a pragmatic approach to reviving legacy code.
  • Five releases in just over a year indicate a modest but steady development cadence.
  • The effort is community‑driven, targeting a small niche of users who prefer classic X11/ Motif interfaces over modern toolkits.

For engineers maintaining legacy X11 applications or building niche Linux desktops, an up‑to‑date Motif source can reduce the need to vendor old binaries or patch broken builds, and it provides a concrete example of how open‑source stewardship can revive abandoned projects.

4/10

Related reading

  1. Migrating the GitHub Copilot runtime to Rust, using Copilot

    The Copilot agent runtime was rewritten from a 130‑k‑line TypeScript/Node.js codebase into a native Rust library (~830 k lines of Rust) to reduce startup latency, memory use, and improve reliability. The migration was done incrementally (in‑place) across 128 PRs, with AI‑generated code handling most of the work. The new runtime exposes a C ABI for in‑process embedding by all six Copilot SDK langu…

    GitHub Oldgithub.blog65 minHN188
  2. This Week in Rust 666

    This issue of *This Week in Rust* (2026‑08‑26) aggregates community news: official Rust announcements (maintainers‑in‑residence, next‑gen trait solver, supply‑chain attack on arrayref, function‑overloading experiment), a Mozilla JPEG‑XL tooling update, several observations (AI‑assisted C/C++ rewrites, enum‑to‑word speedup, compilation metadata shaving, driver state handling, async vs sync for a r…

    Mozilla Automation Teamthis-week-in-rust.org9 min
  3. Icons! Lots of them! – These Weeks in Firefox: Issue 206

    Firefox 154 adds a Windows‑only UI to change the default browser icon, exposes a new Picture‑in‑Picture WebAPI, and ships a raft of small but concrete improvements across Add‑ons, DevTools, WebExtensions, WebDriver and the Rust‑based login storage component. Most changes are toggles or bug‑fixes (e.g., CSS handling in the Debugger, startup‑performance regression fix, storage.local auto‑reset, and…

    Mozilla Automation Teammozilla.org13 min
  4. webaudio fingerprinting on alibaba

    Firefox made WebAudio output deterministic in v118, collapsing most variance to three CPU‑dependent buckets (x86 without FMA, x86/x64 with FMA, ARM NEON). Telemetry shows 99.24% of users fall into these buckets; a long tail of 23 distinct values affects <0.1% of users. Ongoing bugs aim to merge the remaining buckets. Alibaba’s fingerprint script was extracted (two SHA‑256 hashes) and shown to be…

    Mozilla Automation Teamritter.vg3 min
  5. Reinventing issue tracking: Local-first and Git-native

    A devlog describing how Manganin’s issue tracker stores issues in a dedicated Git repo as plain files, after rejecting earlier approaches that tried to embed issue data in the code tree or Git refs. The author explains the pitfalls of using refs for issue storage, shows the low‑level Git commands needed for that approach, and then outlines the final design: a hidden sister repository where each i…

    Lobstersmanganin.dev6 minHN1lobste.rs27