# Fearless extensibility: Modular malleability

**URL:** <https://forum.malleable.systems/t/fearless-extensibility-modular-malleability/249>\
**Category:** Fearless extensibility\
**Created:** [16 October 2024 13:05 UTC](https://forum.malleable.systems/t/fearless-extensibility-modular-malleability/249 "2024-10-16T13:05:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![khinsen](https://forum-cdn.malleable.systems/user_avatar/forum.malleable.systems/khinsen/32/45_2.png) [@khinsen](https://forum.malleable.systems/u/khinsen)\
**Post date:** [16 October 2024 13:05 UTC](https://forum.malleable.systems/t/fearless-extensibility-modular-malleability/249/1 "2024-10-16T13:05:22Z")

</div>

So… here is my contribution!

[https://blog.khinsen.net/posts/2024/10/16/modular-malleability.html](https://blog.khinsen.net/posts/2024/10/16/modular-malleability.html)

---

<div class="post-metadata">

**Author:** ![jryans](https://forum-cdn.malleable.systems/user_avatar/forum.malleable.systems/jryans/32/7_2.png) [@jryans](https://forum.malleable.systems/u/jryans)\
**Post date:** [28 October 2024 11:04 UTC](https://forum.malleable.systems/t/fearless-extensibility-modular-malleability/249/2 "2024-10-28T11:04:47Z")

</div>

Thanks for sharing this focus on modularity! 🙂 I think in some sense I sort of “assume” modularity in my own malleable thinking, so I might not have realised the importance of calling it out specifically like this. It’s nice to have articles like this that bring it front and center.

---

<div class="post-metadata">

**Author:** ![khinsen](https://forum-cdn.malleable.systems/user_avatar/forum.malleable.systems/khinsen/32/45_2.png) [@khinsen](https://forum.malleable.systems/u/khinsen)\
**Post date:** [28 October 2024 14:29 UTC](https://forum.malleable.systems/t/fearless-extensibility-modular-malleability/249/3 "2024-10-28T14:29:29Z")

</div>

It’s not just some form of modularity that I propose, but more precisely a module structure in which the dependency graph is a tree.

---

<div class="post-metadata">

**Author:** ![colby](https://forum-cdn.malleable.systems/letter_avatar_proxy/v4/letter/c/d07c76/32.png) [@colby](https://forum.malleable.systems/u/colby)\
**Post date:** [23 November 2024 21:14 UTC](https://forum.malleable.systems/t/fearless-extensibility-modular-malleability/249/4 "2024-11-23T21:14:44Z")

</div>

Needs an in-depth comparison to the work Bracha has done on Newspeak. There’s a lot of overlap here re the safety of using a submodule without polluting a shared namespace and clobbering something else.

The Newspeak—Smalltalk connection is something, too.

---

<div class="post-metadata">

**Author:** ![khinsen](https://forum-cdn.malleable.systems/user_avatar/forum.malleable.systems/khinsen/32/45_2.png) [@khinsen](https://forum.malleable.systems/u/khinsen)\
**Post date:** [24 November 2024 09:49 UTC](https://forum.malleable.systems/t/fearless-extensibility-modular-malleability/249/5 "2024-11-24T09:49:53Z")

</div>

Thanks for pointing out Newspeak! I had looked at it a while ago but with a different focus: its [integration into the DOM](https://blog.bracha.org/illiterateProgramming/out/illiterateProgramming.html), which is quite neat. I noticed the concept of nested classes but didn’t look into it any further. I guess I should!