So I opened up Adobe Brackets to update a website’s source files, and it showed me this notification:
On September 1, 2021, Adobe will end support for Brackets. If you would like to continue using, maintaining and improving Brackets, you may fork the project on GitHub. Brackets users are encouraged to switch to Visual Studio Code for code editing.
The quotation might be inaccurate because as soon as I clicked the GitHub link and Microsoft Edge pulled up the GitHub repository for Brackets, the notification went away (I mostly use Firefox, but I generally don’t bother to make Firefox the default Web browser). So I might be wrong about the Visual Studio Code link.
However, on the GitHub repository README, there is a slightly elaborated version of the notification:
⚠️ On September 1, 2021, Adobe will end support for Brackets. If you would like to continue using, maintaining, and improving Brackets, you may fork the project on GitHub. Through Adobe’s partnership with Microsoft, we encourage users to migrate to Visual Studio Code, Microsoft’s free code editor built on open source.
Back then it looked like Sublime Text was considered the standard editor for Web development. And it also seemed that every individual user was using it without paying the license fee, taking advantage of the fact that the trial period is open-ended.
But come on, after a year of using Sublime Text every single day how can you possibly still be undecided?
I’ve been told that Sublime HQ doesn’t prosecute individual users for failure to pay the license fee, they only care about corporate users, and that makes sense. Even so, if there’s a free alternative that I can use with a clear conscience, I should use that instead.
And that’s how I found Brackets. Just like Sublime Text, Adobe Brackets makes it very easy for you to write relative URLs for links and images.
That was a frequent pain point for me with Notepad (which I still do occasionally use for editing HTML, when I know I won’t have to deal with a bunch of “internal” URLs).
I’ve used Visual Studio Code on both Windows 10 and macOS Catalina, but not very much on either. It seems to be a decent enough program when run on a computer with sufficient memory.
If I recall correctly, my old Gateway with Windows 8 only had four gigabytes RAM. Brackets had become sluggish to start on that computer. I surmise Visual Studio Code would have performed no better.
According to Shalitha Suranga, Visual Studio Code requires 1.2 gigabytes of RAM to do its job properly. Add in a Web browser, Adobe Photoshop and Slack, and you’re probably maxing out your RAM if you only have four gigabytes to work with.
Suranga switched to Lite, a lightweight text editor for Windows and Linux available under the MIT License. Lite is said to only need twenty megabytes’ worth of RAM.
As for me, I haven’t used Lite, I might try it. For the time being, I will keep using Brackets. But come August, I will probably reassess that decision.