# comes Published articles for comes. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Exploring the Craft CMS Console Command Line Interface (CLI) DevFeed: [Exploring the Craft CMS Console Command Line Interface (CLI)]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-02-27T20:49:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Command-line interface](), [Content Management System](), [PHP](), [Code](), [Process]() Tags: [article](), [automated](), [cli](), [cms](), [code](), [comes](), [command-line](), [commands](), [console](), [craft](), [easier](), [insights](), [learn](), [life](), [love](), [make](), [php](), [process](), [save](), [server](), [stop](), [time](), [useful](), [worrying](), [you-ll]() ### AI overview This tutorial explains Craft CMS's console command-line interface and how its commands can handle time-consuming or memory-intensive tasks, automate recurring work, and reduce problems caused by web-request limits such as timeouts. ### Source excerpt Craft CMS comes with many useful commands that can save you time, and make your life easier. In this article, you'll learn how to stop worrying and love the CLI ## Akka workshop at Finn.no DevFeed: [Akka workshop at Finn.no]() Original publisher: [Read original article]() Author: Sjur Millidahl Published: 2017-10-17T06:56:49Z Content type: tutorial Language: en Sources: [Finn.no]() Topics: [Concurrency](), [async](), [distributed-systems](), [Scalability](), [systems]() Tags: [apache-kafka](), [async](), [asynchronous](), [comes](), [concurrency](), [distributed-systems](), [java](), [kafka](), [kotlin](), [scalability](), [workshop]() ### AI overview The article recaps an Akka workshop at FINN.no and explains the Actor Model, in which actors communicate asynchronously through messages. It describes sequential message processing, state, supervision, scalability, reliability, and hands-on exercises with Java and Kotlin branches. ### Source excerpt Akka workshoppers hard at work! In FINN.no we have experience in running distributed systems, and we often rely on asynchronous communication between our applications. Apache Kafka is the work-horse on the house, and it's doing an excellent job for us. But this doesn't mean that we shouldn't learn new things - or look at other solutions. Akka is an implementation of the Actor Model - a concept of concurrent processing first published in 1973. The Actor Model is all about two ideas: Actors and Messages. Actors sending messages A number of Actors communicate to each other using messages. An Actor will process its received messages sequentially, and send messages to other actors asynchronously. It can also keep state, perform side-effects and supervise other actors. This small hand-full of operations makes the Actor Model easy to reason about and within one Actor we need not worry about the complexity of concurrency - one message is processed after another. The power of the Actor Model comes from combining (often specialized) Actors in a supervised hierarchy. Concurrency and scalability comes naturally as the sending of messages between them are asynchronous. Reliability and uptime comes from a let-it-crash philosophy and supervision done through special Supervisor-Actors. Arild wrapping heads around the async monad! The workshop was a hands-on with a few slides between the exercises. You can do the tasks yourself by cloning and checking out the master-branch (for java) or the kotlin-branch. Slides Resources ## ReactOS Newsletter 63: Automated Test Fix and MSVC Compatibility Work DevFeed: [ReactOS Newsletter 63: Automated Test Fix and MSVC Compatibility Work]() Original publisher: [Read original article]() Published: 2009-08-01T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Testing](), [bug](), [MSVC](), [gcc]() Tags: [bug](), [comes](), [free](), [gcc](), [memory](), [msvc](), [open-source](), [os](), [react](), [reactos](), [testing](), [win32](), [winapi]() ### AI overview ReactOS Newsletter 63 reports a fix for an infinite loop in the automated test suite caused by memory corruption in LoadLibraryExW when handling an untrimmed library name. It also describes ongoing fixes for MSVC compilation and syntax issues. ### Source excerpt Test Disruptions For several days the automated testing suite that runs every ReactOS revision got stuck in an infinite loop once it reached the msi_winetest. Several people following the testing noticed this issue and suggested possible causes but Jeffrey Morlan eventually committed a patch that seems to resolve it. The problem appeared to be in the LoadLibraryExW function, in a specific case where the LOAD_LIBRARY_AS_DATAFILE flag was set. The function received as one of its inputs DllName, the name of the library it was being asked to load.