Atom No More?
Yesterday one of my library colleagues at Grinnell College posted an announcement that Atom would be retired (sunset) in December 2022. Ouch, I have a lot of workflows that depend on Atom!
So, today part of my mission is to begin the process of migrating workflows, both work-related and personal/at-home, from Atom to its most logical replacement, Visual Studio Code or VS Code as it’s largely known in the development community. The other part of today’s mission was to update this blog, something I’ve not done in far too long!
Continue Reading »