pulsar VS micro-editor

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.

To see more screenshots of micro, showcasing some of the default color schemes, see here.

Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:

- gdu: a NCDU clone, much faster on SSD mounts [1]

- duf: a `df` clone with a nicer interface [2]

- massren: a `vidir` clone (simpler to use but with fewer options) [3]

- gotop: a `top` clone [4]

- micro: a nice TUI editor [5]

Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.

[1]: https://github.com/dundee/gdu

[2]: https://github.com/muesli/duf

[3]: https://github.com/laurent22/massren

[4]: https://github.com/xxxserxxx/gotop

[5]: https://github.com/zyedidia/micro

> The worst way to store and manipulate text is to use an array.

Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.

Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.

Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).

[1] https://github.com/zyedidia/micro

[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...

[3] https://github.com/cessen/ropey/pull/67

There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:

found that micro has dedicated info page for copy paste

micro: winget install zyedidia.micro