# Shared environments?

**URL:** <https://discourse.julialang.org/t/shared-environments/79002>\
**Category:** General Usage\
**Tags:** shared-environments\
**Created:** [April 4, 2022, 12:06pm UTC](https://discourse.julialang.org/t/shared-environments/79002 "2022-04-04T12:06:09Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [April 4, 2022, 12:45pm UTC](https://discourse.julialang.org/t/shared-environments/79002/14 "2022-04-04T12:45:41Z")

</div>

> [@BeastyBlacksmith](#):
>
> one may need to get used to the habit

I keep getting that answer 🙂 , but I have the impression that this is a misconception about a complete set of kind of people that will use Julia. As a package developer I see the many advantages of that, but:

1. I don’t think it is a good thing that I have to manage environments just to sporadically plot some data which I happen to have to see while developing a package. I just want to use Plots once.

2. Most of the users of my packages will never develop packages. They will follow a tutorial, and get their results. Having the possibility of these users having issues with dependencies of other projects, of asking them to get used to using environments is out of question.

And I think that `2` is quite transparent to everybody here. I don’t know of any package author that suggests how to deal with environments _before_ installing his/her package. We don’t want our users to have these barriers, so we tell them to `] add MyPackage` and `using MyPackage` and that is it. And it should safe to do that.

edit: I consider this thread solved, my delusional speculations on this are [on this other thread](https://discourse.julialang.org/t/speculations-about-the-default-environment-or-a-new-draft-environment/78967).

---

_[View the full topic](https://discourse.julialang.org/t/shared-environments/79002)._