# Modular Published articles for Modular. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Power Banks Make You Pick a Size, Trozk T3 Lets You Build One DevFeed: [Power Banks Make You Pick a Size, Trozk T3 Lets You Build One]() Original publisher: [Read original article]() Author: JC Torres Published: 2026-09-17T13:20:55Z Content type: article Language: en Sources: [Yanko Design]() Topics: [Hardware]() Tags: [battery](), [capacity](), [fast](), [gadgets](), [gadgets-technology-modular-power-bank](), [hardware](), [modular](), [power](), [power-bank](), [technology]() ### AI overview The Trozk T3 Module Power Bank uses separate modules that can be combined or detached to provide 5,000mAh, 10,000mAh, or 15,000mAh of capacity. It supports charging up to 22.5W through PD and QC protocols and includes built-in safety protections, automotive-grade 21700 cells, and a color status display. ### Source excerpt Power Banks Make You Pick a Size, Trozk T3 Lets You Build One Most power banks force a single decision at checkout: buy the huge one for peace of mind, or the tiny one for your pocket, and... ## Syitren R400 is a portable Bluetooth CD player with a modular, customizable design DevFeed: [Syitren R400 is a portable Bluetooth CD player with a modular, customizable design]() Original publisher: [Read original article]() Author: Ida Torres Published: 2026-09-15T13:20:31Z Content type: opinion Language: en Sources: [Yanko Design]() Topics: [Hardware](), [Bluetooth]() Tags: [2026](), [a-design-award-and-competition](), [audio](), [audio-music-technology-a-design-award-and-competition-cd-player-music-player](), [bluetooth](), [cd-player](), [collection](), [cost](), [design](), [hardware](), [modular](), [mount](), [music](), [music-player](), [portable](), [product](), [technology]() ### AI overview The article presents Syitren's R400 as an entry-level portable Bluetooth CD player designed by ORGDOT Design. Its detachable modular shell supports customization, a desk stand, and an optional wall-mount bracket, while dual-material construction and cable-management details aim to improve everyday use. ### Source excerpt Finally, a CD Player Gen Z Actually Wants to Own It really warms my heart when I see Gen Z and Gen Alpha kids collecting physical media from their favorite artists. These are people who... ## Dell Pro 5 16 (AMD) Laptop Review DevFeed: [Dell Pro 5 16 (AMD) Laptop Review]() Original publisher: [Read original article]() Author: Ryan Smith Published: 2026-09-14T16:25:36Z Content type: article Language: en Sources: [ServeTheHome]() Topics: [dell](), [Hardware](), [cpu](), [intel]() Tags: [amd](), [cpu](), [dell](), [external](), [hardware](), [intel](), [intel-core](), [laptop](), [laptops](), [mobile](), [modular](), [overview](), [performance](), [platform](), [portable](), [product](), [review](), [ryzen-ai](), [series](), [strix-point](), [thunderbolt]() ### AI overview A review of Dell's 16-inch Pro 5 business laptop powered by an AMD Ryzen AI 400 series processor. The article highlights its performance, modularity, business positioning, and comparability with Intel-based Dell models. ### Source excerpt Today we are taking a look at Dell's 16-inch laptop for mainstream business segment, the AMD-based Dell Pro 5 16. The pro laptop hits all the high notes, pairing an AMD Ryzen AI 9 HX PRO 470 processor with great modularity and a good balance between size, weight, and performance The post Dell Pro 5 16 (AMD) Laptop Review appeared first on ServeTheHome. ## A Custom Handheld Cyberdeck Rehouses an M4 Mac Mini Motherboard DevFeed: [A Custom Handheld Cyberdeck Rehouses an M4 Mac Mini Motherboard]() Original publisher: [Read original article]() Author: JC Torres Published: 2026-09-14T10:07:38Z Content type: article Language: en Sources: [Yanko Design]() Topics: [Mac Mini](), [macOS](), [touchscreen](), [USB](), [3D]() Tags: [3d](), [apple](), [cyberdeck](), [diy](), [gadgets](), [gadgets-gaming-technology-cyberdeck-diy-gaming-handheld-mac-mini-modular](), [gaming](), [gaming-handheld](), [mac-mini](), [macos](), [modular](), [technology](), [touchscreen](), [usb]() ### AI overview A builder converted an M4 Mac Mini motherboard into the core of a handheld cyberdeck. The custom 3D-printed device retains the original cooling system, runs macOS, and includes a touchscreen, keyboard, wired Joy-Con controls, and a USB hub. ### Source excerpt The Mac Mini Belongs on a Desk, This Build Runs It From Your Hands Most people who outgrow a Mac Mini just buy a bigger one. One builder went the opposite direction, gutting an M4 Mac Mini down to... ## Modular Monoliths: Creating Real Boundaries Before Reaching for Microservices DevFeed: [Modular Monoliths: Creating Real Boundaries Before Reaching for Microservices]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-08-20T13:48:25Z Content type: article Language: en Sources: [freek.dev - all blogposts]() Topics: [Architecture & Design](), [Microservice](), [Database]() Tags: [apis](), [architecture](), [database](), [design-patterns](), [microservices](), [migration](), [modular](), [monolith](), [tests]() ### AI overview This article examines modular monoliths as a way to establish real architectural boundaries before adopting microservices. It covers module APIs, database ownership, cross-module communication, architecture tests, incremental migration, and signals that may justify a move to microservices. ### Source excerpt A deep dive into modular monoliths, from module APIs and database ownership to cross-module communication, architecture tests, incremental migration, and the signals that justify microservices. Read more ## AI Coding Tip 025 - Pair Every Skill With a Pitfalls File DevFeed: [AI Coding Tip 025 - Pair Every Skill With a Pitfalls File]() Original publisher: [Read original article]() Author: Maxi Contieri Published: 2026-06-20T00:51:51Z Content type: tutorial Language: en Sources: [Maximiliano Contieri - Software Design]() Topics: [ai-coding](), [coding](), [Artificial Intelligence](), [Documentation]() Tags: [ai](), [ai-coding](), [coding](), [memory](), [mistakes](), [modular](), [pitfalls](), [skills]() ### AI overview This tutorial recommends placing an append-only PITFALLS.md file beside each SKILL.md to record an AI's recurring mistakes, their triggers, and the correct behavior. The goal is to preserve corrections across sessions while keeping skill documentation focused on the normal workflow. ### Source excerpt TL;DR: Add a PITFALLS.md next to every SKILL.md so your AI never repeats the same mistake twice. Common Mistake ❌ You write a great SKILL.md. The AI follows it well most of the time. Then it does som ## Monolith vs Microservices vs Modular Monoliths DevFeed: [Monolith vs Microservices vs Modular Monoliths]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-05-12T04:10:14Z Content type: article Language: en Sources: [AlgoMaster Newsletter]() Topics: [Software](), [Microservice](), [Database]() Tags: [database](), [microservices](), [modular](), [monolith](), [software]() ### AI overview The document introduces software systems that begin with a small team, a single codebase, one database, and a few features, in the context of comparing monoliths, microservices, and modular monoliths. ### Source excerpt Most software systems start simple. A small team, a single codebase, one database, and a few features. ## Creating an Arduino Library for ESP32 DevFeed: [Creating an Arduino Library for ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2025-12-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Arduino](), [ESP32](), [Library](), [Development](), [Code](), [C++](), [ide](), [Programming](), [API]() Tags: [arduino](), [arduino-ide](), [beginner](), [blog](), [c-plus-plus](), [class](), [classes](), [code](), [development](), [esp32](), [getting-started](), [guide](), [how-to](), [ide](), [libraries](), [library](), [maintainability](), [modular](), [modularity](), [modules](), [programming](), [structure](), [tutorial]() ### AI overview A step-by-step guide to creating, structuring, and publishing custom Arduino libraries for ESP32. It explains library benefits and structure, prerequisites, and implementation through a minimal "Hello World" example. ### Source excerpt Learn how to create, structure, and publish Arduino libraries for ESP32. This step-by-step guide covers everything from understanding a library structure to submitting your library to the Arduino Library Manager. ## Exploring a space-based, scalable AI infrastructure system design DevFeed: [Exploring a space-based, scalable AI infrastructure system design]() Original publisher: [Read original article]() Published: 2025-11-04T16:58:00Z Content type: article Language: en Sources: [The latest research from Google]() Topics: [AI Infrastructure](), [Google](), [AI Platform](), [AI Research]() Tags: [2025](), [ai](), [ai-infrastructure](), [compute](), [engineering](), [general-science](), [google](), [machine-learning](), [modular](), [orbit](), [paper](), [research](), [responsible-ai](), [science](), [solar](), [space]() ### AI overview Google describes Project Suncatcher, a research moonshot exploring solar-powered satellite constellations equipped with TPUs and connected by free-space optical links. The proposed system aims to scale machine learning compute in space while addressing communication, orbital dynamics, radiation, and modular satellite design challenges. ### Source excerpt General Science ## Structured Tags in OpenAPI 3.2: Organising APIs the Way They Deserve DevFeed: [Structured Tags in OpenAPI 3.2: Organising APIs the Way They Deserve]() Original publisher: [Read original article]() Author: Zaid Daba'een Published: 2025-10-26T21:00:37Z Content type: article Language: en Sources: [DeveloperHub.io]() Topics: [OpenAPI Specification](), [Documentation](), [API](), [SDKs]() Tags: [api-design](), [api-documentation](), [engineering](), [modular](), [navigation](), [openapi](), [sdks](), [structured]() ### AI overview OpenAPI 3.2 adds structured, hierarchical tags that let APIs organize endpoints into nested categories. The article explains how this can improve documentation navigation, SDK organization, and maintainability for large or modular APIs. ### Source excerpt OpenAPI 3.2 introduces structured tags, allowing APIs to organize endpoints into nested categories for clearer, more maintainable documentation. ## Genesis IoT Discovery Lab - A Plug-and-Play Classroom Built on ESP32-S3 DevFeed: [Genesis IoT Discovery Lab - A Plug-and-Play Classroom Built on ESP32-S3]() Original publisher: [Read original article]() Author: John Lee Published: 2025-06-27T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32-S3](), [Internet of things](), [Hardware](), [Arduino](), [MicroPython](), [CircuitPython](), [ESP-IDF](), [cross-platform](), [Crowd Supply]() Tags: [announcement](), [arduino](), [blog](), [circuitpython](), [cross-platform](), [crowd-supply](), [education](), [esp-idf](), [esp32-s3](), [genesis](), [hardware](), [iot](), [micropython](), [modular](), [modular-hardware](), [open-hardware](), [prototyping]() ### AI overview Genesis IoT Discovery Lab is a modular, open-hardware prototyping kit built around the ESP32-S3-WROOM-1-N8R2. It uses standardized AX22 ports and snap-in modules for hands-on learning, classroom projects, and portable experimentation. ### Source excerpt Genesis turns the ESP32-S3 into a modular playground with snap-in AX22 modules for prototyping, teaching, and creative hardware experimentation. ## Holo1: New family of GUI automation VLMs powering GUI agent Surfer-H DevFeed: [Holo1: New family of GUI automation VLMs powering GUI agent Surfer-H]() Original publisher: [Read original article]() Author: Mats L Richter; Pierre-Louis Cedoz Published: 2025-06-03T13:27:59Z Content type: release Language: en Sources: [Hugging Face - Blog]() Topics: [Artificial Intelligence](), [computer-use](), [browsers](), [Website](), [Benchmark](), [Transformers](), [hugging face](), [Localization (l10n)]() Tags: [agents](), [ai](), [automation](), [benchmarks](), [browsers](), [cost](), [gui](), [models](), [modular](), [open-source](), [performance](), [transformers](), [vlms](), [web]() ### AI overview Holo1 is an open-source family of Action VLMs for understanding web interfaces and locating UI elements precisely. Holo1-3B and Holo1-7B are released on Hugging Face with the WebClick benchmark; Holo1-7B reports 76.2% average accuracy on common UI localization benchmarks. The article also describes Surfer-H, a browser-based web automation agent built with separate policy, localization, and validation components. ### Source excerpt Surfer-H, a web-native agent that interacts with browsers like a human relies on the Holo1. Holo1 is the first family of open-source Action VLMs designed specifically for deep web UI understanding and precise localization. The family includes Holo1-3B and Holo1-7B models, with the latter achieving 76.2% average accuracy on common UI localization benchmarks--the highest among small-size models. ## Bevy Entity Component System on ESP32 with Rust no\_std DevFeed: [Bevy Entity Component System on ESP32 with Rust no\_std]() Original publisher: [Read original article]() Author: John Lee Published: 2025-04-09T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Bevy](), [Rust](), [ESP32](), [Development]() Tags: [bevy](), [blog](), [component](), [ecs](), [embedded](), [embedded-systems](), [esp32](), [esp32-c3](), [esp32-s3](), [microcontrollers](), [modular](), [modularity](), [no-std](), [rust](), [wasm]() ### AI overview This tutorial demonstrates how to use Bevy ECS with Rust no_std on ESP32 devices. It explains ECS concepts and shows embedded application examples based on Conway's Game of Life and the Spooky Maze Game, with an emphasis on modular code structure and event-based peripheral integration. ### Source excerpt Introduction# Embedded development in Rust is rapidly evolving, and one of exciting new developments is the introduction of no_std support into the Bevy Entity Component System (ECS). This improvement allows developers to leverage the powerful and modular design of Bevy ECS on resource-constrained devices like the ESP32. ## Angular Architecture Guide To Building Maintainable Applications at Scale DevFeed: [Angular Architecture Guide To Building Maintainable Applications at Scale]() Original publisher: [Read original article]() Author: Juri Strumpflohner Published: 2025-03-18T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Architecture & Design](), [Domain-driven design (DDD)](), [Scalability](), [Tooling]() Tags: [angular](), [architecture](), [collaboration](), [design](), [development](), [domain](), [domain-driven-design](), [guide](), [how-to](), [key-angular](), [key-architecture](), [maintainability](), [modular](), [nx](), [scalable-architecture](), [scale](), [software-architecture](), [structure](), [tooling]() ### AI overview A guide to architecting maintainable Angular applications at scale. It explains modular design, clear boundaries, dependency decoupling, layered and vertical architectures, and organizing code around business domains. ### Source excerpt Learn how to build scalable Angular applications using domain-driven design, clear boundaries, and Nx tooling for better maintainability and team collaboration. ## Controlling Language Model Generation with NVIDIA's LogitsProcessorZoo DevFeed: [Controlling Language Model Generation with NVIDIA's LogitsProcessorZoo]() Original publisher: [Read original article]() Author: Aritra Roy Gosthipaty; Ahmet Erdem Published: 2024-12-23T00:00:00Z Content type: article Language: en Sources: [Hugging Face - Blog]() Topics: [Language models](), [Nvidia](), [hugging face](), [AI Development](), [Open Source]() Tags: [artificial-intelligence](), [generation](), [hugging-face](), [language-models](), [llm](), [model](), [models](), [modular](), [nvidia](), [open](), [open-source](), [research](), [text-generation](), [transformers](), [workflows]() ### AI overview This article explains how logit processing controls language model generation by modifying prediction scores before they become token probabilities. It introduces Hugging Face's LogitsProcessor API and NVIDIA's modular LogitsProcessorZoo, highlighting use cases such as sequence-length control, key-phrase enforcement, and multiple-choice guidance. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## Nix Weekly Recap: 2024-07-07 DevFeed: [Nix Weekly Recap: 2024-07-07]() Original publisher: [Read original article]() Published: 2024-07-07T00:00:00Z Content type: news Language: en Sources: [nixpkgs.news]() Topics: [Nix](), [OpenSSH](), [vulnerability](), [Development](), [Command-line interface](), [FIRST](), [Shell](), [Bash](), [GitHub]() Tags: [github](), [modular](), [module](), [news](), [openssh](), [recap](), [report](), [security](), [security-advisory](), [weekly]() ### AI overview This weekly Nix ecosystem recap announces that nixpkgs.news will stop issuing new releases and focus primarily on news about Lix and Aux. It also covers an OpenSSH CVE-2024-6387 security advisory, the modular make-shell project, the faster nix-search utility, and updates to Nixpkgs governance. ### Source excerpt Critical SSH vulnerability, improved DX for dev shells, faster search, and Nix Constitutional Assembly updates. ## Five Years of Apollo Federation: the Standard for Enterprise API Platforms DevFeed: [Five Years of Apollo Federation: the Standard for Enterprise API Platforms]() Original publisher: [Read original article]() Author: Jeff Auriemma Published: 2024-04-09T05:35:00Z Content type: opinion Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [API](), [Framework]() Tags: [announcement](), [apollo-federation](), [architecture](), [enterprise](), [governance](), [graphql](), [modular](), [platforms](), [scale]() ### AI overview The article marks five years since Apollo Federation code was first published and reviews GraphQL federation's role in composing APIs at scale. It describes federation as declarative, composable, modular, and compatible with centralized governance and team autonomy, while citing adoption by several organizations and Gartner's forecast of increased enterprise use. ### Source excerpt GraphQL federation has emerged as the industry consensus for composing APIs at scale. Organizations such as Netflix, Expedia, and Wayfair quickly adopted this architecture to abstract API complexity and further adoption is on the rise. Gartner predicts that "By 2027, 30% of enterprises using GraphQL will use GraphQL federation, up from less than 5% in 2024."1 This pattern didn't emerge by accident; it was created and refined here at Apollo GraphQL. ## A Packwerk Retrospective DevFeed: [A Packwerk Retrospective]() Original publisher: [Read original article]() Author: Gannon McGibbon Published: 2024-02-07T21:40:35Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Rails](), [Dependency management](), [Ruby](), [Command-line interface](), [Code](), [Shopify]() Tags: [analysis](), [article](), [blog](), [command-line](), [dependencies](), [modular](), [retrospective](), [ruby](), [shopify](), [tool]() ### AI overview A retrospective on Packwerk, a Ruby gem released by Shopify in 2020 to enforce boundaries and modularize Rails applications. It describes Packwerk as a static analysis and dependency management tool that analyzes constant references, organizes code into packages, and identifies violations of declared dependency relationships. ### Source excerpt This article was originally posted on the Rails at Scale blog. In September, 2020, our team at Shopify released a Ruby gem named Packwerk, a tool to enforce boundaries and modularize Rails applications. Since its release, Packwerk has taken on a life of its own, inspiring blog posts, conference talks, and even an entire gem ecosystem. Its popularity is an indication that Packwerk clearly filled a void in the Rails community. ## A Journey from Monolith to Micro frontends at Udemy -- Part 1 of 3 DevFeed: [A Journey from Monolith to Micro frontends at Udemy -- Part 1 of 3]() Original publisher: [Read original article]() Author: Hamza ERBAY Published: 2024-01-02T18:47:48Z Content type: article Language: en Sources: [Udemy Engineering]() Topics: [Front end](), [Architecture & Design](), [Scalability](), [Development]() Tags: [architecture](), [development](), [frontend](), [innovation](), [modular](), [monolithic-architecture](), [performance](), [scalability](), [user-experience]() ### AI overview Udemy describes its migration from a monolithic frontend architecture toward micro frontends. The article explains that scaling created bottlenecks in development speed, release processes, CDN use, and user experience, motivating a more modular and scalable architecture. ### Source excerpt Transforming Frontend Architecture: A Journey from Monolith to Micro Frontends at Udemy -- Part 1 of 3 By: Chris Nienhuis, Hamza Erbay, Matthew Bise, Nathan Chapman, Seth Hodgson, Trey Briggs, Charles Pham Photo by Annie Spratt on UnsplashIntroduction At Udemy, we have over 67M learners and over 75K instructors, and we're working on a fast and accessible experience for them. Our underlying application architecture is a monolith -- a single, unified codebase that houses our marketplace, consumer subscription services, and business applications. The engine that powers our global platform is constantly being improved by our dedicated teams working to enhance the learning and teaching experience. In the spirit of innovation, we pitched an idea at the 2021 hackathon to decouple frontend engineering from the monolithic structure. The concept resonated with the hackathon committee (Shark Tank Council), earning a decisive nod. Thus began our odyssey toward a more modular, resilient, and scalable frontend architecture. Motivation to migrate monolith to micro frontend At the heart of our decision to migrate from a monolithic architecture to micro frontends was the need to address critical pain points impeding our ability to scale and innovate effectively. Development Speed and Scalability Our monolithic application served us well in the early days, but as we scaled, it became a double-edged sword. Development speed slowed to a crawl due to two main bottlenecks: When you start a new project, the build process takes approximately 10-15 mins. Cold Start (blue and orange), Warm Start (only orange boxes)Complex Release Process Deploying our code was a difficult and time-consuming process. Any changes to the code had to go through a slow and tedious cycle of review, approval, and queuing, which often took several days, especially during release freezes. This slow process was not sustainable for a growing global team generating many experiments. The release process can take days.In 20 ## VIPER Architecture for iOS Apps DevFeed: [VIPER Architecture for iOS Apps]() Original publisher: [Read original article]() Author: Surbhi Gupta Published: 2023-05-18T14:59:24Z Content type: tutorial Language: en Sources: [ymedialabs-innovation - Medium]() Topics: [iOS](), [Code](), [business logic](), [ui](), [navigation](), [mvc]() Tags: [apps](), [architecture](), [business-logic](), [code](), [controllers](), [flow](), [ios](), [modular](), [mvc](), [mvvm](), [navigation](), [patterns](), [swift](), [ui](), [viper]() ### AI overview This tutorial explains VIPER, an architectural pattern for iOS apps. It describes how VIPER divides each module into View, Presenter, Interactor, Entity, and Router components, with separate responsibilities and delegation-based communication. ### Source excerpt What is a Good Architecture? Architecture serves as a blueprint for a system. It provides a mechanism to communicate between various components and abstracts the complexity. It is important to separate out code components so that they are identifiable, serve a single purpose/responsibility and also fit logically. Code should be scalable, stable upon expansion, and flexible, which brings in the need for a good architecture. A good architecture not only helps in the success of the product but also allows for easy maintenance and makes people's lives easier. This article will talk about VIPER architecture, which is used to build many large projects. What is VIPER? VIPER is an architectural pattern like MVC and MVVM. One of the major issues with MVC and MVVM is bulky controllers. VIPER solves this problem by following Single Responsibility Principle and making the code more modular. Flow of Control Each module created with VIPER has five classes, each with their own responsibilities. No class does anything other than the specified role. These classes are listed below: View: It is responsible for only maintaining and displaying the view. It picks up any user interactions and passes the information to the presenter to decide the next step. Unlike other architecture patterns like MVC or MVVM, its sole responsibility is to manage and show the UI. Presenter: It is the only class that interacts with all other components except Entity. It is the decision-making engine for routing the flow. Interactor: It interacts with Entity and contains business logic. This class is where all the API calls and database interactions are added. Entity: Data model that is used by the interactor. Router: It does all the wire-framing or navigation from one module to another based on the information passed by the presenter. An ideal folder structure would be like below: Ideal Folder Structure with VIPER The communication between various components follows a delegation pattern. One component calls ## The Road To 1.0 DevFeed: [The Road To 1.0]() Original publisher: [Read original article]() Author: Nenad Rakocevic (noreply@blogger.com) Published: 2022-07-14T16:41:00Z Content type: opinion Language: en Sources: [Red]() Topics: [Red](), [modules](), [Package Management](), [Concurrency](), [toolchain](), [Compiler]() Tags: [announce](), [build](), [compilation](), [concurrency](), [modular](), [package-management](), [toolchain]() ### AI overview The Red project presents an updated plan focused on completing its core language and reaching version 1.0. The plan includes upgrading the 32-bit implementation, formalizing the language specification, adding modules and package management, defining a concurrency model, and preparing a new toolchain. ### Source excerpt You cannot have missed that in the last months (and even last years), our overall progress has slowed down drastically. One of the main reasons is that we have spread our limited resources chasing different objectives while making little progress on the core language. That is not satisfying at all and would bring us most likely to a dead-end as we exhaust our funding. We have spent the last weeks discussing about how to change that. This is our updated action plan. From now on, our only focus will be to finish the core language and bring it to the much-awaited version 1.0. We need to reach that point in order to kickstart a broader adoption and provide us and our users a stable and robust foundation upon which we can build commercial products and services necessary for sustainability. Given the complexities involved in completing the language and bringing an implementation that can run on modern 64-bit platforms, we have devised a two-stage plan. Upgrade the current 32-bit Red implementation 👉 Language specification It is now time to do so in order to clean-up some semantic rules and address all possible edge cases which will help fulfill our goals of implementation robustness and stability. The process of writing down the complete language specs will result in dropping some features that we currently have that end up being problematic or inconsistent. OTOH, we might add some new features that will need to be implemented for 1.0. 👉 Modules We need a proper module system in order to be scalable. We also need to have a proper package management system which will be tied to a central repo where we can gather third-party libraries. That would also enable modular/incremental compilation (or encapping) which will be most probably supported in the self-hosted toolchain. 👉 Concurrency We need a proper model for concurrent execution in order to leverage multicore architectures. We will define one and make a prototype implementation in the 32-bit version. 👉 Toolchain Before s ## The supergraph: a new way to think about GraphQL DevFeed: [The supergraph: a new way to think about GraphQL]() Original publisher: [Read original article]() Author: Matt DeBergalis Published: 2022-05-18T09:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [API](), [Architecture & Design](), [Microservices](), [Microservice](), [Kubernetes](), [React]() Tags: [announcement](), [apis](), [apollo](), [apollo-federation](), [architecture](), [bff](), [deployment](), [graphql](), [kubernetes](), [microservices](), [mobile-development](), [modular](), [modularity](), [react](), [updates](), [use-cases]() ### AI overview Apollo announces the general availability of Apollo Router and a cloud-hosted build pipeline, alongside recent releases of Federation 2 and Contracts. The article introduces "supergraph" architecture as a unified, modular approach to composing GraphQL APIs, organizational data, microservices, and digital capabilities. ### Source excerpt We've had a busy month at Apollo. Over the last several weeks we've released some significant updates to the Apollo stack. Last month we shipped Federation 2, a sophisticated and more flexible approach to GraphQL composition. And last week we made Contracts generally available, a way to tailor your graph to specific use cases like mobile development or creating public GraphQL APIs. ## How to Improve User Experience (and Behavior): Three Papers from Stanford's Alexa Prize Team DevFeed: [How to Improve User Experience (and Behavior): Three Papers from Stanford's Alexa Prize Team]() Original publisher: [Read original article]() Author: A Href; Amelia Hardy; Haojun Li; Abigail See Published: 2022-02-01T08:00:00Z Content type: article Language: en Sources: [The Stanford AI Lab Blog]() Topics: [User Experience](), [Bot](), [Chat Bot](), [Language models](), [Open Source]() Tags: [alexa](), [chat](), [code](), [developers](), [experience](), [language-models](), [modular](), [neural](), [scripted]() ### AI overview This article presents research from Stanford's Alexa Prize team on improving user experience and behavior in socialbot conversations. It discusses user dissatisfaction, responses to offensive behavior, and how conversational control can be balanced between users and bots. The Chirpy Cardinal socialbot uses a modular combination of neural generation and scripted dialogue to support broad, open-domain conversations. ### Source excerpt Introduction In 2019, Stanford entered the Alexa Prize Socialbot Grand Challenge 3 for the first time, with its bot Chirpy Cardinal, which went on to win 2nd place in the competition. In our previous post, we discussed the technical structure of our socialbot and how developers can use our open-source code to develop their own. In this post we share further research conducted while developing Chirpy Cardinal to discover common pain points that users encounter when interacting with socialbots, and strategies for addressing them. The Alexa Prize is a unique research setting, as it allows researchers to study how users interact with a bot when doing so solely for their own motivations. During the competition, US-based Alexa users can say the phrase "let's chat" to speak in English to an anonymous and randomly-selected competing bot. They are free to end the conversation at any time. Since Alexa Prize socialbots are intended to create as natural an experience as possible, they should be capable of long, open-domain social conversations with high coverage of topics. We observed that Chirpy users were interested in many different subjects, from current events (e.g., the coronavirus) to pop culture (e.g., the movie Frozen 2) to personal interests (e.g,. their pets). Chirpy achieves its coverage of these diverse topics by using a modular design that combines both neural generation and scripted dialogue, as described in our previous post. We used this setting to study three questions about socialbot conversations: What do users complain about, and how can we learn from the complaints to improve neurally generated dialogue? What strategies are effective and ineffective in handling and deterring offensive user behavior? How can we shift the balance of power, such that both users and the bot are meaningfully controlling the conversation? We've published papers on each of these topics at SIGDIAL 2021 and in this post, we'll share key findings which provide practical insights for ## Latent Effects for Reusable Language Components DevFeed: [Latent Effects for Reusable Language Components]() Original publisher: [Read original article]() Published: 2021-10-14T14:02:48Z Content type: article Language: en Sources: [Lambda the Ultimate]() Topics: [Haskell](), [Programming](), [Development](), [implementation]() Tags: [abstraction](), [deferred](), [effects](), [examples](), [functional](), [haskell](), [modular](), [monad](), [programming-languages](), [semantics](), [theory]() ### AI overview The article discusses latent effects, a generic class of control-flow mechanisms for modular language definitions. It describes how function abstractions, lazy computations, and MetaML-like staging can be expressed and combined, with a full Haskell implementation and examples. ### Source excerpt Latent Effects for Reusable Language Components, by Birthe van den Berg, Tom Schrijvers, Casper Bach Poulsen, Nicolas Wu: The development of programming languages can be quite complicated and costly. Hence, much effort has been devoted to the modular definition of language features that can be reused in various combinations to define new languages and experiment with their semantics. A notable outcome of these efforts is the algebra-based "datatypes "a la carte" (DTC) approach. When combined with algebraic effects, DTC can model a wide range of common language features. Unfortunately, the current state of the art does not cover modular definitions of advanced control-flow mechanisms that defer execution to an appropriate point, such as call-by-name and call-by-need evaluation, as well as (multi-)staging. This paper defines latent effects, a generic class of such control-flow mechanisms. We demonstrate how function abstractions, lazy computations and a MetaML-like staging can all be expressed in a modular fashion using latent effects, and how they can be combined in various ways to obtain complex semantics. We provide a full Haskell implementation of our effects and handlers with a range of examples. Looks like a nice generalization of the basic approach taken by algebraic effects to more subtle contexts. Algebraic effects have been discussed here on LtU many times. I think this description from section 2.3 is a pretty good overview of their approach: LE&H is based on a different, more sophisticated structure than AE&H's free monad. This structure supports non-atomic operations (e.g., function abstraction, thunking, quoting) that contain or delimit computations whose execution may be deferred. Also, the layered handling is different. The idea is still the same, to replace bit by bit the structure of the tree by its meaning. Yet, while AE&H grows the meaning around the shrinking tree, LE&H grows little "pockets of meaning" around the individual nodes remaining in the [Next page]()