systemd Merges Rust Infrastructure, Limited to New Leaf Components Without Cargo

·13 views

systemd, the Linux startup and service manager, has merged Rust support into its Git repository through PR #44324, which adds about 5,100 lines across 54 files. The rules agreed by maintainers restrict Rust to new leaf components, with no plans to port existing C code. The build continues to use Meson rather than Cargo, no external crates are included, and code runs under no_std with only C linkage permitted. The design also avoids Rust's standard allocator in favor of a custom one that returns errors instead of aborting, and it adds type-based erasure of sensitive data. A first practical Rust program is still awaiting merge, while distributions such as Arch and openSUSE must decide whether to add build dependencies or disable Rust support.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Python 3.10 and Node 20 reach end of life: how to find pinned versions

Python 3.10 reaches end of life on October 31, 2026, and Node 20 already reached it on April 30, 2026. Ending support does not stop software from running, but security patches for new vulnerabilities will no longer be released. Because these runtime versions are often pinned in several files such as Dockerfiles, version files, and serverless configs, the article recommends auditing the whole codebase with a search. The author suggests choosing a runtime version with years of support remaining and notes Node 22 is supported until April 30, 2027. The piece also promotes a daily automated check that flags pinned versions 180 days before their end-of-life dates, while leaving the decision to upgrade to developers.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why lidar range falls short of datasheet figures: four conditions that matter

A lidar rated at 40 m may reach only 9 m outdoors, not because the device is faulty but because datasheet ranges are measured under unstated conditions. The article identifies four factors that usually explain the gap: the target's reflectance, which is often far below the 90 percent benchmark most specs assume; ambient background light, which can exceed a module's stated tolerance in direct sunlight; atmospheric visibility, which degrades returns in fog or rain; and integration time and update rate, which affect how long a sensor can collect signal. The author argues that range figures are only meaningful when paired with these conditions, and recommends testing with repeated measurements at several distances while recording the failure boundary.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Choosing Embedding Models for CRM-Linked Chatbot Retrieval

A DEV Community article argues that the best embedding model for a chatbot's RAG semantic search is the one that performs best on a labeled retrieval set while keeping the fields needed for CRM actions. Using an edtech sales-call assistant as the example, the author recommends measuring whether the right CRM policy, objection playbook, and follow-up rule are retrieved before weighing model size or cost. The proposed workflow defines a CRM action schema, builds test cases from real call summaries, compares candidate embedders under identical chunking and indexing, and validates generated actions separately. The piece includes a Python evaluator measuring recall at k and mean reciprocal rank, and suggests starting with 60 to 100 labeled queries and adding cases for every observed miss.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Price and Sell an AI Agent or n8n Workflow You Built

A practical guide for creators explains how to turn a working automation, such as an n8n workflow or AI chatbot, into a sellable product. It advises defining exactly what the buyer receives, whether a template, setup guide, hosted access, source code, or done-for-you installation, and treating each format as a distinct offering. Sellers are urged to disclose platform requirements, paid API costs, account needs, setup time, and limitations to reduce refunds. Pricing should weigh the value to the buyer, comparable products on marketplaces, and the seller's ongoing support burden. The guide suggests one-time purchases for templates and subscriptions for hosted or continuously updated tools.

0 comments Read more at DEV Community