# Github annouced codespace. does it mean Atom is now abandoned?

**URL:** <https://discourse.julialang.org/t/github-annouced-codespace-does-it-mean-atom-is-now-abandoned/38923>\
**Category:** Community\
**Created:** [May 7, 2020, 1:03am UTC](https://discourse.julialang.org/t/github-annouced-codespace-does-it-mean-atom-is-now-abandoned/38923 "2020-05-07T01:03:59Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![Zach\_Christensen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zach_christensen/32/7220_2.png) [@Zach\_Christensen](https://discourse.julialang.org/u/Zach_Christensen)\
**Post date:** [May 7, 2020, 3:22pm UTC](https://discourse.julialang.org/t/github-annouced-codespace-does-it-mean-atom-is-now-abandoned/38923/17 "2020-05-07T15:22:17Z")

</div>

This is a good example of why it has been wise to invest more in development of modular components of an IDE than a single unified codebase. Editors will come and go but we can continue to develop the components with a fair degree of confidence they will be useful for years to come.

---

_[View the full topic](https://discourse.julialang.org/t/github-annouced-codespace-does-it-mean-atom-is-now-abandoned/38923)._