# immutability Published articles for immutability. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Value Classes Still Need Compiler Sympathy DevFeed: [Value Classes Still Need Compiler Sympathy]() Original publisher: [Read original article]() Author: Johan Sjölén Published: 2026-08-24T00:00:00Z Content type: article Language: en Sources: [Inside Java]() Topics: [JDK 28](), [Optimization](), [Compiler]() Tags: [compiler](), [immutability](), [jdk-28](), [jep-401](), [jvm](), [openjdk](), [optimization](), [payload](), [profiling](), [project-valhalla](), [valhalla]() ### AI overview This article examines value classes as a preview feature in JDK 28 and explains how giving up object identity can enable JVM optimizations such as flattening and scalarization. It also describes limitations caused by representation changes, abstraction boundaries, mutability, and generic virtual calls. ### Source excerpt Declaring a value class is first and foremost a semantic decision. It tells our fellow programmers that its instances are defined entirely by their state and do not need identity. That clearer model is valuable in itself! The JVM's additional freedom to optimize how those values are represented is a welcome bonus. C2 can do amazing things with that freedom, but it cannot always recover information hidden behind abstraction boundaries. Profiling and inspecting the generated code remain the best ways to understand what is happening. To get the best results, we may still need to have a little sympathy for the compiler. ## Immutability in PHP Beyond readonly DevFeed: [Immutability in PHP Beyond readonly]() Original publisher: [Read original article]() Author: Freek Van der Herten (freek@spatie.be) Published: 2026-08-17T12:12:30Z Content type: article Language: en Sources: [freek.dev - all blogposts]() Topics: [PHP]() Tags: [best-practices](), [deep-dive](), [design-patterns](), [immutability](), [php](), [properties](), [value](), [value-objects]() ### AI overview A deep dive into immutability in PHP, covering readonly properties, interior mutability, immutable value objects and collections, dates, cloning, boundaries, and testing. ### Source excerpt A deep dive into immutability in PHP, from readonly properties and interior mutability to immutable value objects, collections, dates, cloning, boundaries, and testing. Read more ## Changing Immutable Collections DevFeed: [Changing Immutable Collections]() Original publisher: [Read original article]() Author: jonskeet Published: 2025-12-31T10:32:45Z Content type: article Language: en Sources: [Jon Skeet]() Topics: [C#](), [Code]() Tags: [array](), [arrays](), [blog](), [blog-post](), [c-sharp](), [collection](), [election-2029](), [immutability](), [linq](), [migration](), [properties]() ### AI overview The article explains a migration from ImmutableList and ImmutableDictionary to immutable collection types better suited to code that creates collections and then leaves them unchanged. It describes the migration steps and related helper-method and property-type changes. ### Source excerpt As I've written before, I'm leaning heavily into immutability in the election site code. Until September 2025 (it's taken a long time to get round to writing this blog post) that meant a combination of records, ImmutableList and ImmutableDictionary. In an ECMA C# standards meeting, however, Joseph Musser passed on some really valuable feedback ... Continue reading Changing Immutable Collections -> ## The principle of immutability DevFeed: [The principle of immutability]() Original publisher: [Read original article]() Published: 2024-08-20T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Programming](), [Rust](), [Functional programming](), [C++](), [Programming language]() Tags: [c-plus-plus](), [functional-programming](), [immutability](), [rust](), [secure-by-default](), [secure-by-design]() ### AI overview The article argues that immutability is about intentionally controlling change rather than preventing change. It presents immutability by default as part of secure-by-design software and compares approaches in functional programming, C++, and Rust. ### Source excerpt Secure by default starts with immutability. Discover how to control change and minimize risks. ## Best practices for patching and deprecating Docker images DevFeed: [Best practices for patching and deprecating Docker images]() Original publisher: [Read original article]() Author: Tom Published: 2024-02-09T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [Docker Image](), [Security](), [DevOps]() Tags: [best-practices](), [devops](), [devops-docker-management](), [docker](), [docker-image](), [docker-image-deprecation](), [docker-image-maintenance](), [docker-image-patching](), [docker-security-best-practices](), [docker-update-strategies](), [how-to](), [immutability](), [linux](), [security]() ### AI overview This article presents practices for maintaining Docker images securely and predictably. It recommends deprecating images before deleting them, notifying users of upcoming breaking changes, upgrading base images quarterly, and pinning versions to keep rebuilds stable. ### Source excerpt Learn the best practices for patching and deprecating Docker images to maintain security and stability in your DevOps workflows. ## Oxidizing OCaml: Rust-Style Ownership DevFeed: [Oxidizing OCaml: Rust-Style Ownership]() Original publisher: [Read original article]() Author: Max Slater Published: 2023-06-21T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [OCaml](), [Rust](), [Concurrency]() Tags: [concurrency](), [functional](), [immutability](), [ocaml](), [rust]() ### AI overview This article examines ownership modes in OCaml with Jane Street extensions. It explains how unique references can allow in-place updates while preserving an immutable interface, and discusses how uniqueness may support static prevention of data races in multicore OCaml. ### Source excerpt OCaml with Jane Street extensions is available from our public opam repo. Only a slice of the features described in this series are currently implemented. ## Platonic C# - Managing Referential Transparency through Unique Types DevFeed: [Platonic C# - Managing Referential Transparency through Unique Types]() Original publisher: [Read original article]() Published: 2023-03-04T20:11:56Z Content type: opinion Language: en Sources: [Lambda the Ultimate]() Topics: [C#](), [Data structures](), [context]() Tags: [c-sharp](), [context](), [data-structures](), [immutability](), [object-functional]() ### AI overview The article proposes Platonic C# as a set of rules intended to enforce referential transparency by defaulting to immutable data structures and requiring unique instances of mutable types. ### Source excerpt The idea of Platonic C# is to enforce referential transparency within the context of C#, by enforcing a set of rules around defaulting to immutability of data structures and requiring uniqueness of instances of mutable types. ## A birds-eye view of Arrow: Data Immutability with Arrow Optics DevFeed: [A birds-eye view of Arrow: Data Immutability with Arrow Optics]() Original publisher: [Read original article]() Published: 2022-12-19T00:15:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Functional programming](), [Kotlin](), [Programming](), [API](), [Code]() Tags: [arrow](), [code](), [functional-programming](), [immutability](), [kotlin](), [ksp](), [lens](), [workshop-learning-programming]() ### AI overview This tutorial introduces Arrow Optics for transforming nested immutable data in Kotlin. It explains how Arrow Optics uses a basic library and a compiler plug-in built with Kotlin Symbol Processing, with annotations generating lenses that combine getters and setters. ### Source excerpt Learn to use Arrow Optics to support working on immutable objects. ## Object-oriented or functional? Two ways to see the world DevFeed: [Object-oriented or functional? Two ways to see the world]() Original publisher: [Read original article]() Published: 2022-08-18T00:00:00Z Content type: opinion Language: en Sources: [Kt. Academy]() Topics: [Functional programming](), [Object-oriented programming (OOP)](), [Programming]() Tags: [fp](), [functional](), [immutability](), [inheritance](), [object-oriented](), [oop](), [polymorphism](), [recursion](), [workshop-learning-programming]() ### AI overview This opinion article compares object-oriented programming and functional programming as ways of thinking about program design, rather than merely collections of features. It uses different ways of viewing a bedroom--as objects or actions--to illustrate the distinction while acknowledging that modern languages commonly support both styles. ### Source excerpt The difference between the OOP and FP paradigms is deeply rooted in how we see the world. A few words on the philosophy of both approaches. ## Apollo Kotlin: New Multiplatform Memory Manager DevFeed: [Apollo Kotlin: New Multiplatform Memory Manager]() Original publisher: [Read original article]() Author: Benoit Lubek Published: 2022-08-09T12:05:22Z Content type: news Language: en Sources: [Apollo Blog]() Topics: [Kotlin Multiplatform](), [kotlin-multiplatform-libraries](), [Concurrency]() Tags: [apollo](), [concurrency](), [immutability](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [library](), [mobile](), [multiplatform](), [multithreading](), [performance](), [unit-tests]() ### AI overview Apollo Kotlin 3.5.0 adopts Kotlin Native's new memory manager. The change removes several threading and immutability restrictions, including the requirement to access the library exclusively from the Main thread on Apple targets. Initial benchmarks indicate performance improvements of up to 45%. ### Source excerpt Back in May, we shared about how Apollo Kotlin started supporting the Hierarchical project structure. Following the Kotlin Multiplatform ecosystem, here is some more news, this time about the new Memory Manager. Kotlin Native's Memory Manager Since its early days, Kotlin Native has had specific rules regarding multithreading and immutability: - objects could only be accessed from the thread they were created in - unless they had been "frozen", in which case they could be accessed by multiple... ## Data is immutable DevFeed: [Data is immutable]() Original publisher: [Read original article]() Author: Yehonathan Sharvit Published: 2022-06-22T02:34:24Z Content type: article Language: en Sources: [Klipse]() Topics: [data](), [Programming](), [Data structures](), [Clojure](), [JavaScript]() Tags: [clojure](), [d](), [data](), [dop](), [immutability](), [javascript](), [mutation]() ### AI overview This article explains the third principle of Data-Oriented Programming: data is immutable. It describes replacing mutation with new data versions, contrasts this approach in Clojure and JavaScript, and discusses cloning and persistent data structures as implementation strategies. ### Source excerpt With data separated from code and represented with generic data structures, how are changes to the data managed? DOP is very strict on this question. Mutation of data is not allowed! In DOP, changes to data are accomplished by creating new versions of the data. The reference to a variable may be changed so that it refers to a new version of the data, but the value of the data itself must never change. ## Represent data with generic data structures DevFeed: [Represent data with generic data structures]() Original publisher: [Read original article]() Author: Yehonathan Sharvit Published: 2022-06-22T02:33:24Z Content type: article Language: en Sources: [Klipse]() Topics: [Data structures](), [Code](), [Programming](), [Object-oriented programming (OOP)](), [JavaScript]() Tags: [array](), [arrays](), [code](), [d](), [data-structures](), [dop](), [immutability](), [javascript](), [oop](), [programming]() ### AI overview This article explores the second principle of Data-Oriented Programming: representing application data with generic data structures such as maps and arrays instead of specific classes. It also discusses other structures, including sets, trees, and queues, and describes benefits such as reusable generic functions and a flexible data model. ### Source excerpt When adhering to Principle #1 of DOP, code is separated from data. DOP is not opinionated about the programming constructs to use for organizing the code, but it has a lot to say about how the data should be represented. This is the theme of Principle #2. ## Immutability we can afford DevFeed: [Immutability we can afford]() Original publisher: [Read original article]() Author: Roman Elizarov Published: 2020-07-22T09:18:28Z Content type: opinion Language: en Sources: [Stories by Roman Elizarov on Medium]() Topics: [Software Engineering](), [Programming](), [Software](), [ui](), [Caching]() Tags: [architecture](), [asynchronous](), [caching](), [code](), [debugging](), [immutability](), [languages](), [object](), [programming](), [programming-languages](), [software-engineering](), [state](), [ui]() ### AI overview The article traces the shift from mutable global state and object-encapsulated state toward immutability. It argues that mutable state becomes difficult to reason about in user interfaces and asynchronous systems, where unexpected mutations complicate debugging, event processing, and caching. ### Source excerpt Photo by Li Yang on Unsplash At the dawn of software engineering computers were programmed directly in machine code, then in assembly, and only later in higher-level languages. Computers are imperative. They operate by executing instructions that mutate their state, stored in registers and memory. Naturally, the same was true about programming languages. In the old world of expensive computers with limited resources, the primary concern was an efficient translation of higher-level abstractions into low-level code. The past glory of mutable state It used to be a normal practice to write software in a way that mimics the actual computer architecture with thousands of global variables that are being mutated by various pieces of the system. It might be shocking for a modern developer to learn that just recently there were cars on the street, designed as late as 2005, that ran what we would call the "Spaghetti" code. The software industry, in general, had firmly moved past the unruly global state before the end of the last century. The rise of the object-oriented programming paradigm had established an orderly approach with the encapsulation of all the mutable state in our software systems inside of objects. It had fueled tremendous growth in the complexity of modern software, layering abstractions above abstractions, while still maintaining a reasonable degree of human's ability to make sense of it. However, any developer who worked on a non-trivial piece of UI using an object-oriented framework, or had programmed in another domain with lots of asynchronously occurring events, can tell you stories of debugging all those cases where mutable state, even encapsulated into objects, continually trips you. You expect this object to be in a such and such state, but due to some rare sequence of events, it turns out to be in a state you did not expect, having been mutated by another piece of code. For example, take a popular architectural pattern where a repository class encapsu ## \[Перевод\] Архитектурный шаблон MVI в Kotlin Multiplatform, часть 1 DevFeed: [\[Перевод\] Архитектурный шаблон MVI в Kotlin Multiplatform, часть 1]() Original publisher: [Read original article]() Author: arkivanov (Badoo) Published: 2020-05-14T14:01:02Z Content type: tutorial Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [Kotlin Multiplatform](), [multiplatform](), [Kotlin](), [Android](), [iOS]() Tags: [android](), [architecture](), [concurrency](), [cross-platform](), [immutability](), [ios](), [kotlin](), [kotlin-multiplatform](), [kotlin-native](), [model-view-intent](), [mpp](), [multiplatform](), [mvi](), [mvvm](), [reactive]() ### AI overview This first article in a three-part series describes using the MVI architectural pattern with Kotlin Multiplatform. It introduces a shared module intended for integration with iOS and Android applications and discusses related testing topics. The author argues that MVI is a better fit for Kotlin Multiplatform than MVVM or an added clean-architecture layer, while noting that the article does not teach Kotlin Multiplatform fundamentals or project setup. ### Source excerpt Около года назад я заинтересовался новой технологией Kotlin Multiplatform. Она позволяет писать общий код и компилировать его под разные платформы, имея при этом доступ к их API. С тех пор я активно экспериментирую в этой области и продвигаю этот инструмент в нашей компании. Одним из результатов, например, является наша библиотека Reaktive -- Reactive Extensions для Kotlin Multiplatform. В приложениях Badoo и Bumble для разработки под Android мы используем архитектурный шаблон MVI (подробнее о нашей архитектуре читайте в статье Zsolt Kocsi: "Современная MVI-архитектура на базе Kotlin"). Работая над различными проектами, я стал большим поклонником этого подхода. Конечно, я не мог упустить возможность попробовать MVI и в Kotlin Multiplatform. Тем более случай был подходящий: нам нужно было написать примеры для библиотеки Reaktive. После этих моих экспериментов я был вдохновлён MVI ещё больше. Я всегда обращаю внимание на то, как разработчики используют Kotlin Multiplatform и как они выстраивают архитектуру подобных проектов. По моим наблюдениям, среднестатистический разработчик Kotlin Multiplatform -- это на самом деле Android-разработчик, который в своей работе использует шаблон MVVM просто потому, что так привык. Некоторые дополнительно применяют "чистую архитектуру". Однако, на мой взгляд, для Kotlin Multiplatform лучше всего подходит именно MVI, а "чистая архитектура" является ненужным усложнением. Поэтому я решил написать эту серию из трёх статей на следующие темы: Краткое описание шаблона MVI, постановка задачи и создание общего модуля с использованием Kotlin Multiplatform. Интеграция общего модуля в iOS- и Android-приложения. Модульное и интеграционное тестирование. Ниже -- первая статья серии. Она будет интересна всем, кто уже использует или только планирует использовать Kotlin Multiplatform. ## Useful Kotlin Features Compared with Java DevFeed: [Useful Kotlin Features Compared with Java]() Original publisher: [Read original article]() Published: 2020-05-03T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Kotlin](), [Java](), [Development](), [Android]() Tags: [classes](), [hashcode](), [immutability](), [java](), [kotlin](), [modifiers](), [package-private](), [process](), [smart-cast](), [visibility]() ### AI overview This article compares Kotlin with Java through several less-discussed language differences. The supplied text covers immutable method-parameter references in Kotlin and contrasts Java visibility modifiers, including protected and package-private access. ### Source excerpt Source Introduction Many of us first learned Kotlin after Java. Learning process was fairly simple because Kotlin has many similarities when at the same time improves development experience by fighting common pain points Java developer (especially on Java 6, which is common in Android world) has to encounter every day. There are a bunch of articles about cool Kotlin features like immutability, handling nullability, smart-cast, data classes, and so forth. Yes, these features are great. Having to add a bunch of nullability annotations, final keywords, override equals/hashCode methods, create additional local variables after type checks -- all of this adds unnecessary work that needs to be done all the time. ## Using Rust Playground for Hello World and Variable Interpolation DevFeed: [Using Rust Playground for Hello World and Variable Interpolation]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-02T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rust](), [Code](), [compiled language](), [Repl.it](), [browser]() Tags: [browser](), [code](), [compiled-language](), [experiment](), [function](), [immutability](), [language](), [let](), [playground](), [program](), [run](), [rust](), [variables]() ### AI overview A beginner-oriented walkthrough of using Rust Playground to run a Hello World program and experiment with variables. It explains Rust syntax such as fn, println!, let, and string interpolation, and briefly compares Rust Playground with Repl.it, including a criticism of Repl.it's paid privacy option. ### Source excerpt Artwork by my friend Autumn Mott; Hopefully I can find a better link to put here It is a Monday and what better way to start your 6 am Monday morning then learning some of the elements of a new language - Rust. I started by adding a link in my Browser toolbar to the Rust Playground which amounts to a web based REPL (Read Evaluate Print Loop) for Rust where you can type in Rust code and run it. Yes I know it really isn't a REPL because Rust is a compiled language not an interpreted one but it functions well enough as a REPL that I can wrap my Ruby tinged mind around it. Here's the Hello World program that automatically appears in the Rust playground fn main() { println!("Hello, world!"); } The output of this is: Hello, world! That's pretty easy to understand: A main function defined with fn A print line function defined with a ! (my previous Rust reading tells me that's a macro indicator) { and } to denote structure A ; to denote the end of lines I wanted to make a simple change to experiment with the use of variables so I added a main2() function and called it from main(): fn main() { println!("Hello, world!"); main2(); } fn main2() { let x = 5; println!("The value of x is: {}", x); let y = 6; println!("The value of y is: {}", y); } The output of this is: Hello, world! The value of x is: 5 The value of y is: 6 You can see that the let keyword assigns a variable and that {} binds a variable into a string (which is generally called interpolation). Note: Variables quickly bring you in to the heart of Rust - immutability - and here there by dragons that hopefully come up tomorrow after some reading. Link Here's a permanent link to this if you want to try it out. What about Repl.it? Another way to have a web based REPL for Rust is Repl.it. And while I like the concept of repl.it, they have eliminated any privacy without a paid account: Upgrade your account for private repls. This appears on the bottom of every new REPL you create and at $74 / 12 months that feels expensi ## On let vs const DevFeed: [On let vs const]() Original publisher: [Read original article]() Published: 2019-12-22T00:00:00Z Content type: opinion Language: en Sources: [Dan Abramov]() Topics: [JavaScript](), [Code](), [React Hooks]() Tags: [eslint](), [immutability](), [javascript](), [mutation](), [react](), [react-hooks]() ### AI overview This article examines the debate over using JavaScript let versus const. It summarizes arguments about reducing reassignment-related bugs, teaching mutation and assignment distinctions, React Hooks data flow, performance claims, and preserving intent, then presents the author's personal conclusion. ### Source excerpt So which one should I use? ## What's new in Apollo Client 2.6 DevFeed: [What's new in Apollo Client 2.6]() Original publisher: [Read original article]() Author: Ben Newman Published: 2019-06-11T22:01:40Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [apollo-client](), [Cache](), [Caching](), [Optimization](), [React]() Tags: [announcement](), [apollo-client](), [cache](), [immutability](), [optimization](), [react](), [snapshots]() ### AI overview Apollo Client 2.6 is a backwards-compatible update that fixes bugs and adds options intended to improve component rendering performance. The article explains how immutable cache results, configurable cache normalization, cache eviction and garbage collection, async iterators, and smaller bundle sizes support the next major version's goals. ### Source excerpt Apollo Client 2.6 is a backwards-compatible update that fixes bugs and provides new options (namely, , , and ) for rendering components faster and more smoothly. These changes lay the groundwork for the next major version of Apollo Client, whose interrelated goals and guiding principles we think you will find both compelling and worth understanding: - 🔏 Immutability of cache results, enabling equality where possible - 🔂 Selective, configurable cache normalization - ♻ Cache eviction,... ## Kotlin first impressions DevFeed: [Kotlin first impressions]() Original publisher: [Read original article]() Published: 2017-11-29T00:00:00Z Content type: opinion Language: en Sources: [Paweł Chudzik]() Topics: [Kotlin](), [Development](), [Java](), [Gradle](), [Hibernate]() Tags: [development](), [gradle](), [hibernate](), [immutability](), [java](), [kotlin]() ### AI overview A developer shares first impressions from using Kotlin on an actively developed project. The article discusses Kotlin's default immutability, extension methods, interoperability with Java, integration with Spring and Hibernate, Gradle build scripts, named parameters, and compile-time null checks. ### Source excerpt Recently while starting work on a project we've (team of two ;)) decided to try something new and use Kotlin. The project is far from ready and still under active development, but after writing some code in Kotlin I've got few observations I'd like to share. Read more ## Immutability in angular DevFeed: [Immutability in angular]() Original publisher: [Read original article]() Published: 2017-07-11T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Angular](), [Data structures](), [Front end](), [Code](), [ui](), [Graphs]() Tags: [angular](), [asynchronous](), [data-structure](), [frontend](), [http](), [immutability](), [ui]() ### AI overview This article explains an immutable, Redux-inspired approach to managing complex hierarchical state in Angular. It recommends recalculating possible values from scratch after user changes, including when asynchronous backend requests and multiple UI components are involved, and presents a simpler categories-and-tags example. ### Source excerpt Some time ago I've been struggling with mapping hierarchical data structure in angular. Labels hierarchy was complex (like 4 levels deep with multiple parents, multiple children, basically graph like structure with some logic behind it). In the end it was/is still working but that's the best I can say about it. Read more ## Immutable dto in jackson DevFeed: [Immutable dto in jackson]() Original publisher: [Read original article]() Published: 2017-04-15T00:00:00Z Content type: tutorial Language: en Sources: [Paweł Chudzik]() Topics: [Jackson](), [JSON](), [Programming](), [Code]() Tags: [code](), [constructor](), [functional-programming](), [how-to](), [immutability](), [jackson](), [json]() ### AI overview This tutorial explains how Jackson 2.7 can deserialize immutable Java DTOs from JSON by using constructor-based object creation and @ConstructorProperties. It also describes using Lombok's @RequiredArgsConstructor to generate the required constructor metadata. ### Source excerpt Immutability and functional programming are hot right now. But how to achieve immutability with objects deserialized from json? Luckily there is pretty old feature introduced in jackson 2.7.0 which uses constructor based object creation and uses @ConstructorProperties (introduced in java7). Read more ## Ethereum Dev Roundup: Q1 DevFeed: [Ethereum Dev Roundup: Q1]() Original publisher: [Read original article]() Author: Vitalik Buterin Published: 2017-04-01T02:55:28Z Content type: opinion Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Algorithms](), [Formal verification](), [zero-knowledge]() Tags: [algorithms](), [attacks](), [consensus](), [dev](), [ethereum](), [formal-verification](), [immutability](), [implementation](), [metropolis](), [privacy](), [proof-of-authority](), [protocol](), [research](), [research-development](), [state](), [verification](), [zero-knowledge]() ### AI overview An Ethereum development roundup discusses research progress in consensus algorithms, privacy, zero-knowledge proofs, and formal verification, alongside proposed changes involving proof of authority, transaction reversion, Metropolis, and protocol rules. ### Source excerpt The last one and a half months have seen great progress for Ethereum research, and we are excited that the protocol is moving closer and closer to the point where it is ready for mainstream adoption. Progress on consensus algorithms, privacy, zero knowledge proofs and formal verification is happening at... ## Kotlin Data Classes Reduce Boilerplate Code DevFeed: [Kotlin Data Classes Reduce Boilerplate Code]() Original publisher: [Read original article]() Published: 2017-01-25T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Kotlin](), [Boilerplate](), [Code](), [Java]() Tags: [class](), [classes](), [code](), [constructor](), [copy](), [data-class](), [destructuring](), [function](), [generate](), [immutability](), [java](), [kotlin](), [properties]() ### AI overview This tutorial explains Kotlin data classes, which represent state and automatically provide useful generated code. It covers destructuring, immutable-object copying, and how data classes reduce boilerplate compared with Java. ### Source excerpt Everything Android, Kotlin and other random topics ## Reactive Apps with Model-View-Intent - Part 2: View and Intent DevFeed: [Reactive Apps with Model-View-Intent - Part 2: View and Intent]() Original publisher: [Read original article]() Author: Hannes Dorfmann Published: 2017-01-17T09:00:00Z Content type: article Language: en Sources: [Hannes Dorfmann]() Topics: [reactive](), [Development](), [Mobile](), [JavaScript]() Tags: [code](), [immutability](), [javascript](), [mvi](), [reactive](), [ui]() ### AI overview This second-part article introduces the Model-View-Intent pattern for building reactive Android applications. It explains how user intents produce model changes, how business logic returns a new immutable model, and how the view renders that model. ### Source excerpt In the first part we have discussed what a Model actually is, the relation to State and how a well defined Model can solve some common issues in android development. In this blog post we continue our journey towards "Reactive Apps" by introducing the Model-View-Intent pattern to build Reactive Apps. [Next page]()