# Scripting Published articles for Scripting. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Java Weekly, Issue 661 DevFeed: [Java Weekly, Issue 661]() Original publisher: [Read original article]() Author: baeldung Published: 2026-08-26T17:15:42Z Content type: article Language: en Sources: [Baeldung]() Topics: [IntelliJ IDEA](), [Spring Boot 4](), [Orchestration](), [Quarkus](), [elasticsearch](), [JSON](), [Compiler](), [Scripting](), [GUI](), [Cryptography](), [Security]() Tags: [boot](), [cryptography](), [gui](), [intellij](), [intellij-idea](), [java](), [json](), [metrics](), [netflix](), [no-ads](), [no-after-post](), [no-before-post](), [no-optins](), [orchestration](), [post](), [release](), [scripting](), [security](), [weekly-review](), [weekly-review-no-ads-no-after-post-no-before-post-no-optins]() ### AI overview Java Weekly, Issue 661 is a roundup covering IntelliJ IDEA Conf, the JDK 27 release candidate, early JDK 28 developments, Spring and Java updates, technical articles, webinars, and recent framework and library releases. It also highlights Netflix Conductor's evolution as a workflow orchestration engine. ### Source excerpt IntelliJ IDEA Conf is back, JDK 27 got its first RC and JDK 28 is already looking solid The post Java Weekly, Issue 661 first appeared on Baeldung. ## ESP32 Bit Pirate: a multi-protocol workbench built on the ESP32-S3 DevFeed: [ESP32 Bit Pirate: a multi-protocol workbench built on the ESP32-S3]() Original publisher: [Read original article]() Author: John Lee Published: 2026-08-20T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32-S3](), [Embedded Software Dev](), [Hardware](), [Command-line interface](), [ESP32-C5](), [Scripting](), [Open Source](), [Python]() Tags: [2](), [ble](), [blog](), [bridging](), [cli](), [community-contribution](), [debugging](), [development-board](), [esp32](), [esp32-c5](), [esp32-s3](), [firmware](), [hardware](), [open-hardware](), [open-source](), [python](), [scripting](), [tooling](), [usb](), [wi-fi]() ### AI overview ESP32 Bit Pirate turns an ESP32-S3 into a scriptable multi-protocol workbench. The article describes its firmware, more than twenty wired and wireless modes, serial and web-based interfaces, Python scripting, and companion open-hardware projects including an ESP32-C5 radio adapter and a carrier dock. ### Source excerpt ESP32 Bit Pirate turns an ESP32-S3 into a scriptable multi-protocol workbench with more than twenty modes, a web and serial CLI, and dump and sniff tooling. This article walks through the firmware and the two open-hardware companions that extend it: a carrier dock with selectable 1.8 V, 3.3 V and 5 V level translation, and an ESP32-C5 adapter that adds a dual-band radio. ## 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++. ## Three Gradle Talks from KotlinConf 2026 (and What to Steal from Each) DevFeed: [Three Gradle Talks from KotlinConf 2026 (and What to Steal from Each)]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2026-07-28T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Kotlin](), [Groovy](), [ide](), [Scripting](), [Refactoring]() Tags: [2026](), [best-practices](), [build](), [build-tool](), [conference](), [developer](), [dsl](), [event](), [gradle](), [groovy](), [ide](), [kotlin](), [kotlinconf](), [refactoring](), [script](), [scripting](), [talk](), [talks]() ### AI overview The article reviews three Gradle talks from KotlinConf 2026. It explains the progression from Groovy build scripts to the Kotlin DSL and early Declarative Gradle, emphasizing the problems each approach addresses. It also introduces Gradle best practices for organizing and optimizing builds. ### Source excerpt Every year I tell myself I'll watch every conference talk I missed. Every year I get through maybe three before a build breaks and I get pulled back into real life. KotlinConf is the one event where I actually follow through, partly because the talks are short and dense, and partly because a good chunk of my coworkers and friends are on stage. This year in Munich, three of them talked about Gradle: Paul Merlin on the history of our DSLs, Stefan Wolf on best practices, and Marcin Mycek on Declarative Gradle for Kotlin. I watched all three so you can decide which ones are worth your fifteen minutes. A Tale of the Gradle DSLs -- Paul Merlin Paul has been inside Gradle's DSL machinery for years, which makes him exactly the right person to tell this story and exactly the wrong person to pretend the early days were clean. The talk traces how build logic went from Groovy, to the Kotlin DSL, to Declarative Gradle. The useful part isn't the timeline. It's that each of those was solving a real problem the previous one couldn't. Groovy gave us a flexible, dynamic scripting language, which was great right up until you wanted your IDE to tell you what was valid. The Kotlin DSL brought static typing, real autocompletion, and refactoring that doesn't rely on hope. That's why the Kotlin DSL is now the default for new Gradle builds. Declarative Gradle is the next swing: describe what your build is rather than script how it runs. The honest through-line is that none of these fully replaces the last one. Kotlin DSL is where most people should be today. Groovy still runs an enormous amount of the world's build logic and isn't going anywhere fast. Declarative Gradle is early but points at where things are headed. Real talk: if your build scripts are still Groovy and still working, you don't have to panic-migrate this weekend. But if you're starting something new, reach for the Kotlin DSL and let the IDE carry some of the weight. 📺 Watch the talk 10 Gradle Best Practices Every Kotlin Deve ## Inspect feature flag history with Vercel CLI DevFeed: [Inspect feature flag history with Vercel CLI]() Original publisher: [Read original article]() Author: Chris Widmaier Published: 2026-07-23T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Command-line interface](), [Vercel](), [Scripting]() Tags: [cli](), [documentation](), [feature](), [json](), [scripting](), [update](), [vercel]() ### AI overview Vercel CLI now supports inspecting Vercel Flags version history, including revision authors, messages, timestamps, changed environments, filtering, pagination, JSON output, and semantic diffs between revisions. ### Source excerpt Vercel Flags version history can now be inspected from the Vercel CLI with the new vercel flags versions command. Run vercel flags versions to print the full revision history for a flag, with each revision's author, message, timestamp, and changed environments. Filter to a specific environment with --environment, paginate with --limit and --cursor, or add --json for scripting. To compare a revision against the one before it, run vercel flags versions diff --revision . The diff is semantic, surfacing field-level changes to targeting rules, rollout percentages, and conditions. Additions, removals, and modifications appear as colored +, -, and ~. Update to the latest version of the Vercel CLI and learn more in the Vercel Flags CLI documentation to get started. Read more ## Debug your Postgres from the terminal: a tour of \`neon inspect db\` DevFeed: [Debug your Postgres from the terminal: a tour of \`neon inspect db\`]() Original publisher: [Read original article]() Author: Savannah Longoria Published: 2026-07-22T18:00:00Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [Database](), [telemetry](), [SDKs]() Tags: [cli](), [debug](), [diagnostics](), [json](), [observability](), [performance](), [postgres](), [product](), [scripting](), [sql](), [statistics](), [tooling]() ### AI overview Neon introduces `neon inspect db`, a Neon CLI command suite for read-only Postgres diagnostics. Its subcommands run bounded, versioned queries against Postgres statistics and catalog views, returning tables or JSON/YAML without requiring users to assemble connection strings or write catalog queries. ### Source excerpt The Neon CLI now ships `neon inspect db`: read-only, high-signal Postgres diagnostics that answer "what is slow?" without leaving the terminal or writing a single catalog query. Each subcommand runs one known-good query against Postgres' own statistics and catalog views and prints a clean table (or JSON/YAML for scripting). ## Worth Reading: Scripting Good Practices in Python DevFeed: [Worth Reading: Scripting Good Practices in Python]() Original publisher: [Read original article]() Published: 2026-07-08T05:28:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Python](), [Scripting](), [Artificial Intelligence]() Tags: [ai](), [python](), [scripting](), [worth-reading]() ### AI overview A recommendation to read Brett Cannon's guidance on good scripting practices in Python, especially when building a simple Python project. ### Source excerpt Just in case you decide to build a simple Python project over the summer: read scripting good practices in Python by Brett Cannon and tell your AI friend to adhere to them ;) ## We put a Redis server inside our runtime DevFeed: [We put a Redis server inside our runtime]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-06-25T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Redis](), [Rust](), [Development](), [Cache]() Tags: [cache](), [development](), [protocol](), [redis](), [rust](), [scripting](), [streams](), [transactions]() ### AI overview Encore describes how its runtime provides an in-memory Redis server for local development and tests, aiming to keep behavior consistent with Redis in production. The Rust runtime embeds a port of miniredis as a library that supports commonly used Redis data types, streams, pub/sub, transactions, Lua scripting, TCP, and the Redis wire protocol. ### Source excerpt How we run an in-memory Redis inside the runtime for local development and tests, and how we keep it behaving the same as the Redis you run in production. ## 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 ## Managing Multiple Lua Scripts with Ceph Object Storage DevFeed: [Managing Multiple Lua Scripts with Ceph Object Storage]() Original publisher: [Read original article]() Author: Kirby Chin Published: 2026-06-10T00:00:00Z Content type: article Language: en Sources: [Ceph Blog]() Topics: [Lua](), [Script](), [Scripting](), [Security](), [Command-line interface](), [cloud-infrastructure](), [ransomware]() Tags: [availability](), [blog](), [blog-post](), [ceph](), [cli](), [data](), [developer](), [en-article](), [en-blog-post](), [examples](), [feature](), [go](), [lua](), [management](), [new-feature](), [object-storage](), [operations](), [rados](), [ransomware](), [rgw](), [s3](), [scripting](), [security](), [storage]() ### AI overview This article introduces a Ceph RADOS Gateway feature for managing multiple Lua scripts within the same request context and tenant. It demonstrates scripts for enforcing bucket object locks to mitigate ransomware risks and for optimizing storage through object auto-tiering. ### Source excerpt Since the Pacific release, Lua scripting in Ceph's RADOS Gateway (RGW) has provided users the ability to interpolate a single script to upload operations per request context and tenant. This way of working might be completely fine for a storage deployment with limited scripting customizations. However, script management becomes increasingly difficult as more than one team wants to get involved in managing the Lua script within the same context and tenant. For this reason, we've released a new feature in RGW allowing you to manage more than one Lua script at a time. In this blog, we'll go over a couple of examples to walk you through how this feature can help your team to reduce runtime errors and lower developer friction when managing Lua scripts in RGW. To begin, we will create a script to enforce a bucket security control and then add another script to demonstrate the new feature. Script 1: Bucket security ¶ Let's suppose we are part of a security team and want to mitigate the risk of ransomware threats happening on our storage platform. One possible way to achieve this is to implement a Write Once, Read Many (WORM) strategy to add an object lock onto any newly created bucket. By using an object lock, we can add a constraint to write objects to disk only once, ensuring that an infected client cannot delete or override objects at a later time. To set our WORM strategy, we can create a Lua script in the prerequest context that aborts when a create_bucket operation is made without the write-once (object lock) requirement. objectlock.lua -- enforcing object lock on bucket creation if Request.RGWOp == "create_bucket" and Request.HTTP.Metadata["x-amz-bucket-object-lock-enabled"] ~= "true" then RGWDebugLog("object lock is missing on bucket: " .. Request.Bucket.Name) Request.Response.Message = "Bucket must have object lock enabled" return RGW_ABORT_REQUEST end You can create a new objectlock.lua file with the contents above and run the CLI commands below to upload the scr ## Introducing Trusted Remote Execution: Policy-Enforced Scripts for AI Agents and Humans DevFeed: [Introducing Trusted Remote Execution: Policy-Enforced Scripts for AI Agents and Humans]() Original publisher: [Read original article]() Author: Nick MacDonald Published: 2026-05-04T15:34:36Z Content type: release Language: en Sources: [AWS Open Source Blog]() Topics: [AI Bots](), [SDKs]() Tags: [agent](), [agentic](), [agents](), [ai](), [ai-agents](), [case-study](), [code](), [logs](), [model](), [open](), [open-source](), [operations](), [policy](), [production](), [remote](), [review](), [safety](), [sandboxes](), [scripting](), [software]() ### AI overview Trusted Remote Execution (Rex) is an open-source scripting runtime that authorizes each host operation against a Cedar policy. It is designed to give service owners runtime control over scripts generated by AI agents or used by humans. ### Source excerpt Today, we're announcing Trusted Remote Execution (Rex, for short) -- an open source scripting runtime where every system operation is authorized by policy. Scripts are written in Rhai, a lightweight language with no built-in system access. The only way to reach the host is through operations Rex explicitly provides, which are authorized against a Cedar [...] ## Jenkins Series DevFeed: [Jenkins Series]() Original publisher: [Read original article]() Author: baeldung Published: 2026-04-03T12:36:55Z Content type: tutorial Language: en Sources: [Baeldung - Ops]() Topics: [Jenkins](), [Automation](), [CI/CD](), [Groovy](), [Scripting](), [Server](), [Open Source]() Tags: [administration](), [automation](), [ci-cd](), [docker](), [jenkins](), [jenkins-series](), [open-source](), [scripting](), [series](), [server]() ### AI overview A tutorial series covering Jenkins pipelines, job management, administration, Groovy scripting, parameterized and parallel builds, and server maintenance across the CI/CD lifecycle. ### Source excerpt This tutorial provides an overview of Jenkins pipelines, job management, and administration. Related Stories Git Series Troubleshoot Docker Daemon Connection Issues in Jenkins Troubleshooting Jenkins 403 No Valid Crumb in Request Error ## Playground and java.time Support in Codename One DevFeed: [Playground and java.time Support in Codename One]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-03-27T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Scripting](), [ui](), [Java](), [API]() Tags: [api](), [java](), [playground](), [scripting](), [ui]() ### AI overview Codename One adds a new Playground for rapid UI scripting, prototyping, and sharing runnable examples, along with built-in support for the java.time API to improve modern Java compatibility. ### Source excerpt Codename One now includes a new Playground for rapid UI scripting and iteration, and adds built-in support for the java.time API. ## Staying Technical as a Technical Program Manager DevFeed: [Staying Technical as a Technical Program Manager]() Original publisher: [Read original article]() Author: Dean Hume Published: 2026-02-18T11:39:39Z Content type: opinion Language: en Sources: [Dean Hume]() Topics: [Development](), [coding](), [engineering-culture](), [Raspberry Pi](), [Scripting]() Tags: [code](), [development](), [engineering](), [game-development](), [habits](), [hardware](), [learn](), [practices](), [scripting](), [skills](), [technical](), [technical-leadership]() ### AI overview A Technical Program Manager shares practical habits for staying technically sharp while managing programs, including occasional coding, writing technical content, following technology blogs, and building hands-on side projects. ### Source excerpt Learn practical ways Technical Program Managers can stay technical - daily habits, internal engineering practices, and hands-on routines that keep skills sharp while leading programs at scale. ## ClickPy at 2 Trillion rows: Scaling ingestion and fixing the past DevFeed: [ClickPy at 2 Trillion rows: Scaling ingestion and fixing the past]() Original publisher: [Read original article]() Author: Lionel Palacin Published: 2026-01-21T10:48:32Z Content type: article Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [data](), [Python](), [BigQuery](), [dataset](), [cloud-infrastructure](), [Code](), [Scripting]() Tags: [bigquery](), [blog](), [blog-post](), [clickhouse](), [cloud-storage](), [code](), [data](), [database](), [operational](), [python](), [scale](), [scripting](), [storage]() ### AI overview ClickPy has grown to more than 2 trillion Python package-download rows dating back to 2011. This article describes replacing a custom, cron-based ingestion script with ClickPipes and correcting historical data while keeping the service available and ingestion uninterrupted. ### Source excerpt A look at how ClickPy handles over 2 trillion Python package downloads, from ingestion redesign to fixing historical data at scale. ## Embedding Wren in Hare DevFeed: [Embedding Wren in Hare]() Original publisher: [Read original article]() Author: August Published: 2025-08-20T00:00:00Z Content type: article Language: en Sources: [Drew DeVault]() Topics: [Scripting](), [API](), [Library](), [Command-line interface](), [C]() Tags: [api](), [cli](), [library](), [scripting]() ### AI overview The article introduces hare-wren, an interface for embedding the Wren scripting language in Hare programs. It describes its Hare-oriented wrapper around the Wren C API, bidirectional calls between Hare and Wren, an optional asynchronous runtime and standard library, file and process-environment features, third-party module loading, and command-line access without a REPL. ### Source excerpt I've been on the lookout for a scripting language which can be neatly embedded into Hare programs. Perhaps the obvious candidate is Lua - but I'm not particularly enthusiastic about it. When I was evaluating the landscape of tools which are "like Lua, but not Lua", I found an interesting contender: Wren. I found that Wren punches far above its weight for such a simple language. It's object oriented, which, you know, take it or leave it depending on your use-case, but it's very straightforwardly interesting for what it is. I found a few things to complain about, of course - its scope rules are silly, the C API has some odd limitations here and there, and in my opinion the "standard library" provided by wren CLI is poorly designed. But, surprisingly, my list of complaints more or less ends there, and I was excited to build a nice interface to it from Hare. The result is hare-wren. Check it out! The basic Wren C API is relatively straightforwardly exposed to Hare via the wren module, though I elected to mold it into a more idiomatic Hare interface rather than expose the C API directly to Hare. You can use it something like this: use wren; export fn main() void = { const vm = wren::new(wren::stdio_config); defer wren::destroy(vm); wren::interpret(vm, "main", ` System.print("Hello world!") `)!; }; $ hare run -lc main.ha Hello world! Calling Hare from Wren and vice-versa is also possible with hare-wren, of course. Here's another example: use fmt; use wren; export fn main() void = { let config = *wren::stdio_config; config.bind_foreign_method = &bind_foreign_method; const vm = wren::new(&config); defer wren::destroy(vm); wren::interpret(vm, "main", ` class Example { foreign static greet(user) } System.print(Example.greet("Harriet")) `)!; }; fn bind_foreign_method( vm: *wren::vm, module: str, class_name: str, is_static: bool, signature: str, ) nullable *wren::foreign_method_fn = { const is_valid = class_name == "Example" && signature == "greet(_)" && is_static; if (!is_vali ## Enhance Your Firebase Studio Workflow with Gemini CLI DevFeed: [Enhance Your Firebase Studio Workflow with Gemini CLI]() Original publisher: [Read original article]() Author: Jess Kuras Published: 2025-07-22T10:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Command-line interface](), [Artificial Intelligence](), [Google](), [Authentication](), [Automation](), [Code](), [debug]() Tags: [ai](), [authentication](), [automation](), [cli](), [code](), [debugging](), [environment-variables](), [firebase](), [firebase-studio](), [gemini](), [google](), [scripting](), [terminal](), [tutorials](), [updates]() ### AI overview Firebase Studio now includes Gemini CLI preinstalled in its terminal. The article explains who may benefit from using it, how to launch and authenticate it, and how to configure settings, scripting, automation, environment variables, and project-specific instructions. ### Source excerpt News, tutorials, and updates from the Firebase team. ## openHAB 5.0 Release DevFeed: [openHAB 5.0 Release]() Original publisher: [Read original article]() Published: 2025-07-21T19:00:00Z Content type: release Language: en Sources: [openHAB]() Topics: [releases](), [Matter](), [Scripting](), [GitHub](), [pull-requests](), [Code](), [Java]() Tags: [code](), [features](), [github](), [improvements](), [java](), [new-features](), [pull-requests](), [release](), [release-notes](), [scripting](), [tooling]() ### AI overview openHAB 5.0 is a major release with Matter support, a new Python Scripting add-on, upgraded dependencies, Java 21, virtual threads, and 64-bit-only support. The release includes breaking changes and contributions across the project's repositories. ### Source excerpt As this is a major release, we have a number of breaking changes that are required for the new features and improvements. So, please have a look at our official release notes to learn about all breaking changes, new add-ons, enhancements and fixes. ## How to Identify the Package Manager of a Linux System DevFeed: [How to Identify the Package Manager of a Linux System]() Original publisher: [Read original article]() Author: Umara Mushtaq Published: 2025-07-14T02:13:11Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Package Management](), [Linux](), [apt](), [Bash](), [Scripting, bash](), [Ubuntu](), [Automation](), [Debian](), [Arch Linux](), [dnf](), [Fedora](), [pacman]() Tags: [apt](), [automation](), [bash](), [debian](), [dependency](), [dnf](), [efficiency](), [errors](), [how-to](), [installation](), [linux](), [linux-how-to](), [package-management](), [package-management-scripting-apt-dnf-pacman-snap-yum](), [pacman](), [scripting](), [snap](), [ubuntu]() ### AI overview This tutorial explains how to identify the package manager used by a Linux system. It covers inferring the manager from the distribution, checking distribution metadata with /etc/os-release or lsb_release, verifying an installed manager with which, and using Bash scripts to detect package managers in automated or multi-distribution environments. ### Source excerpt Learn different ways to guess or identify the default package manager of a Linux system. The post How to Identify the Package Manager of a Linux System first appeared on Baeldung on Linux. Related Stories How to Check for Available Package Updates in Linux How to Properly Install Valgrind? Background Jobs in a Loop in Bash ## Background Jobs in a Loop in Bash DevFeed: [Background Jobs in a Loop in Bash]() Original publisher: [Read original article]() Author: Sourov Jajodia Published: 2025-06-24T11:47:03Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [Processes]() Tags: [bash](), [jobs](), [linux](), [loops](), [processes](), [resource](), [scripting](), [scripting-bash](), [tutorial]() ### AI overview A Bash tutorial on running loop iterations as background jobs, waiting for completion, and avoiding excessive parallel work. ### Source excerpt Learn several patterns to run background jobs in a loop in Bash. The post Background Jobs in a Loop in Bash first appeared on Baeldung on Linux. Related Stories Why the Value of a Variable Modified in a while Loop Is Not Remembered Outside? Executing Commands in Gnuplot through Shell Script Converting Output to String in Linux ## Using if-else Conditionals in a Makefile DevFeed: [Using if-else Conditionals in a Makefile]() Original publisher: [Read original article]() Author: baeldung Published: 2025-06-06T09:36:00Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [make](), [Linux](), [Operating system](), [gcc]() Tags: [build](), [building](), [building-make-popular](), [code](), [examples](), [gcc](), [how-to](), [learn](), [linux](), [make](), [optimization](), [os](), [popular](), [programming](), [scripting](), [tutorial]() ### AI overview A tutorial explaining how to use if-else conditional directives in Makefiles. It covers ifeq, ifneq, ifdef, and ifndef, with examples for selecting compiler flags, handling operating-system differences, and assigning default variable values. ### Source excerpt Learn how to use if-else conditional statements inside of Makefiles. The post Using if-else Conditionals in a Makefile first appeared on Baeldung on Linux. Related Stories How to Identify the Package Manager of a Linux System Background Jobs in a Loop in Bash Executing Commands in Gnuplot through Shell Script ## Using Lua as ESP-IDF Component with ESP32 DevFeed: [Using Lua as ESP-IDF Component with ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2024-10-22T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Lua](), [ESP-IDF](), [ESP32](), [Embedded Systems](), [Scripting]() Tags: [blog](), [component](), [embedded-systems](), [esp-idf](), [esp32](), [esp32-c3](), [firmware](), [how-to](), [lua](), [monitoring](), [risc-v](), [scripting](), [spiffs]() ### AI overview This tutorial explains how to integrate Lua as an ESP-IDF component in ESP32 projects and run Lua scripts from the SPIFFS filesystem. It covers the example project, cross-architecture support for ESP32 and ESP32-C3, configurable Lua stack size, and memory monitoring while Wi-Fi is enabled. ### Source excerpt Lua is a lightweight and powerful scripting language, making it ideal for use in embedded systems like the ESP32. By integrating Lua into your ESP-IDF project, you can execute scripts directly on the ESP32, offering a flexible way to manage application behavior without recompiling the entire firmware. This guide walks through how to set up Lua as an ESP-IDF component, with a focus on running Lua scripts from the filesystem. ## Listen to the whispers: web timing attacks that actually work DevFeed: [Listen to the whispers: web timing attacks that actually work]() Original publisher: [Read original article]() Author: James Kettle Published: 2024-08-07T18:10:21Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [Web](), [Server](), [ctf](), [Open Source](), [configuration](), [Data structures]() Tags: [attacks](), [ctf](), [open-source](), [pdf](), [presentation](), [research](), [scripting](), [server](), [web]() ### AI overview This research paper presents practical web timing attack techniques for extracting server secrets and exposing hidden attack surfaces. It describes methods involving masked misconfigurations, blind data-structure injection, hidden routes, and automated exploitation, supported by real-world case studies, open-source tools, custom scripting, and a CTF. ### Source excerpt Websites are riddled with timing oracles eager to divulge their innermost secrets. It's time we started listening to them. In this paper, I'll unleash novel attack concepts to coax out server secrets ## Exclusive accordions using the HTML details element DevFeed: [Exclusive accordions using the HTML details element]() Original publisher: [Read original article]() Author: brian-smith Published: 2024-08-05T00:00:00Z Content type: tutorial Language: en Sources: [MDN Blog]() Topics: [Web platform](), [Web Development](), [modern web development]() Tags: [browsers](), [chrome](), [css](), [feature](), [firefox](), [html](), [scripting](), [support](), [ui]() ### AI overview The article explains how the HTML details element's name attribute can create exclusive accordions, allowing only one section in a group to remain open. It also discusses browser support and using HTML and CSS instead of custom scripting. ### Source excerpt The 'name' attribute of the HTML details element is gaining more support across browsers. Learn how this feature allows creating exclusive accordions without scripting widgets from scratch. [Next page]()