You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft Visual Studio in all of its versions is an unproven technology. The trouble started on Microsoft Visual Studio 2019 a decrepit free download with bugs when I tried to save a simple Visual Basic program. Not only is it bear to download my work did not save correctly. Why does adobe/Brackets have to migrate to this unsatisfactory application when I can just use the adobe/brackets during these extraordinary circumstances? The coursework I need to do is just fine right here.
The text was updated successfully, but these errors were encountered:
Comment by OdinVex Friday Jul 09, 2021 at 14:45 GMT
Visual Studio 2019 and Visual Studio Code aren't the same thing. At all.
I think GitHub being owned by Microsoft might have some kind of censorship about this, but I say :censored: Microsoft. I've begun searching for a FOSS (free, open-source software) alternative to Brackets. I don't use JavaScript/npm :censored:, pure HTML5+CSS. Brackets has worked flawlessly for me.
Comment by adrocknaphobia Tuesday Aug 24, 2021 at 21:50 GMT
Brackets is not going away.
The community will take ownership of the project after Sept 1 (albeit with a different repo). Both the website (brackets.io) and the extension registry will live on. <3
Issue by Corncheese2
Tuesday May 11, 2021 at 00:18 GMT
Originally opened as adobe/brackets#15347
Microsoft Visual Studio in all of its versions is an unproven technology. The trouble started on Microsoft Visual Studio 2019 a decrepit free download with bugs when I tried to save a simple Visual Basic program. Not only is it bear to download my work did not save correctly. Why does adobe/Brackets have to migrate to this unsatisfactory application when I can just use the adobe/brackets during these extraordinary circumstances? The coursework I need to do is just fine right here.
The text was updated successfully, but these errors were encountered: