“Sunsetting” an open source project seems… unfitting? Hand it off to the community, look for new maintainers, donate it to the Apache Retirement Home for Veteran Projects, sure. But saying that you’ve decided to “sunset” or “archive” it, telling users to plan for their migration, seems counter to the notion that open source software forms part of a commons - something that Github, of all companies, should understand.
> Apache Retirement Home for Veteran Projects Honestly, it kind of sucks that at this point you might as well call a project sunset if it has ASF stewardship, and that we seem to practically need the resources of a large company to keep an open source project "truly" afloat. I vastly prefer the honesty in saying "sunset"; it helps bring more light to this situation, and will perhaps drive new approaches to funding fo…
Sunsetting Atom
721–730 of 880 posts
Re: Sunsetting Atom
#722Earlier quoted context omitted.
Add a really good vim mode and I’m there.
Earlier this year Keith Simmons, the author of Neovide ( https://github.com/neovide/neovide ), joined our team. He's been working on Vim bindings and paying a lot of attention to getting it right. As you probably know there's a lot of surface area, so this will take time.
Re: Sunsetting Atom
#723Re: Sunsetting Atom
#724Earlier quoted context omitted.
Hey, Please don't forget about accessibility. Getting this right from day 1 will make your life a lot easier in the long run. If I remember correctly, I was never able to use Atom with a screen reader. Hearing custom UI already makes me nervous and I'm pretty sure I won't be able to use Zed with a screen reader either. Blind developers exist. Please don't forget about us. It's one of the few areas where we can actual…
It is normal to advocate for your needs but asking for it to be included from day 1 is weird. The same way you don't start a saas app with localization from day one. I'm not blind so for sure I won't really care about accessibility but honest question why not use an ide developed for blind people instead of using the same as non blind people?
Re: Sunsetting Atom
#725Re: Sunsetting Atom
#726Earlier quoted context omitted.
Are you kidding? It’s a chat client that works in a browser. About as Linux friendly as it gets.
That's just an example. You want some more? https://www.electronjs.org/apps
Re: Sunsetting Atom
#727Founder of Atom here. We're building the spiritual successor to Atom over at https://zed.dev . We learned a lot with Atom and had a great time, but it always fell short of our vision. With Zed we're going to get it right. Written in Rust, custom native UI framework, engineered to be collaborative. Just starting our private alpha this week, so the timing of this announcement feels quite fitting. Here's a talk I gave l…
>When you move the cursor or type a character, you should see pixels on the next refresh of your display—every time. Even sub-perceptual pauses add up over the course of a day to create unnecessary stress.
I remember there were lots of research for this in Next-Generation Atom during the Atom era, before VSCode came along. Having a UI and text responsiveness within 16ms on a 60Hz Monitor is a tall order which I believe even Sublime is incapable of.
Considering 95% if not 99% of developers on HN thinks VSCode is very fast or fast enough, I am not sure this point is worth pursuing. Personally I really want to see it happen. As I hate latency.
Re: Sunsetting Atom
#728Earlier quoted context omitted.
> "but it's still using 400mb of RAM" Why does this matter? What is the point of saving RAM instead of using it?
It matters because your program is probably not the only one running.
Re: Sunsetting Atom
#729Earlier quoted context omitted.
Though why does it need to be in your editor vs some command line tools or something else?
So you can deploy at a moment's notice. Why run a command instead of hitting a key combo? Or even deploy as soon as tests pass? Software should allow that. Especially software for writing other software.
Re: Sunsetting Atom
#730Earlier quoted context omitted.
> Unlike VSCode, Emacs and Vim have a learning curve. That's not the point, we were talking about plugins.
I think that the learning curve might be in reference to installing plugins. Installing an extension on vim (never done emacs) is something that does not just happen easily. There is no intuitive search for extensions built in, you likely have to install software that manages your plugins. VSCode on the other hand rarely requires more than a single click through a built in interface. The plugin ecosystem exists for c…
I personally do not use any of these package managers and instead use my systems package manager on Gentoo to manage everything. Gentoo has most of the popular projects in the ::gentoo repo under app-emacs, and packaging your own is only a few lines of bash.