# Scripting The practice of creating and running script files containing program source code that an interpreter executes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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 ## 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 ;) ## 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 ## 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. ## 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 ## 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. ## 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. ## A hacking hat-trick: previewing three PortSwigger Research publications coming to DEF CON & Black Hat USA DevFeed: [A hacking hat-trick: previewing three PortSwigger Research publications coming to DEF CON & Black Hat USA]() Original publisher: [Read original article]() Author: James Kettle Published: 2024-07-02T12:57:08Z Content type: article Language: en Sources: [PortSwigger Research]() Topics: [Hacking](), [releases](), [Parser](), [Scripting](), [Open Source](), [ctf]() Tags: [attacks](), [automated](), [black-hat](), [ctf](), [hacking](), [open-source](), [parsing](), [releases](), [research](), [scripting](), [side-channel]() ### AI overview PortSwigger Research previews three publications scheduled for Black Hat USA and DEF CON 32. The article highlights practical timing attacks using timing oracles, including techniques for uncovering server secrets, masked misconfigurations, blind data-structure injection, hidden routes, and invisible attack surfaces. It also describes open-source tools for automated exploitation and attack scripting, a CTF, and a forthcoming session on the challenges of parsing email addresses. ### Source excerpt We're delighted to announce three major research releases from PortSwigger Research will be published at both Black Hat USA and DEF CON 32. In this post, we'll offer a quick teaser of each talk, info ## Node.js script to run multiple commands in parallel DevFeed: [Node.js script to run multiple commands in parallel]() Original publisher: [Read original article]() Author: Stanko Published: 2024-06-13T00:00:00Z Content type: tutorial Language: en Sources: [Stanko Tadić]() Topics: [Node.js](), [JavaScript](), [Command-line interface](), [Scripting](), [Concurrent Programming]() Tags: [bash](), [commands](), [concurrently](), [javascript](), [node-js](), [parallel](), [script]() ### AI overview This tutorial presents a small Node.js script for running multiple commands in parallel. It explains the requirements, including stopping all commands when one fails and prefixing each command's output with color-coded names, and shows how to use and implement the script. ### Source excerpt If you encountered a case where you wanted to run multiple commands in parallel, the usual suggestion is to use the shell's & operator to send commands to the background. This approach kind of works, but it has its quirks. I often ended up with a process hanging in the background, multiple outputs being mangled, or the output of some commands completely missing. Bash scripting wizards can probably solve all of these issues, but I turned to JavaScript, as it is the language I know best. If you're eager to see the code, feel free to jump to it. Why not an existing library? # In my professional projects, I would probably just use concurrently. However, this time I decided to write a poor man's version of it. Although simple and basic, it covers my specific use case. It was mostly for learning purposes, but sometimes I create things from scratch for fun or to avoid installing a large library for a tiny piece of it. My requirements # Run multiple commands in parallel. Terminate all of the commands if any of them fail. Prefix each command's output with its color-codedIn the finished version, I added an option to disable colors, as I know some people really don't like colors in their terminals name. I also decided to keep it simple: No CLI version to avoid parsing the arguments. Name (prefix) should be a mandatory input. Usage # To use the script, you need to import it and pass the list of your commands (along with their names) to it. Like this: import { Runner } from './runner.js'; const tasks = [ { name: 'sass', command: 'npm run sass' }, { name: 'build', command: 'npm run build' }, ]; new Runner(tasks); This is how the script looks in action: Source code # Here is the complete script: import { spawn } from 'child_process'; export class Runner { tasks = []; exiting = false; colors = [ '\x1b[33m', // yellow '\x1b[34m', // blue '\x1b[35m', // magenta '\x1b[36m', // cyan ]; /** * Create a new runner. * @param {Object[]} tasks - List of tasks to run in parallel. * @param {st ## I am very excited about using nushell everyday DevFeed: [I am very excited about using nushell everyday]() Original publisher: [Read original article]() Author: Manideep Polireddi Published: 2023-08-28T13:00:00Z Content type: opinion Language: en Sources: [@okmanideep]() Topics: [Structured-data](), [Bash](), [PowerShell](), [Command-line interface](), [Terminal](), [Scripting]() Tags: [bash](), [here](), [nushell](), [optimizing](), [plugins](), [powershell](), [terminal]() ### AI overview The author explains why Nushell appeals to them as a structured-data shell combining aspects of Bash and PowerShell. They compare Nushell's table-oriented pipelines and clearer property-based sorting with Unix-style commands, while noting that startup and new-terminal performance remain slow despite profiling and optimization. ### Source excerpt From the moment I saw the intro video, I found it very appealing. It takes the best of bash and powershell ## Performance impacts of Apollo Router customizations DevFeed: [Performance impacts of Apollo Router customizations]() Original publisher: [Read original article]() Author: Lucas Leadbetter Published: 2023-07-10T10:00:00Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [configuration](), [Latency](), [Scripting](), [Script](), [Programming language](), [Jule]() Tags: [apollo](), [backend](), [configuration](), [cpu](), [curl](), [docker](), [github](), [kubernetes](), [latency](), [orchestration](), [performance](), [router](), [scripting]() ### AI overview This article examines the performance overhead of three Apollo Router extensibility options: configuration, Rhai scripting, and external coprocessing. It reports that configuration generally performs best, followed by Rhai scripting, while external coprocessing adds about 350 microseconds of overhead. Results can vary with factors such as programming language, task complexity, network proximity, and host machine. ### Source excerpt The Apollo Router features three customization options out of the box to adjust behavior: configuration options, Rhai scripting, and external coprocessing. We refer to these as extensibility options. Extensibility of the Router is one of its primary strengths and is a critical feature for many organizations large and small. Understanding the performance implications of these options is important as the Router is designed for performance and serves as the entry point to your supergraph. ## Using Kotlin Scripts and GitHub Copilot for Quick Command-Line Tasks DevFeed: [Using Kotlin Scripts and GitHub Copilot for Quick Command-Line Tasks]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2023-05-07T01:25:34Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [Kotlin](), [GitHub Copilot](), [Scripting](), [Command-line interface](), [Markdown](), [Scripting, bash]() Tags: [bash](), [command-line](), [github](), [github-copilot](), [how-to](), [ide](), [kotlin](), [markdown](), [scripting](), [video]() ### AI overview This tutorial presents Kotlin scripts as an alternative to Bash for command-line automation and demonstrates using GitHub Copilot to build a script that processes Markdown front matter. The author reports completing the example in less than 4½ minutes, including IDE autocomplete setup. ### Source excerpt One of the gifts we got from Kotlin 1.3.70 was the ability to effortlessly run a kscript (Kotlin script) from the command line. All you need to do is add the suffix .main.kts. Seriously, this is all you need to do: brew install kotlin echo '#!/usr/bin/env kotlin' > hello-world.main.kts chmod +x hello.main.kts ./hello.main.kts # 💥 With this 0 friction setup, there's little reason for me to ever write a bash script again. I get to write my script in Kotlin -- a modern & beautiful language. But slap on Github Copilot and I think we've unlocked the holy grail of quick scripting. To prove my point, I recorded a video live coding a script tackling a moderately involved task. Here's what I wanted to do: Take a directory path as argument Make sure it's valid and has at least one .md (markdown) file in it Search the front matter for the "categories" array pluck all the categories from all the files de-duplicate, sort and print them out The entire thing took less than 4½ minutes. This is including me figuring out how to get autocomplete working in my IDE, restarting it etc. Sure I could try to wield a one-line command and do the same thing for this use case but it's so much nicer in Kotlin. If you're intrigued, feel free to checkout my github repo of kscripts. I try to tackle a variety of common use cases in there P.S: The text snippet I use in there kscript;; basically gives me a starter hello world template. Not cheating, I promise. ## Pleasant debugging with GDB and DDD DevFeed: [Pleasant debugging with GDB and DDD]() Original publisher: [Read original article]() Published: 2022-07-17T00:00:00Z Content type: article Language: en Sources: [Joe Nelson]() Topics: [debugging](), [configuration](), [Terminal](), [Linux](), [Scripting](), [Text-based user interface]() Tags: [article](), [configuration](), [ddd](), [debugger](), [debugging](), [gdb](), [linux](), [scripting](), [terminal]() ### AI overview This article presents configuration and scripting techniques for making GDB debugging more pleasant on Linux and BSD systems. It compares several interface-customization approaches and focuses on using the Data Display Debugger (DDD), including workarounds for its compatibility problems with recent GDB versions and its remote SSH support. ### Source excerpt 2022-07-17 GDB is an old and ubiquitous debugger for Linux and BSD systems that has extensive language, processor, and binary format support. Its interface is a little cryptic, but learning GDB pays off. This article is a set of miscellaneous configuration and scripting tricks that illustrate reusable principles. It assumes you're familiar with the basics of debugging, like breakpoints, stepping, inspecting variables, etc. Table of contents By default, GDB provides a terse line-based terminal. ## Miller: Command-Line Data Processing for CSV, TSV, JSON, and JSON Lines DevFeed: [Miller: Command-Line Data Processing for CSV, TSV, JSON, and JSON Lines]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2022-05-13T16:54:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [CSV](), [Data Science](), [Scripting](), [Command-line interface]() Tags: [command-line](), [commands](), [csv](), [data-science](), [json](), [miller](), [perl](), [python](), [ruby]() ### AI overview A practical tutorial introducing Miller, a command-line tool for querying, shaping, and reformatting CSV, TSV, JSON, and JSON Lines data. It covers installation, command structure, help commands, output redirection, and examples such as listing and selecting lines from CSV files. ### Source excerpt Every so often I run into a tool which just impresses me. This time it is Miller. And when I find such a tool, I write up a blog post to firm up my learnings. Here is the official description: Miller is a command-line tool for querying, shaping, and reformatting data files in various formats including CSV, TSV, JSON, and JSON Lines. The people that know me know that I've spent literal man years working with textual data, often CSV format - I first got started at this using Awk, specifically the NTERGAID version of Awk called HyperAwk and then I've done the Perl dance, spent time in the bowels of the abyss that is Sed, PHP, Python and Ruby. A lot of the ad hoc scripting I've written over the years can be accomplished via Miller and that is a lovely change. Just as a note, Miller's docs are really quite excellent and it is a sophisticated tool. This blog post really only touches a bit on what Miller is capable of. If you don't find what you are looking here then hit the docs. Installation I'm on a Mac so all this took was: brew install miller To confirm this works, just type: mlr --version and you should get back something like 6.x.y. I got: mlr 6.2.0 General Command Structure and Operation Miller is a command line tool that operates with commands like this: mlr --csv sort -f name input.csv Basically the syntax amounts to: input type command verb (sort in this case) option flag input source Getting Help The -help flag gives you help: mlr --help Usage: mlr [flags] {verb} [verb-dependent options ...] {zero or more file names} If zero file names are provided, standard input is read, e.g. mlr --csv sort -f shape example.csv Output of one verb may be chained as input to another using "then", e.g. mlr --csv stats1 -a min,mean,max -f quantity then sort -f color example.csv Please see 'mlr help topics' for more information. Please also see https://miller.readthedocs.io The mlr help topics command is quite informative: mlr help topics Type 'mlr help {topic}' for any of the fol ## Scripting Languages and Compiled Languages in WebAssembly DevFeed: [Scripting Languages and Compiled Languages in WebAssembly]() Original publisher: [Read original article]() Author: Matt Butcher Published: 2022-03-07T21:51:54Z Content type: article Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [WebAssembly](), [Scripting](), [JavaScript](), [Python](), [Ruby](), [C](), [C++](), [Go](), [Rust]() Tags: [c](), [c-plus-plus](), [go](), [javascript](), [python](), [ruby](), [rust](), [scripting](), [webassembly]() ### AI overview This article surveys WebAssembly across scripting languages such as JavaScript, Python, and Ruby and compiled languages such as C, C++, Go, and Rust, highlighting differences in how developers traditionally work with these language groups. ### Source excerpt The promise of WebAssembly is that it can be a common runtime for all sorts of languages. But there are differences between how we traditionally write in scripting languages (JavaScript, Python, Ruby) versus compiled languages (C/C++, Go, Rust). In this post, we survey the WebAssembly landscape to see what is happening along these fronts. ## Why I migrated to the Fish Shell DevFeed: [Why I migrated to the Fish Shell]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2020-12-07T00:00:00Z Content type: opinion Language: en Sources: [Carlos Becker]() Topics: [friendly interactive shell](), [Shell](), [Zsh](), [Bash](), [dotfiles](), [Command-line interface](), [Environment Variables](), [lazy loading](), [Scripting]() Tags: [aliases](), [bash](), [environment-variables](), [lazy-loading](), [plugins](), [porting](), [prompt](), [scripting](), [shell](), [zsh]() ### AI overview The author explains migrating dotfiles from Zsh to Fish, emphasizing Fish's startup performance, universal variables, lazy loading, and built-in features such as syntax highlighting, autosuggestions, and man-page completions. The article also notes differences from POSIX shells and describes the author's plugin setup. ### Source excerpt Back in June, I started porting my dotfiles from ZSH to Fish. Here's why. ## Investigating AVX-512 Frequency Transitions on Intel CPUs DevFeed: [Investigating AVX-512 Frequency Transitions on Intel CPUs]() Original publisher: [Read original article]() Author: Travis Downs (travis.downs@gmail.com) Published: 2020-01-17T00:00:00Z Content type: article Language: en Sources: [Performance Matters]() Topics: [intel](), [Benchmark](), [Linux](), [Code](), [Script](), [Scripting](), [Shell]() Tags: [avx](), [benchmark](), [blog](), [c-plus-plus](), [code](), [hardware](), [intel](), [linux](), [metrics](), [performance](), [python](), [scripting](), [shell](), [tests](), [uarch]() ### AI overview This article investigates the detailed behavior of AVX and AVX-512 frequency transitions on Intel CPUs using target tests and sampled performance metrics. It describes the test structure and provides accompanying source code and data-generation scripts. ### Source excerpt Investigating some details of SIMD related frequency transitions on Intel CPUs. ## Creating valid and accessible links DevFeed: [Creating valid and accessible links]() Original publisher: [Read original article]() Author: Emma Patricios Published: 2019-02-15T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [HTML](), [Web Development](), [Web platform](), [web-standards](), [CSS](), [Scripting]() Tags: [article](), [css](), [html](), [scripting](), [web]() ### AI overview This article explains how to create valid and accessible HTML links. It covers required link structure, meaningful link text, cautious use of the title attribute, visible keyboard focus states, and preserving native keyboard behavior. ### Source excerpt The anchor element is often cited as the main building block of the World Wide Web. It is used to create a link to other pages, to anchors within the same page, to other resources (such as a PDF) or to an email address. How can we make sure they are accessible to everyone? Start with valid HTML To be a valid link it must have: A href attribute: The location of the anchor, page or resource. Link content Text describing where the link is going, this could be plain text or the alt attribute of an image. Opening and closing tags. Write helpful link text Common unhelpful link texts are 'click here', 'read more' and 'link'. These are problematic because when a person using a screen reader is navigating using links alone these will be read out of context. Where would you expect any of those three links to go if you heard them? It's impossible to know. Think about restructuring your sentence to remove 'click here' or 'link' and then surround the meaningful part with the link: To see our documentation click here. We have made our documentation available. "Read more" can be fixed by including what we will be reading more about: Read more. Read more - Accessible Landmarks What about the title attribute? The title attribute is not exposed by all browsers in an accessible way meaning that people using keyboards and touch-only devices will likely never see that information. If you want to hide content from mobile and tablet users as well as assistive tech users and keyboard only users, use the title attribute. Using the HTML title attribute - TTPGi It is therefore not recommended to use the title attribute on elements. If you do use it don't double up on the accessible name of the link, this can produce unnecessary duplicate announcements to some screen readers. Focus state and keyboard Some developers/designers se [Next page]()