# Ink & Switch malleable software essay

**URL:** <https://forum.malleable.systems/t/ink-switch-malleable-software-essay/340>\
**Category:** General\
**Created:** [10 June 2025 16:17 UTC](https://forum.malleable.systems/t/ink-switch-malleable-software-essay/340 "2025-06-10T16:17:45Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![Apostolis](https://forum-cdn.malleable.systems/user_avatar/forum.malleable.systems/apostolis/32/96_2.png) [@Apostolis](https://forum.malleable.systems/u/Apostolis)\
**Post date:** [20 June 2025 16:18 UTC](https://forum.malleable.systems/t/ink-switch-malleable-software-essay/340/41 "2025-06-20T16:18:01Z")

</div>

Components —\> reusable pieces like software in a library  
standards → abstractions / specification that leads to increase in variation.

From the thread on lithification:

> [@Lithification](http://forum.malleable.systems/t/lithification/315/13):
>
> Some more thoughts: A. Abstraction vs reusability Assuming there is a membrane that separates a component from its environment, that has constrains on both the component and its environment. We could have big variation on the environment and a single implementation of the component in which case, we talk about reusability. the component that only works on a specific environment, in which case we talk about abstraction. I believe that we are interested in abstraction and not so much reusa…

---

_[View the full topic](https://forum.malleable.systems/t/ink-switch-malleable-software-essay/340)._
