# optional Published articles for optional. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Makera Z1 Desktop CNC Review - Smart milling, 4-th axis module, and 5W laser engraving DevFeed: [Makera Z1 Desktop CNC Review - Smart milling, 4-th axis module, and 5W laser engraving]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-01T10:51:29Z Content type: article Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Tool]() Tags: [camera](), [cnc-router](), [diy](), [dust](), [hardware](), [optional](), [precision](), [review](), [reviews](), [testing](), [video](), [volume]() ### AI overview A review of the Makera Z1 desktop CNC machine, covering its enclosed aluminum construction, 200 x 200 x 100 mm work volume, milling and engraving capabilities, assistive features, specifications, and optional 4th-axis and 5W laser accessories. ### Source excerpt The Makera Z1 Desktop CNC is a desktop CNC machine designed for milling and engraving work that requires precision. The fully enclosed machine features an aluminum structure, offers a 200 x 200 x 100 mm work volume, and is suitable for wood, plastic, acrylic, PCB boards, carbon fiber, as well as non-ferrous metals such as aluminum, brass, and copper. The standout feature of this model is its fairly complete set of assistive functions, including a quick tool change system for swapping milling bits, auto probing & leveling for detecting position and leveling the workpiece, the AeroDust system for blowing and managing chips/dust, and a built-in camera for monitoring operation. In addition, optional accessories such as a 4th-axis rotary module, a 5W laser head, a workholding kit, and a 3D probe can also be installed. This model relies on a linear rail system featuring Acme lead screws and NEMA 17 stepper [...] The post Makera Z1 Desktop CNC Review - Smart milling, 4-th axis module, and 5W laser engraving appeared first on CNX Software - Embedded Systems News. ## Remote Asset Libraries DevFeed: [Remote Asset Libraries]() Original publisher: [Read original article]() Author: Julian Eisel Published: 2026-07-22T12:26:48Z Content type: release Language: en Sources: [Blender]() Topics: [Library](), [Self-hosted](), [Internet]() Tags: [download](), [general-development](), [internet](), [libraries](), [offline](), [optional](), [remote](), [self-hosting]() ### AI overview Blender's Remote Asset Libraries let users browse assets stored on remote servers and download them only when needed. They support optional online content, self-hosting, and offline access after assets are downloaded. ### Source excerpt Browse assets stored online and download them only when needed. ## OpenCL 3.1 is Here DevFeed: [OpenCL 3.1 is Here]() Original publisher: [Read original article]() Author: Khronos Group (webservices@khronosgroup.org) Published: 2026-05-04T07:01:00Z Content type: release Language: en Sources: [Blogs Khronos Blog]() Topics: [cross-platform](), [Compiler](), [Open Source](), [toolchain]() Tags: [2026](), [api](), [blog-openc](), [compilation](), [compiler](), [compilers](), [cross-platform](), [directx](), [embedded](), [enumerate](), [opencl](), [optional](), [source](), [spir](), [vulkan]() ### AI overview The Khronos OpenCL Working Group has released OpenCL 3.1, moving field-proven capabilities into the core specification. The release mandates SPIR-V kernel ingestion for conformant implementations and expands cross-platform availability through a growing implementation, compiler, runtime, and framework ecosystem. ### Source excerpt On the eve of IWOCL 2026, the Khronos® OpenCL Working Group has released OpenCL™ 3.1, bringing widely deployed, field-proven capabilities into the core specification to expand functionality, including SPIR-V ingestion, that developers will be able to rely on across conformant implementations. The new specification arrives into a growing OpenCL ecosystem, with implementations from multiple silicon vendors, particularly in mobile and embedded markets, and higher-level frameworks including SYCL™ and chipStar increasingly targeting OpenCL as an acceleration backend. The open-source compiler and runtime ecosystem around OpenCL also continues to mature with layered implementations of OpenCL over Vulkan and DirectX 12 -- widening OpenCL's cross-platform availability, including on platforms without native drivers. ## Illegal vs Unwanted States DevFeed: [Illegal vs Unwanted States]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2026-04-28T15:14:09Z Content type: article Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [systems](), [Software](), [data](), [Network](), [Server]() Tags: [airline](), [data](), [data-type](), [event](), [network](), [optional](), [servers](), [software](), [state](), [systems]() ### AI overview The article distinguishes illegal states, which a system must never enter, from unwanted states, which may be temporarily acceptable but must not persist or develop into illegal states. It argues that systems should represent unwanted states because external inputs and unreliable infrastructure make them unavoidable, while detection and resolution mechanisms limit their consequences. ### Source excerpt An illegal state is a state we never want our system to be in. An unwanted state is a state we don't want to stay in. Many states that we wish were illegal are actually unwanted. Considering a calendaring software which stores calendar events as {user: {events: [event]}}, where each event has a start and end time. This allows one person to attend two events at the same time. We might consider this illegal and replace the data type with {user: {time: optional event}} which makes this impossible. However, a scheduling conflict isn't illegal, only unwanted! It is possible for a person to sign up for two overlapping events. Maybe they're supposed to choose one event, maybe they'll decide which event to go to later, maybe one of the events doesn't actually represent an in-person meeting. In that case it's acceptable, if not ideal, to remain in the unwanted state. Other unwanted states lead to invalid states if not exited quickly. An airline flight is in an unwanted state if there are more passengers booked to fly than seats available. This must be resolved before passengers actually board, as "more passengers physically on the plane than seats available" is an illegal state. In some cases, an unwanted state does not lead to illegal states, but permanently remaining in the unwanted state is still a problem. We might guarantee that a network partition does not ever lead to inconsistent data. Even though the unwanted state of a network partition cannot cause the illegal state of corrupt data, we still have a big problem if we don't ever fix the partition. Why systems must represent unwanted states Generally, unwanted states can happen if we don't have complete control over our system's behavior. We can't guarantee our network is perfectly reliable, our servers are always up, our users all put in correct data. If our system gets input from the external world then the world can push us into an unwanted state. We need to be able to detect these states so we can resolve them. E ## Migrating to Angular Signals DevFeed: [Migrating to Angular Signals]() Original publisher: [Read original article]() Author: Armen Vardanyan Published: 2025-08-27T10:43:56Z Content type: tutorial Language: en Sources: [Daniel Glejzner]() Topics: [Angular](), [reactive]() Tags: [angular](), [articles](), [optional](), [reactive](), [rxjs](), [state](), [state-management]() ### AI overview This tutorial examines migrating Angular applications to Signals for state management and reactivity. It explains that RxJS is expected to become optional rather than unsupported, while Signals can handle many tasks. ### Source excerpt Today, everyone, everywhere in the Angular community is talking about Signals. They are the new way to manage state and reactivity in Angular applications, promising a better way to build logic and a very much improved change detection. However, many are hesitant. And this is understandable! Not only are signals ## Zed AI: Introducing Usage-Based Billing for High-Volume Users DevFeed: [Zed AI: Introducing Usage-Based Billing for High-Volume Users]() Original publisher: [Read original article]() Author: Nathan Sobo Published: 2024-10-17T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Artificial Intelligence](), [Code](), [issue tracker]() Tags: [account](), [ai](), [cost](), [free](), [issue-tracker](), [optional](), [subscription](), [tokens](), [usage-based-billing](), [volume]() ### AI overview Zed is introducing usage-based billing for high-volume Zed AI users while keeping a free tier for everyone else. Users will be billed at cost for tokens beyond the free tier, with optional subscription billing and monthly spending limits. ### Source excerpt Some billing-related changes for Zed's AI offering ## Overscroll animations in Jetpack Compose DevFeed: [Overscroll animations in Jetpack Compose]() Original publisher: [Read original article]() Author: sinasamaki Published: 2024-07-12T07:11:09Z Content type: tutorial Language: en Sources: [sinasamaki]() Topics: [Jetpack Compose](), [Compose]() Tags: [animation](), [article](), [build](), [code](), [compose](), [events](), [jetpack-compose](), [optional](), [parameter]() ### AI overview This tutorial explains how to create custom overscroll animations in Jetpack Compose using a Modifier and nested scrolling. It develops a bounce effect designed to work with LazyLists and Pagers. ### Source excerpt Add bouncy overscroll animations to all your scrolling elements ## Pattern match Optional in Java 21 DevFeed: [Pattern match Optional in Java 21]() Original publisher: [Read original article]() Author: Stephen Colebourne (noreply@blogger.com) Published: 2024-02-20T09:19:00Z Content type: article Language: en Sources: [Stephen Colebourne]() Topics: [Java](), [Code]() Tags: [code](), [java](), [java21](), [null](), [optional](), [pattern-matching]() ### AI overview This article presents a rarely useful technique for pattern matching an Optional in Java 21 by converting its value with orElse(null) and testing it with instanceof. It discusses functional Optional methods, an iterable helper, limitations in Java 17, and a possible use in long if-else chains. ### Source excerpt I'm going to describe a trick to get pattern patching on Optional in Java 21, but one you'll probably never actually use. Using Optional As of Java 21, Pattern matching in Java allows us to check a value against a type like an instanceof with a new variable being declared of the correct type. Pattern matching can handle simple types and the deconstruction of records. But pattern matching of arbitrary classes like Optional is not yet supported. (Work to support pattern match methods is ongoing). In normal code, the best way to use Optional is with one of the functional methods: var addressOpt = findAddress(personId); var addressStr = addressOpt .map(address -> address.format()) .orElse("No address available"); This works well in most cases. But sometimes you want to use the Optional with a return statement. This results in code using get() like this: var addressOpt = findAddress(personId); if (addressOpt.isPresent()) { // early return if address found return addressOpt.get().format(); } // lots of other code to handle case when address not found One way to improve this is to write a simple method: /** * Converts an optional to an iterable for use in the for-each statement. * * @param <lT> the type of optional element * @param optional the optional * @return an iterable representation of the optional */ public static <lT> Iterable<lT> inOptional(Optional<lT> optional) { return optional.isPresent() ? List.of(optional.get()): List.of(); } Which allows the following neat form: for (var address : inOptional(findAddress(personId))) { // early return if address found return address.format(); } // lots of other code to handle case when address not found This is a great approach providing that you don't need an else branch. Using Optional with Pattern matching With Java 21 and pattern matching we have a new way to do this! if (findAddress(personId).orElse(null) instanceof Address address) { // early return if address found return address.format(); } else { // lots of ## Keep your phone number private with Signal usernames DevFeed: [Keep your phone number private with Signal usernames]() Original publisher: [Read original article]() Published: 2024-02-20T00:00:00Z Content type: release Language: en Sources: [Signal Blog]() Topics: [App]() Tags: [app](), [chat](), [communication](), [features](), [optional](), [privacy]() ### AI overview Signal is introducing privacy features that hide phone numbers from people who do not already have them saved, allow users to initiate contact with optional usernames, and let users control whether they can be found by phone number. The features are initially in beta and require the latest app version. ### Source excerpt Signal's mission and sole focus is private communication. For years, Signal has kept your messages private, your profile information (like your name and profile photo) private, your contacts private, and your groups private - among much else. Now we're taking that one step further, by making your phone number on Signal more private. Here's how: Read more... ## Understanding nullability in GraphQL and Swift with Apollo iOS DevFeed: [Understanding nullability in GraphQL and Swift with Apollo iOS]() Original publisher: [Read original article]() Author: Calvin Cestari Published: 2023-10-03T09:53:34Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Swift](), [Programming]() Tags: [apollo](), [graphql](), [language](), [languages](), [mobile](), [optional](), [swift](), [syntax](), [types]() ### AI overview This tutorial explains how nullability works in GraphQL and Swift, whose default nullability rules differ, and how Apollo iOS maps nullable GraphQL fields into generated Swift models. It also introduces the semantic distinction between GraphQL nullable and optional values. ### Source excerpt Nullability is a fundamental concept in many programming languages giving us the ability to express the absence of a value or assigned object. This is particularly relevant in strongly typed languages where each constant or variable must be defined with one of the language data types or explicitly allowed to be null. GraphQL is strongly-typed and all fields are, by default, nullable with being a valid response for any field unless explicitly declared otherwise. ## KotlinConf'23-Kotlin & Functional Programming: pick the best, skip the rest by Urs Peter DevFeed: [KotlinConf'23-Kotlin & Functional Programming: pick the best, skip the rest by Urs Peter]() Original publisher: [Read original article]() Author: Matthew Dolan Published: 2023-04-14T06:32:47Z Content type: opinion Language: en Sources: [Stories by Matthew Dolan on Medium]() Topics: [Kotlin](), [Functional programming](), [Programming](), [exceptions]() Tags: [android](), [android-app-development](), [arrow](), [data-structures](), [exceptions](), [functional-programming](), [kotlin](), [monad](), [optional](), [programming]() ### AI overview A review of Urs Peter's KotlinConf'23 talk on functional programming, covering monoids, functors, monads, and selective use of the Arrow framework. It highlights using Either for recoverable service errors, nullable comprehensions, and Arrow Optics for nested data updates. ### Source excerpt KotlinConf'23 -- Kotlin & Functional Programming: pick the best, skip the rest by Urs Peterhttps://medium.com/media/b5b95f6bdbb507930534ef8279ba1d05/href I recently had the pleasure of listening to Urs Peter's talk on Kotlin & Functional. The speaker gave a great, simple summary of what a Monad is and how it works. In essence: a Monoid is combinable (plus) and has an identity (empty) element which when combined with another value returns that other value. a Functor is mappable (map) a Monad is composable (flatMap) The talk then went on to discuss some common monads, such as Collections and Optional. The highlight of the talk for me was when the speaker talked about cherry-picking the best features between Kotlin and Monads (using the Arrow framework). Use Monads selectively where needed and useful. Why use a Monad to replace try-catch blocks for the 95% of use cases? Let exceptions bubble up to a GlobalExceptionHandler. For the other 5%, where we're typically recovering in our service, prefer Either over Result as it makes the contract explicit with easy access to the error reply. Prevent tedious null checks with Arrow's nullable{ } comprehension. With deeply nested data structures where you want to change something at the leaf level, use Arrow Optics instead of nested copy calls. While I enjoyed the talk, I would have loved to hear more best features. You can find my thoughts on more KotlinConf'23 talks at KotlinConf'23. Please let me know your thoughts. Join medium to read all of my articles or subscribe for e-mail updates. ## Animating fonts in Jetpack Compose DevFeed: [Animating fonts in Jetpack Compose]() Original publisher: [Read original article]() Author: sinasamaki Published: 2022-11-03T06:32:43Z Content type: tutorial Language: en Sources: [sinasamaki]() Topics: [Jetpack Compose](), [Compose](), [floating-point]() Tags: [animation](), [article](), [behavior](), [code](), [color](), [compose](), [extend](), [floating-point](), [function](), [jetpack](), [jetpack-compose](), [object](), [optional](), [state]() ### AI overview A tutorial on animating between TextStyles in Jetpack Compose. It explains using lerp with a float animation and introduces a helper function that manages animation state and completion callbacks to reduce repetitive code. ### Source excerpt Jetpack compose offers many different animation helper functions. We can easily animate floats, colors, density-pixels, etc. These helper functions are usually called like this: val animatedColor by animateColorAsState( targetValue = color, animationSpec = tween(durationMillis = 300, easing = LinearEasing) ) The animateColorAsState function returns a state object and we can simply listen to ## The Many Different Ways to Fetch Data in jOOQ DevFeed: [The Many Different Ways to Fetch Data in jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-05-19T07:29:09Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [jooq](), [Java](), [SQL]() Tags: [collections](), [collector](), [convenience](), [fetching](), [java](), [jdbc](), [joo-f6a0c60d3d07](), [jooq](), [jooq-in-use](), [optional](), [r2dbc](), [reactive-streams](), [sql](), [stream-api](), [streams]() ### AI overview This tutorial explains several ways to fetch data with jOOQ, including eager result-set fetching, external and internal iteration, single-record retrieval, optional results, and resource-managed fetching for large data sets. ### Source excerpt The jOOQ API is all about convenience, and as such, an important operation (the most important one?) like fetch() must come with convenience, too. The default way to fetch data is this: It fetches the entire result set into memory and closes the underlying JDBC resources eagerly. But what other options do we have? Iterable ... Continue reading The Many Different Ways to Fetch Data in jOOQ -> ## An Approach for Migrating From Objective-C to Swift DevFeed: [An Approach for Migrating From Objective-C to Swift]() Original publisher: [Read original article]() Author: Steve Barnegren Published: 2022-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Steve Barnegren]() Topics: [Objective-C](), [Swift](), [interoperability](), [iOS](), [tvOS](), [generics](), [Code]() Tags: [apple](), [enums](), [generics](), [interoperability](), [ios](), [objective-c](), [optional](), [swift](), [types](), [with]() ### AI overview This article shares lessons from transitioning a large iOS and tvOS application from Objective-C to Swift. It explains why simply adding new Swift code produced limited progress and caused Swift code to be constrained by Objective-C interoperability. ### Source excerpt It feels like Swift is pretty ubiquitous across the Apple ecosystem now, but there's a lot of Objective-C out there. The larger and older the app, the more likely that there's still a bunch of Objective-C powering various bits behind the scenes. ## Nulls and Null Safety DevFeed: [Nulls and Null Safety]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2021-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Kotlin](), [Jetpack Compose]() Tags: [elvis-operator](), [introduction](), [kotlin](), [learn-to-program](), [not-null-assertion-operator](), [null](), [null-safety](), [optional](), [programming](), [safe-call-operator](), [smart-cast]() ### AI overview An introduction to nulls and null safety in Kotlin, explaining that variables may not always hold a value and setting up a coffee-rating example implemented in Kotlin. ### Source excerpt So far in this book, every time that we created a variable, whether it was a String, an Int, or a Boolean, we assigned a value to it. There are times, though, when we need to create a variable that might not actually hold a value! This brings us to the exciting topic of nulls! Introduction to Nulls James has set up a coffee stand downtown, and he's ready to start sharing his fine brew! ## Ethereum Berlin Upgrade Announcement DevFeed: [Ethereum Berlin Upgrade Announcement]() Original publisher: [Read original article]() Author: Tim Beiko Published: 2021-03-08T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Network](), [bug]() Tags: [announcement](), [bug](), [deprecated](), [fork](), [network](), [node](), [optional](), [protocol-announcements](), [release](), [release-schedule](), [upgrade]() ### AI overview Ethereum's Berlin upgrade is scheduled for deployment on testnets beginning with Ropsten on March 10, 2021, and on mainnet around April 15, 2021. The article lists compatible client versions, upgrade guidance for node operators, and the EIPs included in Berlin. ### Source excerpt TL;DR Berlin is ready to be deployed! We're moving fast: the first testnet to upgrade, Ropsten, is scheduled to upgrade on March 10th. Mainnet is scheduled for April 15th. If you are running an Ethereum node, you should upgrade it to a Berlin-compatible version ASAP for testnets and before... ## Optional dependencies are not optional DevFeed: [Optional dependencies are not optional]() Original publisher: [Read original article]() Author: Cédric Champeau Published: 2020-01-07T05:00:00Z Content type: tutorial Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Maven](), [Library](), [Cryptography](), [Logging]() Tags: [blog](), [blog-post](), [cryptography](), [dependencies](), [gradle](), [library](), [optional]() ### AI overview The article explains that so-called optional dependencies are actually required when a specific library feature is used. Using Gradle, Apache Maven, Apache PDFBox, and BouncyCastle as examples, it describes how optional dependencies are omitted during transitive dependency resolution, leaving consumers to determine and add the required components manually. It introduces feature-based dependency modeling as a clearer approach. ### Source excerpt In a previous blog post, we demonstrated how capabilities could be used to elegantly solve the problem of having multiple logging frameworks on the classpath. In this post, we will again use this concept in a different context: optional dependencies. At Gradle, we often say that there are no optional dependencies: there are dependencies which are required if you use a specific feature. Let's explain why. Optional dependencies Until recently, Gradle didn't offer any way to publish optional dependencies, which is something which puzzled a number of Apache Maven™ users. To understand in what context optional dependencies are used, let's look at a real world project. The Apache PDFBox library declares the following optional dependencies in its POM file: org.bouncycastle bcmail-jdk15on true org.bouncycastle bcprov-jdk15on true Those are 2 dependencies on a specific component, the BouncyCastle cryptography library. Now let's imagine your project depends on PDFBox, either using Gradle: dependencies { implementation("org.apache.pdfbox:pdfbox:2.0.17") } or using Apache Maven™: org.apache.pdfbox pdfbox 2.0.17 Now if you look at the dependencies that both Maven and Gradle resolve, you will see that the Bouncycastle library is absent. This is because it's defined as an optional dependency. There are multiple problems with optional dependencies as they are defined today: Library authors know why a dependency is optional, but consumers don't: how do you know when you should add bcprov-jdk15on? Optional dependencies are mixed up: how do you know when to add bcprov-jdk15on and if bcmail-jdk15on should be added as well? Optional dependencies are ignored ## Data classes aren't (that) magical DevFeed: [Data classes aren't (that) magical]() Original publisher: [Read original article]() Author: Márton Braun Published: 2019-01-16T16:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Kotlin](), [Code](), [Java]() Tags: [android](), [classes](), [constructor](), [create](), [data-class](), [destructuring](), [generate](), [kotlin](), [marton-braun](), [optional](), [parameter](), [properties](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview This tutorial explains what Kotlin data classes add to regular classes. It covers generated methods, how primary-constructor properties affect those methods, destructuring support, and the copy method with optional named parameters. ### Source excerpt Data classes are great, but don't underestimate what a regular Kotlin class can do on its own. ## Intentional Optionality DevFeed: [Intentional Optionality]() Original publisher: [Read original article]() Author: Steve Barnegren Published: 2018-09-13T00:00:00Z Content type: tutorial Language: en Sources: [Steve Barnegren]() Topics: [Swift](), [Code]() Tags: [code](), [guards](), [let](), [optional](), [swift]() ### AI overview A Swift article examines intentional use of optionality. It argues that while non-optional types are usually preferable, optional values can sometimes make code easier to read and understand, including when handling leaderboard entries and conditional menu items. ### Source excerpt When I first started writing Swift, I felt like Optionals were a constant pain point. Everything seemed to end up being Optional, resulting in me littering if lets and guards around my code, and generally just making a horrible mess of things. ## Clean code with Java 9 at GeeCON DevFeed: [Clean code with Java 9 at GeeCON]() Original publisher: [Read original article]() Published: 2018-05-17T20:05:44Z Content type: opinion Language: en Sources: [Miro Cupak]() Topics: [Java](), [Code](), [HTTP]() Tags: [clean-code](), [conference](), [geecon](), [interfaces](), [java](), [java-9](), [jvm](), [new-features](), [optional](), [speaking](), [talk]() ### AI overview A personal report from GeeCON describes a live demo on writing cleaner code with Java 9. The talk covers JShell and several JDK 9 features, including collection factory methods, private interface methods, Stream API enhancements, Optional updates, StackWalker, and an HTTP/2 client. ### Source excerpt Last week, I was fortunate enough to attend GeeCON. GeeCON is a well-known conference in the JVM world and this year marked its 10th anniversary. More than 1200 people came to see over 80 sessions from more than 70 speakers distributed across 4 tracks over 3 days in Krakow, Poland. This was my first time attending GeeCON. In retrospect,... ## Read receipts are coming to Signal DevFeed: [Read receipts are coming to Signal]() Original publisher: [Read original article]() Published: 2017-10-03T00:00:00Z Content type: release Language: en Sources: [Signal Blog]() Topics: [Messaging](), [Android](), [iOS](), [Beta channel](), [Google Play]() Tags: [android](), [beta-channel](), [communication](), [feature](), [ios](), [new-feature](), [optional](), [release]() ### AI overview Signal's beta release for Android and iOS adds optional read receipts. Users can enable or disable them, and both participants must have the feature enabled to see each other's receipts. The feature is enabled for new installations but disabled by default for existing installations. ### Source excerpt Today's beta release of Signal for Android and iOS includes support for read receipts. This is an optional new feature that gives you the ability to see and share when messages have been read. Something tells us that you might find this useful... Read more... ## Java Optionals and Kotlin Nulls DevFeed: [Java Optionals and Kotlin Nulls]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2017-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Java](), [Kotlin]() Tags: [exception](), [extension-function](), [filter](), [java](), [java-8](), [kotlin](), [migration-guide](), [null](), [null-safety](), [optional](), [programming](), [safe-call-operator](), [standard-library](), [transformation]() ### AI overview A guide to translating Java Optional usage into idiomatic Kotlin null-safety patterns. It compares creation, transformation, filtering, and conditional operations, while noting trade-offs and cases where Kotlin nullable types replace Optional. ### Source excerpt When Java 8 introduced Streams for operating on collections of data, it also introduced a similar concept, Optional, which has many methods that are similar to Stream, but operates on a single value that might or might not be present. As you migrate your projects from Java to Kotlin, you might come across some Optional objects. What should you do? Should you leave them as Optional, or change them to more idiomatic Kotlin? ## Maintaining a Swift and Objective-C Hybrid Codebase DevFeed: [Maintaining a Swift and Objective-C Hybrid Codebase]() Original publisher: [Read original article]() Author: Adrianna Chang Published: 2017-06-15T18:13:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Swift](), [Objective-C](), [interoperability](), [iOS](), [Code](), [WebKit]() Tags: [architecture](), [bridging](), [c](), [crash](), [ios](), [null](), [optional](), [pointers](), [swift]() ### AI overview This article explains how to maintain a hybrid Swift and Objective-C codebase when adding new Swift code to an existing actively supported Objective-C project. It discusses interoperability between the two languages and the importance of correct nullability annotations for preserving Swift's compile-time optionality guarantees and avoiding runtime crashes. ### Source excerpt 6 minute read Swift is gaining popularity among iOS developers, which is of no surprise. It's strictly typed, which means you can prove the correctness of your program at compile time, given that your typesystem describes the domain well. It's a modern language offering syntax constructs encouraging developers to write better architecture using fewer lines of code, making it expressive. It's more fun to work with, and all the new Cocoa projects are being written in Swift. At Shopify, we want to adopt Swift where it makes sense, while understanding that many existing projects have an extensive codebase (some of them written years ago) in Objective-C (OBJC) that are still actively supported. It's tempting to write new code in Swift, but we can't migrate all the existing OBJC codebase quickly. And sometimes it just isn't worth the effort. ## An Optional's place in Kotlin DevFeed: [An Optional's place in Kotlin]() Original publisher: [Read original article]() Author: Jake Wharton Published: 2017-05-14T16:18:21Z Content type: article Language: en Sources: [Jake Wharton](), [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Kotlin](), [Java](), [Open Source]() Tags: [engineering](), [java](), [kotlin](), [open-source](), [optional](), [releases](), [serialization]() ### AI overview Kotlin's nullability support does not eliminate every use for Optional. Because RxJava 2 streams do not allow null values, Retrofit 2.3.0 adds converters that wrap potentially null deserialization results in Optional-like types from Guava and Java 8. ### Source excerpt With nullability being a first-class citizen in Kotlin's type system, is there any need for an Optional type? [Next page]()