Brackets VS pulsar

Link to the wonderful people who discovered how to fix the stupidest live preview error in all of human history: https://github.com/adobe/brackets/issues/11519

Heh, just a month ago Adobe Brackets (another Atom clone) did the same https://github.com/adobe/brackets

Oh, that's a good point about the sunsetting. In Brackets's case, Adobe left it active in the hands of the community.

Live Preview in particular is one of the areas I had some fun working on. I worked out a way to do diff/patch to make it quickly and incrementally update the browser[1]

[1]: https://github.com/adobe/brackets/wiki/Research%3A-HTML-DOM-...

Brackets may be a free and open-source code editor from the owner of Photoshop, Premiere Pro, and other amazing software providers Adobe. it's a primary target for web development and particularly on web designing because it provides plenty of features for web designers like Quick edit, Quick Docs, Live preview, Autosave, JSLint, Preprocessor support, Open source, Extension, themes, and more. Its software is licensed under the MIT license and it's currently run and maintained by Github's open-source developers. Its GitHub repository is https://github.com/adobe/brackets. it was created with help of Electron JS(JavaScript). it's available in 38 languages like HTML, CSS, JavaScript. It supports lots of extensions like Beautify, Autoprefixer, Emmet. Minifier, ToDo, Bracket Gits, Brackets File Icons, Swatcher, and more. it absolutely was initially released on 4 November 2014 around 7 years ago. it's integrated with NODE JS, JavaScript, Adobe PhotoShop, Vizy, and more, and firms like Zenkit, Startlink, MaGIC, WorldGaming, NeoQuant, Core, OpportunityWork, and more are using it for her projects. it's lots of benefits like -

I think you just need to download this : https://github.com/adobe/brackets/releases/download/release-1.14.2/Brackets.Release.1.14.2.msi

I don't think there's a fix for this. This problem has many issue entries on github, and it will eventually get worked on at some point. However you could try this troubleshoot guide.

https://brackets.io/ as well as https://registry.brackets.io/ are already back again. Currently there are still some issues with SSL certification but as soon as these are resolved we should expect to get a working extension manager again. After that, the community will be able to transition to the new branch of Brackets (brackets/brackets-cont) most likely by some kind of patch.

You may be thinking of Pulsar (<https://pulsar-edit.dev/>)?

> VSCodium is not "designed" to be less functional, since it is a project maintained by developers who are unaffiliated with Microsoft.

In today's (OSS) world, employment or affiliation doesn't matter much. Microsoft can propose what they want and get what they want from the project, at the end of the day. I don't think these independent maintainers have power to say "No" (if a VSCodium developer can chime in here, I'd love to be stand corrected), or they risk VSCodium to be forked to VSCodiumX, by developers who are friendlier to the megacorp which loves Linux.

Yes, VSCodium is a node to Chromium. "-ium" has a ring akin to "-ish" in today's conjecture. Freemium - Free-ish but not. Chromium - Chrome-ish but not. VSCodium - VSCode-ish, but not. This might be curse in the naming, but it feels like that, at least for me.

The blog post I linked quotes a tweet which supports what I'm saying, heck even the blog post does a much better job of detailing what I was trying to say here in my previous comments.

To circle back, the problem with -ium projects are, they are effectively banned from participating in the main ecosystem which drives these projects forward, and to be in "The Ecosystem", you need to use the closed source versions with pervasive data collection and whatnot. Heck, even Google abuses Chromium with "Experiments and Proposals", which they use to politely yet forcefully push the web to the places they want. VSCodium is the same getaway drug and test vessel for Microsoft.

Lure with Open Source version, trap with closed source version for "Full Benefits" (for the company, because user is the product).

> You're entitled to your own opinion, but Atom was developed by GitHub...

Yes & yes.

> which was acquired by Microsoft.

Yes.

> It doesn't help that Atom was discontinued last year, with the final version having been released in March 2022

However, it's forked as Pulsar [0], which I meant by "current form" in my previous comment. Again, it's MIT licensed, and that's not my favorite, but at least it's not a company editor now.

Atom's original developers started to build Zed, which is worst of both worlds currently (Open source with a closed backend, plus "All your data belong to us" clause).

At the end of the day, from my perspective "-ium" projects and their sanitized versions are just open-core versions of the "main tools" developed from them.

Just because these versions somehow work, and have a permissive license doesn't make them open source in the meta sense. Pedantically they are open source software, yes, but they are just the "Open Core" or Demo/Shareware versions of the tools which companies use to strange to ecosystems.

This is just enshittification of open source in my eyes.

More power to you if you're happy with the -ium tools, but I'd rather use truly free software (Like Eclipse), or use completely honest closed source software (like BBEdit), instead of using tools designed to look like open source but not.

[0]: https://pulsar-edit.dev/

I thought spiritual successor to Atom is Pulsar. https://github.com/pulsar-edit/pulsar

Pulsar has a TTS package, for those who were very comfortable in Atom.

In addition to the already mentioned Emacs, I would check Pulsar, the Atom successor.

Community-led fork of Atom

Also, don't worry - we understand that there's documentation lacking on the "extend Pulsar" part and on package creation, but we're working on it. We're also working on better ways to test, document, and create packages (and grammars - see, for example, how we usually tested grammars in the past and how we're migrating to for example), so it's just a matter of time, really.

Our website is https://pulsar-edit.dev/, feel free to check out or Discord server if you want to come and say hi or have any questions - we are a friendly bunch.