# C C is a programming language standardized as ISO/IEC 9899. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot build system audit plus next-release plans DevFeed: [Libreboot build system audit plus next-release plans]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [Shell](), [releases](), [C]() Tags: [audit](), [bios](), [build-system](), [c](), [canoeboot](), [coreboot](), [free-software](), [libre](), [libreboot](), [opensource](), [release](), [shell](), [testing](), [uefi]() ### AI overview Libreboot reports that more than 200 changes have been made to its lbmk automated build system since the previous release. The article describes an audit, extensive testing, cleanup, and ongoing work toward a future release. ### Source excerpt Article: Libreboot build system audit plus next-release plans Web link: https://libreboot.org/news/audit.html ## A quick overview of atomics in C DevFeed: [A quick overview of atomics in C]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-09-09T20:41:53Z Content type: tutorial Language: en Sources: [Daniel Lemire]() Topics: [C](), [Concurrency](), [Concurrent Programming](), [Programming]() Tags: [atomics](), [c](), [join](), [ordering](), [posix](), [programming-language](), [systems](), [thread](), [threads]() ### AI overview This tutorial introduces atomics in C, explaining data races on shared non-atomic variables, atomic accesses, instruction reordering, and memory-ordering models including relaxed, release, and acquire semantics. It also discusses C11 threads and platform support limitations. ### Source excerpt If you write in C, by default, you use a single thread. Extra cores do not help until you create more threads. However, if you include the header , you can pass a function to thrd_create, and wait for it with thrd_join. #include #include int worker(void *arg) { printf("hello from thread %d\n", *(int ... Continue reading A quick overview of atomics in C ## A C File Runs a 744B Model, Cloudflare Maps Agentic Traffic, and Karpathy's $48 GPT-2 - The Tokenizer Edition #36 DevFeed: [A C File Runs a 744B Model, Cloudflare Maps Agentic Traffic, and Karpathy's $48 GPT-2 - The Tokenizer Edition #36]() Original publisher: [Read original article]() Author: Sairam Sundaresan Published: 2026-09-09T00:00:40Z Content type: article Language: en Sources: [Gradient Ascent]() Topics: [Artificial Intelligence](), [Machine learning](), [C](), [Cloudflare](), [Command-line interface]() Tags: [agentic](), [ai](), [ai-ml](), [c](), [cloudflare](), [terminal]() ### AI overview A curated weekly roundup of AI resources covering research papers, videos, articles, developer tools, and learning materials. Featured items include a C program that streams a 744-billion-parameter model from disk, Cloudflare's analysis of human and agent web sessions, and a low-cost GPT-2-class model training project. ### Source excerpt This week's most valuable AI resources ## Architecting for 6 Billion Daily Requests: Inside Wix's Media Platform DevFeed: [Architecting for 6 Billion Daily Requests: Inside Wix's Media Platform]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-09-08T08:24:05Z Content type: article Language: en Sources: [Wix Engineering]() Topics: [Caching](), [Go Language](), [Latency](), [Compression](), [data](), [C]() Tags: [c](), [cache](), [caching](), [compression](), [cpu](), [data](), [go](), [latency](), [technical]() ### AI overview Wix describes engineering challenges in its media platform, which processes images, video, and audio at large scale. The supplied text explains how the team used unsafe pointers to reduce Go/C memory-copy overhead for AVIF encoding and a tiered Masters cache to reduce CPU work during image resizing. ### Source excerpt At Wix, "Media" isn't just about storing files. It's about processing streams of information - images, video, and audio - at an immense scale. We host over 300 million websites and serve more than 6 billion media requests every single day. To handle dozens of petabytes of data while keeping costs low and latency minimal, we had to treat media handling as a complex engineering discipline. Below are five specific technical challenges we faced and the architectural solutions we implemented to... ## Blue Proton Initiative: four 17-year-olds are building AI-powered livestock monitoring with Arduino DevFeed: [Blue Proton Initiative: four 17-year-olds are building AI-powered livestock monitoring with Arduino]() Original publisher: [Read original article]() Author: Arduino Team Published: 2026-08-27T13:18:53Z Content type: article Language: en Sources: [Arduino Blog]() Topics: [Arduino](), [Artificial Intelligence](), [Computer vision](), [Neural Network](), [object-detection](), [C](), [datasets]() Tags: [ai](), [ai-powered-livestock-monitoring](), [arduino](), [computer-vision](), [data](), [livestock-monitoring](), [model-training](), [monitoring](), [neural-networks](), [uno-q](), [yolo]() ### AI overview An Arduino Blog article profiles four 17-year-olds in Italy developing an AI-powered livestock monitoring system with the UNO Q. The project uses computer vision, custom-trained neural networks, and diverse image data to identify animals, count them, and detect possible health problems in real time. ### Source excerpt Pietro Maria Piazza, Alessandro Nesci, Davide Santucci, and Matteo Angiolillo are not waiting to finish school before starting to build something real. Based in Forlì, Italy, the four friends behind Blue Proton Initiative strive to develop an AI-powered livestock monitoring system designed to help farmers identify individual animals and detect early signs of health problems [...] The post Blue Proton Initiative: four 17-year-olds are building AI-powered livestock monitoring with Arduino appeared first on Arduino Blog. ## A revised algorithm for converting Gregorian dates to day counts DevFeed: [A revised algorithm for converting Gregorian dates to day counts]() Original publisher: [Read original article]() Published: 2026-08-09T02:29:48Z Content type: article Language: en Sources: [Tony Finch's blog]() Topics: [Algorithm](), [DateTime](), [C](), [Code](), [function](), [Compiler]() Tags: [algorithm](), [c](), [code](), [compiler](), [data-type](), [function](), [range]() ### AI overview The article revisits an algorithm for converting Gregorian dates into Julian Day numbers or related day counts such as rata die. It explains the March-based month pattern, leap-year corrections, integer arithmetic, and limitations caused by overflow in the output data type. ### Source excerpt Many years ago I wrote about how to convert Gregorian dates to Julian Day numbers or similar counts such as rata die as used in Calendrical Calculations. This algorithm is the core of C's mktime() function that converts a broken-down date-time into linear time_t. I recently learned from Ben Joffe that I was missing a few tricks, and my old code wasn't as good as it could have been. Here's a better version (using conventional not C numbering): if m > 2 { m -= 2; } else { m += 10; y -= 1; } y*365 + y/4 - y/100 + y/400 + m*979/32 + d - 336 the main idea Julian years Gregorian correction the month pattern the epoch domains and ranges leap year test length of month the main idea There's a helpful coincidence in the Gregorian calendar. Although the month lengths aren't obviously regular, there's a repeating 5 month pattern that becomes easier to see when you start from March, as illustrated by the table below. This pattern resets at the end of February, midway through its third repeat, coincidentally at the same point that leap days occur. Thus the first line of the code above adjusts the month and year numbers so that January and February are counted at the end of the previous year, and the coincidental alignment occurs at the boundary between the adjusted year numbers. I'll explain the details of the adjustment as I discuss the relevant parts of the second line March 31 days April 30 days May 31 days June 30 days July 31 days August 31 days September 30 days October 31 days November 30 days December 31 days January 31 days February 28 or 29 Julian years The first part of the main formula counts the number of days before the start of year y, in terms of normal years and leap days. y * 365 + y / 4 The adjustment subtracts one from the year in January and February. The effect is that the leap day in year 4 is counted as a day before the start of the adjusted beginning of year 4, i.e. before March, i.e. exactly the right place. I previously combined this part of the express ## Creator of Lua: Scripting, Programming Languages, Predictions | Roberto Ierusalimschy DevFeed: [Creator of Lua: Scripting, Programming Languages, Predictions | Roberto Ierusalimschy]() Original publisher: [Read original article]() Author: Ryan Peterman Published: 2026-08-03T13:05:15Z Content type: article Language: en Sources: [The Developing Dev]() Topics: [Lua](), [Programming](), [Scripting](), [C++](), [C](), [Code]() Tags: [c](), [c-plus-plus](), [lua](), [programming](), [programming-languages](), [python](), [scripting]() ### AI overview A conversation with Lua creator Roberto Ierusalimschy explains how Lua works as an embeddable scripting language alongside C or C++, including how applications can call Lua or Lua can call C. The discussion also covers Lua's use in games such as World of Warcraft and Roblox and recommendations for learning other programming languages. ### Source excerpt When I worked at Instagram, most of the codebase was in Python but occasionally I'd see these bindings into C++. ## How ParparVM Reached Performance Parity with Warmed Java 25 DevFeed: [How ParparVM Reached Performance Parity with Warmed Java 25]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-07-10T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [Java](), [Benchmark](), [Optimization](), [Code generation](), [C](), [Project Valhalla]() Tags: [benchmark](), [c](), [java](), [memory](), [optimization](), [performance](), [project-valhalla]() ### AI overview This article explains how ParparVM, an ahead-of-time virtual machine that compiles Java bytecode to C, improved from 4.21x slower than warmed Java 25 to geometric-mean parity across ten benchmarks. It describes changes involving heap layout, code generation, allocation, and collection, with correctness checked against HotSpot. ### Source excerpt ParparVM went from 4.21x slower than warmed Java 25 to geomean parity, with peak memory below the JVM's. The architecture behind it, in C terms. ## Static linking support DevFeed: [Static linking support]() Original publisher: [Read original article]() Author: Nenad Rakocevic (noreply@blogger.com) Published: 2026-06-29T18:39:33Z Content type: release Language: en Sources: [Red]() Topics: [Red](), [toolchain](), [C](), [parquet](), [MSVC](), [Claude Code](), [codex]() Tags: [agents](), [c](), [claude-code](), [codex](), [compression](), [mod-player](), [msvc](), [soundtracker](), [static-linking](), [toolchain]() ### AI overview The Red toolchain now supports statically linking C libraries, allowing Red/System programs to be distributed as single self-contained executables. The article explains the linker's handling of object formats, symbols, sections, and relocations, and demonstrates the process with the miniz compression library. ### Source excerpt We must free ourselves of the hope that the sea will ever rest. We must learn to sail in high winds. -Aristotle Onassis The coding agents revolution is taking the world by storm and we are right in the middle of it. Like most of you, we have experimented with the agent's amazing (and frustrating) capabilities, pondering the role of Red and our vision in that new world. The conclusion is (un)surprisingly clear, Red is still very relevant and will be even more so as we improve it to better work with agents. In the meantime, here are some treats, starting with expanding our toolchain to support static linking of libraries written in C, allowing you to distribute single executables with all dependencies packed inside. This work has been done with the heavy assistance of frontier models and local harnesses (Claude Code and Codex). You might expect that to be a small addition, but a static linker has to read each platform's object format, pull in just the pieces it needs, fold duplicated sections, resolve system symbols and patch relocations by hand, so there was quite a bit of machinery to put together. The reward is the result everyone wants: a single, self-contained binary, with nothing to install beside it. A simple example Let's compress some data without shipping a compression library next to our program. For something concrete we will use miniz, a small, MIT-licensed library that implements the well-known zlib and deflate APIs. It is distributed as a single `miniz.c` / `miniz.h` pair, which makes it especially convenient to compile and link. The first step is to compile miniz into a static library. There are only two things to keep in mind. Red/System currently produces 32-bit code, so the object has to be 32-bit too; and it helps to switch off a couple of compiler extras (C++ exception tables and stack canaries) that would otherwise make the object reference runtime helpers we do not need. On Windows, with MSVC: cl /c /MT /GS- /EHs-c- /GR- miniz.c lib /out:miniz.l ## Documenting the manual: how curiosity and robotic arms led to a career in open source DevFeed: [Documenting the manual: how curiosity and robotic arms led to a career in open source]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-06-22T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [Documentation](), [Open Source](), [Linux Kernel](), [Linux](), [C](), [Undocumented feature](), [Network](), [Scripting]() Tags: [c](), [communities](), [documentation](), [linux](), [linux-kernel](), [linux-man-pages](), [network](), [open-source](), [scripting](), [sponsorship](), [undocumented-feature](), [work]() ### AI overview This article profiles Alejandro "Alex" Colomar's path from working with robotic arms to maintaining Linux Kernel documentation. It explains how documenting the previously undocumented SO_TIMESTAMPNS feature led to his first man-pages patch and eventually to a career focused on clarity in open source communities. Google sponsors his work on the Linux Kernel man-pages project. ### Source excerpt by Daryl Ducharme, Google Open Source When you think of "innovation" in open source, your mind probably jumps to the latest AI model or a revolutionary new framework. You might not immediately think of manual pages. Even Alejandro "Alex" Colomar, who spends his days maintaining Linux Kernel documentation, jokingly admits that some might find the work "boring" because it focuses on fixing existing issues and documenting new features rather than flashy inventions. But as any developer knows, the most powerful code is only as good as the documentation behind it. At Google, we believe that investing in the success of projects we don't own is a core part of being a good open source citizen. That is why we are proud to sponsor Alejandro's work on the Linux Kernel man-pages project--supporting the critical infrastructure that many of our own systems rely on every day. Documentation is the gift you give to your future self and your whole community. The precision of a robot Alejandro's journey into the world of essential documentation started at university. He was working with robotic arms that used a proprietary scripting language. Wanting more control, he decided to write a C library to communicate with the robots over the network by sniffing packets with Wireshark. It worked, but it was slow--he had to wait seconds between commands to ensure the robot had finished moving. To make the movements smooth, he needed to understand the messages the robot was sending back in real-time. This required high-precision timing. He found SO_TIMESTAMP, which provided microsecond precision, but he noticed a macro called SO_TIMESTAMPNS in the header files that promised nanosecond resolution. The problem? It wasn't documented in the manual page. The first patch After figuring out how to use the undocumented feature by looking at the kernel source code, Alejandro decided to ensure the next person wouldn't have to struggle. He cloned the man-pages repository, wrote a new paragraph based on exis ## Developing a Zephyr IoT app with AI DevFeed: [Developing a Zephyr IoT app with AI]() Original publisher: [Read original article]() Author: John Lee Published: 2026-06-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [AI Agent](), [Embedded Software Dev](), [Internet of things](), [Artificial Intelligence](), [cursor](), [Testing](), [C](), [Git](), [Open Source](), [real-time]() Tags: [agent](), [ai](), [ai-agent](), [blog](), [code](), [coding](), [cursor](), [development](), [drivers](), [embedded](), [esp](), [esp-idf](), [espressif](), [experiment](), [firmware](), [git](), [how-to](), [iot](), [llm](), [m5stack](), [testing](), [workflow](), [zephyr]() ### AI overview This article describes applying an AI-agent workflow to develop a Zephyr-based IoT application on the ESP DualKey kit from M5Stack. It emphasizes specifications, project boundaries, Git discipline, testing, and bench validation while moving the implementation from ESP-IDF and Rust to Zephyr C. ### Source excerpt Still on improving our AI-based, embedded software workflow, this article applies the same AI-agent discipline to Zephyr. Using the same ESP Dualkey kit from M5Stack, specs, integration rules, plan->execute->commit->test, reusable modules, journals, and Git - without redefining the product. ## Parsing JSON at compile time with C++26 static reflection DevFeed: [Parsing JSON at compile time with C++26 static reflection]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-06-14T14:59:44Z Content type: tutorial Language: en Sources: [Daniel Lemire]() Topics: [C++](), [JSON](), [C](), [Compiler](), [configuration](), [gcc]() Tags: [c](), [c-plus-plus](), [compiler](), [configuration](), [gcc](), [json](), [library](), [parsing]() ### AI overview This tutorial demonstrates parsing a fixed JSON configuration file at compile time with C++26 static reflection and GCC 16. It explains embedding the file's bytes in the executable, using simdjson to synthesize a typed C++ object, and detecting malformed JSON during compilation instead of at startup. ### Source excerpt Suppose that you have a configuration file in JSON. Something like this: { "width": 1920, "height": 1080, "fullscreen": true, "title": "My Game", "volume": 0.8 } Normally you ship this file alongside your program, open it at startup, read it, and parse it. That is a lot of work for data that never changes. What if ... Continue reading Parsing JSON at compile time with C++26 static reflection ## TempleOS, mental illness, and open-source spectatorship DevFeed: [TempleOS, mental illness, and open-source spectatorship]() Original publisher: [Read original article]() Author: June 5 Published: 2026-06-05T00:00:00Z Content type: opinion Language: en Sources: [Drew DeVault]() Topics: [Operating system](), [Self-hosted](), [C](), [Compiler]() Tags: [c](), [compiler](), [open-source](), [operating-systems](), [self-hosted]() ### AI overview An opinion article on TempleOS argues that its public prominence stemmed less from its technical achievements than from attention to its creator's mental illness. It describes TempleOS as a self-hosted hobby operating system written in a bespoke C dialect, with an editor, interpreter, compiler, and original games. ### Source excerpt The masterwork of Terry A. Davis is his eclectic operating system, TempleOS, which he worked on until his tragic death in 2018. In terms of technical excellence, TempleOS rates well in some respects and poorly in others. For example, it earns the achievement, coveted in OS dev circles, of being self-hosted.1 TempleOS is written in Terry's own bespoke dialect of C and includes an editor, interpreter, and compiler, as well as a number of original games. In other respects, it compares poorly to many hobby OS projects, some of which have achieved significantly greater levels of technical excellence and sophistication. I would place TempleOS somewhere in, say, the lower middle-class of hobbyist operating systems. Among hobbyist operating systems, TempleOS stands out as one of the most well-known, having attracted considerably more press coverage and a much larger fan-base than any other hobby operating system can boast. The reason TempleOS stands out from the crowd is not due to its modest technical achievements, but because it is clearly the product of severe untreated schizophrenia.2 What makes TempleOS special is that Terry built it to talk to God. Every feature and each technical decision re-enforces his schizophrenic delusions, from its implementation language ("HolyC") to its prophetic "oracle" app. Enthusiasts of TempleOS are drawn to it in part because it affords an opportunity to explore the unique, creative masterwork of a person suffering from mental illness in a way that deeply impacts that work. A curious onlooker will find TempleOS interesting and engaging for the space of perhaps one afternoon before moving on. However, for the less scrupulous fans, turning one's attention to Terry himself never failed to entertain. Terry's public life put his mental illness on display, through frequent outbursts, conspiracy theories, rants and nonsensical discourse, all of which was often laced with slurs, racism, and homophobia, endearing him in particular to the 4chan c ## I Will Not Add Query Strings to Your URLs DevFeed: [I Will Not Add Query Strings to Your URLs]() Original publisher: [Read original article]() Published: 2026-05-09T00:00:00Z Content type: opinion Language: en Sources: [Susam Pal]() Topics: [Web Development](), [CSS](), [HTML](), [Self-hosted](), [C](), [C++](), [JavaScript](), [console](), [file]() Tags: [blog-post](), [c](), [c-plus-plus](), [css](), [developer](), [html](), [query]() ### AI overview The article reflects on Chris Morgan's opposition to query strings in URLs and connects that discussion to the author's experiences learning web development, CSS, HTML, and building the self-hosted Wander Console. ### Source excerpt Last evening, a short blog post appeared in my feed reader that felt as if it spoke directly to me. It is Chris Morgan's excellent post I've banned query strings. Contents Wisdom on the Web Wander on the Web Misfeature Broken URLs Qualms Conclusion Wisdom on the Web Chris is someone whose Internet comments I have been reading for about half a decade now. I first stumbled upon his comments on Hacker News, where he left very detailed feedback on a small collection of boilerplate CSS rules I had shared there. I am by no means a web developer. I have spent most of my professional life doing systems programming in C and C++. However, developing websites and writing small HTML tools has been a long-time hobby for me. I have learnt most of my web development skills as a hobbyist by studying what other people do: first by viewing the source of websites I liked in the early 2000s and later by occasionally getting possessed by the urge to implement a new game or tool and searching MDN Web Docs to learn whatever I needed to make it work. One problem with learning a skill this way is that you sometimes pick up habits and practices that are fashionable but not necessarily optimal or correct. So it was really valuable to me when Chris commented on my collection of boilerplate CSS rules. It helped me improve my CSS a lot. In fact, a few of the lessons from his comment have really stuck with me; I keep them in mind whenever I make a hobby HTML project: always retain underlines in links and retain purple for visited links. I have been following Chris's posts and comments on web-related topics since then. He often posts great feedback on web-related projects. Whenever I come across one, I make sure to read them carefully, even when the project isn't mine. I always end up learning something nice and useful from his comments. Here is one such recent example from the Lobsters story Adding author context to RSS. Wander on the Web A couple of months ago, I created a new project called Wan ## Checking multiplication overflow DevFeed: [Checking multiplication overflow]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-05-06T20:15:20Z Content type: article Language: en Sources: [Daniel Lemire]() Topics: [C](), [C++](), [Compiler](), [Go Language]() Tags: [c](), [c-plus-plus](), [compiler](), [go]() ### AI overview This article derives a condition for detecting multiplication overflow when an unsigned variable is multiplied by a non-zero constant. It concludes that overflow occurs if and only if the variable exceeds the relevant integer-division threshold, while noting that a direct comparison is likely more efficient and that the Go compiler does not perform this conversion. ### Source excerpt Suppose that x is a variable of an unsigned type. In C/C++, it could be of type size_t for example. You have an expression like 6 * x and you want to know whether 6 * x overflows. That is, you want to know if 6 * x exceeds the range of values that can ... Continue reading Checking multiplication overflow ## OpenCL Cooperative Matrix Extensions Are Here DevFeed: [OpenCL Cooperative Matrix Extensions Are Here]() Original publisher: [Read original article]() Author: jphilips (jeff@khronosgroup.org) Published: 2026-04-29T13:00:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [AI Inference](), [GPU](), [C](), [LLVM](), [GitHub]() Tags: [api](), [arm](), [blog-opencl-spirv-machinelearning-llv](), [c](), [gpu](), [intel](), [llvm](), [opencl](), [qualcomm](), [spir](), [vulkan]() ### AI overview The OpenCL Working Group has published a working draft of the cl_khr_cooperative_matrix extension, developed with Arm, Intel, and Qualcomm. The extension brings cooperative matrix operations for ML inference to OpenCL, while a companion OpenCL C extension is also being developed. Community feedback is requested before the standards are finalized. ### Source excerpt The OpenCL Working Group has published a draft extension (cl_khr_cooperative_matrix) that brings cooperative matrix operations--a key technology for accelerating ML inference--to OpenCL, developed in collaboration with Arm, Intel, and Qualcomm. A companion extension to expose these capabilities directly in the OpenCL C language is also in progress, and the community is invited to review both drafts and provide feedback before they are finalized. ## Why do developers count from zero? DevFeed: [Why do developers count from zero?]() Original publisher: [Read original article]() Published: 2026-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Programming](), [C](), [Programming language](), [The Julia Language](), [Lua](), [MATLAB]() Tags: [c](), [developers](), [history](), [lua](), [matlab](), [programming](), [programming-language](), [workshop-learning-programming]() ### AI overview This video explains why zero-based indexing became common. It discusses efficient use of numeric values and the simpler memory-address formula for arrays, while noting that MATLAB, Lua, and Julia use one-based indexing. ### Source excerpt Why do developers count from zero? Short history and reasoning behind this convention. ## A brief history of C/C++ programming languages DevFeed: [A brief history of C/C++ programming languages]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-04-09T14:58:53Z Content type: opinion Language: en Sources: [Daniel Lemire]() Topics: [C](), [C++](), [Programming](), [Java](), [C#](), [Fortran](), [Go Language](), [JavaScript](), [Python]() Tags: [c-c-plus-plus](), [compilation](), [garbage-collection](), [go](), [history](), [languages](), [memory](), [programming](), [programming-languages]() ### AI overview This article presents a brief history of C and C++, explaining how C emerged for low-level systems programming and how C++ added object-oriented, generic, and compile-time metaprogramming features. It then contrasts their portability challenges with Java and discusses JavaScript, Python, C#, and Go. The supplied text ends mid-sentence. ### Source excerpt Initially, we had languages like Fortran (1957), Pascal (1970), and C (1972). Fortran was designed for number crunching and scientific computing. Pascal was restrictive with respect to low-level access (it was deliberately "safe", as meant for teaching structured programming). So C won out as a language that allowed low-level/unsafe programming (pointer arithmetic, direct memory access) ... Continue reading A brief history of C/C++ programming languages ## ESP-IDF v6.0: Default libc Switches from Newlib to PicolibC DevFeed: [ESP-IDF v6.0: Default libc Switches from Newlib to PicolibC]() Original publisher: [Read original article]() Author: John Lee Published: 2026-04-02T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [C](), [Embedded Systems](), [migration](), [Streams](), [Library](), [POSIX]() Tags: [apis](), [architectures](), [blog](), [c](), [compatibility](), [embedded](), [embedded-systems](), [esp-idf](), [firmware](), [libc](), [libraries](), [memory](), [migration](), [newlib](), [performance](), [picolibc](), [posix](), [streams](), [systems](), [toolchains]() ### AI overview ESP-IDF v6.0 changes its default C library from Newlib to PicolibC. The article compares the libraries' memory usage, standard I/O behavior, compatibility, and migration considerations, including measurements on ESP32-C3. ### Source excerpt ESP-IDF v6.0 switches the default C library from Newlib to PicolibC. This article compares both libraries in terms of memory usage, stdio behavior, compatibility, and migration tradeoffs, and explains when keeping Newlib still makes sense. ## Mongoose: Preauth RCE and mTLS Bypass on Millions of Devices DevFeed: [Mongoose: Preauth RCE and mTLS Bypass on Millions of Devices]() Original publisher: [Read original article]() Author: Simone Margaritelli Published: 2026-04-01T22:00:00Z Content type: article Language: en Sources: [evilsocket]() Topics: [Mongoose](), [Vulnerabilities](), [Security](), [Embedded Systems](), [Internet of things](), [C](), [cross-platform](), [HTTP](), [MQTT](), [WebSocket]() Tags: [authentication-bypass](), [buffer-overflow](), [c](), [cesanta](), [cross-platform](), [cve](), [cve-2026-5244](), [cve-2026-5245](), [cve-2026-5246](), [cybersecurity](), [embedded](), [embedded-devices](), [embedded-systems](), [exploit](), [heap-overflow](), [http](), [https](), [industrial-control](), [iot](), [iot-security](), [library](), [mdns](), [mips](), [mongoose](), [mqtt](), [mtls](), [rce](), [responsible-disclosure](), [security](), [stack-overflow](), [tls](), [vulnerability-research]() ### AI overview The article reports three independently exploitable vulnerabilities in Mongoose v7.20, an embedded C networking library used in IoT devices: an mTLS authentication bypass, a preauthentication heap-overflow RCE through client public-key parsing, and a preauthentication RCE through mDNS over UDP. Mongoose v7.21 reportedly includes patches for the issues, which were assigned CVE-2026-5244, CVE-2026-5245, and CVE-2026-5246. ### Source excerpt So, Mongoose. I ## Introducing the SPIFFS component DevFeed: [Introducing the SPIFFS component]() Original publisher: [Read original article]() Author: John Lee Published: 2026-03-23T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Filesystems](), [Streams](), [C](), [POSIX](), [ESP32]() Tags: [article](), [beginner](), [blog](), [c](), [esp-idf](), [filesystem](), [guide](), [posix](), [spiffs](), [storage](), [tutorial]() ### AI overview This practical guide introduces the SPIFFS component bundled with ESP-IDF for storing files on SPI NOR flash. It explains how SPIFFS works with the VFS layer and standard C and POSIX file APIs, describes features such as wear levelling, consistency checks, and format-on-mount, and outlines a basic flow for mounting, writing, renaming, and reading files. It also points to SPIFFSgen and an official working example. ### Source excerpt Learn what the ESP-IDF SPIFFS component is, how it works with the VFS layer and standard C file APIs, and how to use the SPIFFSgen tool to embed files. This article is a practical guide with references to the official example. ## GNU/Hurd developments and fixes in Q1 2026 DevFeed: [GNU/Hurd developments and fixes in Q1 2026]() Original publisher: [Read original article]() Published: 2026-03-02T06:07:00Z Content type: news Language: en Sources: [GNU Hurd]() Topics: [GNU/Hurd](), [Linux](), [kernels](), [Debian](), [bug](), [C](), [Deadlock](), [Documentation](), [Claude](), [qemu]() Tags: [2026](), [bug](), [c](), [claude](), [deadlock](), [debian](), [documentation](), [gnu-hurd](), [hardware](), [linux](), [qemu]() ### AI overview A Q1 2026 GNU/Hurd project update reports debugging and fixes across SMP, threading, filesystem, IPC, networking, and related components, along with wiki documentation and hardware-installation guidance. ### Source excerpt Hello! Welcome to a new qoth. This qoth covers new and interesting GNU/Hurd developments in Q1 of 2026! Details. Brent W. Baccala debugged some x86_64 SMP issues with a Claude AI bot. The bot did not contribute any code. It just found some incorrect code that Damien then fixed. It did get some things wrong, but it was incredibly helpful pointing out several problems. You can read its report here. Joshua Branson tweaked the hurd wiki. The most helpful addition is this page, which documents how to flash a working qemu hurd image directly to an HDD or SSD. This is a really easy way to install the Hurd on real hardware! Buy a supported machine from this page and give it a shot! Consider this another reminder that the Hurd project could use more documentation writers. It's an easy way to contribute. As a fun fact, Joshua wrote this qoth on the Hurd running on a T420 with 12 GB of RAM! Running Debian GNU/Hurd on bare metal these days is largely fairly stable. Emacs, i3, netsurf, and luakit all work just fine and most of the Debian package archive compiles without issue on the Hurd. Etienne Brateau fixed a compilation error. He also provided a simple test program that exposed a rather serious threading bug, which Samuel promptly fixed. This is a good reminder that writing simple C test programs that successfully run on Linux, but fail on the Hurd can have a large impact. Gianluca Cannata worked on our httpfs translator. Diego Nieto Cid added a daemon-wait option for console-client. This can help users with slow machines avoid a broken Hurd console. He also fixed a rumpdisk compilation issue. Mike Kelley fixed a deadlock in SMP enabled GNU Mach kernels. He also fixed a page fault in amd64 SMP kernels. He fixed another deadlock in the alarm () function. He fixed a panic when running large builds without the mach-defpager. He also fixed some of our signal related code. He worked with Samuel to investigate an odd bug. Their detailed investigation uncovered and lead to a fix in ## Error Handling in C, Go, Rust, and Google's Absl DevFeed: [Error Handling in C, Go, Rust, and Google's Absl]() Original publisher: [Read original article]() Author: Nevin Zheng Published: 2026-02-28T00:00:00Z Content type: opinion Language: en Sources: [nevzheng]() Topics: [Error Handling](), [Programming](), [Embedded Systems](), [Microcontroller](), [C](), [Go Language](), [Rust](), [Hardware]() Tags: [c](), [embedded](), [embedded-systems](), [error-handling](), [errors](), [go](), [hardware](), [microcontrollers](), [opinions](), [rust](), [stm32]() ### AI overview An opinionated survey of error handling across C, Go, Rust, and Google's Absl. The article traces error recovery from hardware status registers, interrupts, watchdog timers, and resets to modern language features and libraries, with particular attention to firmware, embedded systems, and microcontrollers. ### Source excerpt Errors, opinions, and the rakes I've stepped on. ## Bit-field layout DevFeed: [Bit-field layout]() Original publisher: [Read original article]() Published: 2026-02-22T08:00:00Z Content type: tutorial Language: en Sources: [MaskRay]() Topics: [implementation](), [C](), [C++](), [Compiler](), [clang](), [gcc](), [LLVM](), [MSVC]() Tags: [c](), [c-plus-plus](), [clang](), [codegen](), [compiler](), [compiler-optimization](), [gcc](), [implementation](), [llvm](), [msvc]() ### AI overview This article explains how C and C++ bit-field layout is implementation-defined and governed primarily by platform ABIs. It distinguishes ABI-defined storage layout from compiler code generation, focusing on the Itanium ABI and describing differences in the Microsoft ABI. ### Source excerpt The C and C++ standards leave nearly every detail to the implementation. C23 §6.7.3.2: An implementation may allocate any addressable storage unit large enough to hold a bit-field. If enough space remains, a bit-field that immediately follows another bit-field in a structure shall be packed into adjacent bits of the same unit. If insufficient space remains, whether a bit-field that does not fit is put into the next unit or overlaps adjacent units is implementation-defined. The order of allocation of bit-fields within a unit (high-order to low-order or low-order to high-order) is implementation-defined. The alignment of the addressable storage unit is unspecified C++ is also terse -- [class.bit]p1: Allocation of bit-fields within a class object is implementation-defined. Alignment of bit-fields is implementation-defined. Bit-fields are packed into some addressable allocation unit. [Next page]()