# Let libraries be libraries

**URL:** <https://forum.elixirforum.com/t/let-libraries-be-libraries/75921>\
**Category:** Blog Posts\
**Tags:** best-practices, anti-patterns, blogs-by-jola\
**Created:** [July 7, 2026, 12:50pm UTC](https://forum.elixirforum.com/t/let-libraries-be-libraries/75921 "2026-07-07T12:50:38Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![martosaur](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/martosaur/32/41071_2.png) [@martosaur](https://forum.elixirforum.com/u/martosaur)\
**Post date:** [July 7, 2026, 3:49pm UTC](https://forum.elixirforum.com/t/let-libraries-be-libraries/75921/4 "2026-07-07T15:49:51Z")

</div>

100% with you in this uphill battle. Unfortunately, the DX of letting the app run its own supervision tree is just so good and `Req` is indeed a good example. Same goes for accessing application configuration: it’s just so much easier to say “put an api key into you config `config :foo_client, api_key: <my api key>` and you’re ready to go!”

---

_[View the full topic](https://forum.elixirforum.com/t/let-libraries-be-libraries/75921)._