Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sunsetting Atom

github.blog

Post reply on HN
Print view View original

711–720 of 880 posts

Re: Sunsetting Atom

#711

Post by shuntress »

nathansobo wrote: post #253

Founder 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…

This actually looks really promising despite fitting snugly into the "Show HN: Hey check out my cool unique new project" mold.

I know it's not the main point of the DevXConf presentation but I really like the look of that multi-buffer feature.

Re: Sunsetting Atom

#712

Post by mutagen »

mongol wrote: post #704
ClawsOnPaws wrote: post #561

Earlier 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…

Unrelated question: how does accessibility work on smartphones? Do you use something like a physical keyboard to interact with GUI elements in apps?

I came across this video from 2020 that demonstrates a couple of ways it works on iOS:

https://twitter.com/Kristy_Viers/status/1287189581926981634

You can turn on the various accessibility features and try them yourselves. While I was already aware of the 'voiceover' features, I was blown away by the braille keyboard and how quickly she could type with it.

Blind people use TTS set at ridiculous speeds that make my 1.5x podcast playback seem glacial. Even back in the late 80s I remember a blind classmate who had a portable electronic typewriter thing that read her entries back to her at rapid speed.

Re: Sunsetting Atom

#713

Post by Drew_ »

toyg wrote: post #234
vdnkh wrote: post #190

Earlier quoted context omitted.

> One could imagine a world where strong standards have been established w And yet this didn't happen and Electron did. The "free market" of FOSS development settled on Electron as the winner for cross-platform development.

It wasn't FOSS that settled on Electron - it was businesses and corporations. Decisions were taken with an eye to balance sheets and P&L reports; Electron remains the cheapest option of them all, because the supply of moderately-skilled HTML/JS labor is naturally larger than for any other language - all thanks to choices the Netscape Corporation made in 1995, when they needed interactivity in their product and they n…

Businesses and corporations are part of FOSS. The majority of FOSS doesn't exist without them.

Re: Sunsetting Atom

#714

Post by dangjc »

meanmrmustard92 wrote: post #624

RIP. Hydrogen [ https://atom.io/packages/hydrogen ] running on Atom is the cleanest multi-lingual data science IDE in existence and has been my go-to for years. Haven't found a drop-in replacement elsewhere [vscode's language support is scattered: native python integration, different for R, Julia etc]. Anyone on HN have recs [besides vim slime or send-to-terminal options in other editors, which work but are clunky] ?

People kept asking me why I was still using Atom, and Hydrogen was it. It doesn't seem like there's an exact equivalent in VSCode. For now, I'm just relying on sending blocks of code to the interactive Python terminal. Or using the Jupyter extension. But the former might not work with other languages and the latter requires .ipynb files which maybe you don't want to check into git.

Re: Sunsetting Atom

#715

Post by jeffy90 »

mongol wrote: post #704
ClawsOnPaws wrote: post #561

Earlier 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…

Unrelated question: how does accessibility work on smartphones? Do you use something like a physical keyboard to interact with GUI elements in apps?

smartphones come packaged with a screen reader. The screen reader announces what is present on the screen

Re: Sunsetting Atom

#716

Post by derelicto »

nathansobo wrote: post #253

Founder 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…

Thank you for everything! Atom paved the way for the next gen of editors. Curious to see what comes out of zed! Live collab seems amazing.

As a wishlist item, can we get a native vim mode with .vim.rc support? :D

Re: Sunsetting Atom

#717

Post by dark-star »

polote wrote: post #690
ClawsOnPaws wrote: post #561

Earlier 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?

Actually it's pretty good development practice to start an SaaS app with localization from day one. Why wouldn't you? The world doesn't revolve around English speakers (there are more non-English speakers than there are English speakers, at least what their first language is concerned), the same as it doesn't revolve around people with 100% vision.

You start an editor with extensibility from day one, as well as theming from day one, as well as multi-platform from day one, etc.

Why should it be different for Localization or Accessibility?

Re: Sunsetting Atom

#718

Post by behnamoh »

ClawsOnPaws wrote: post #650
serial_dev wrote: post #606

Earlier quoted context omitted.

How do other editors/IDEs perform in terms of accessibility? What are your favorites?

My favorite is VS Code by far. I use it daily. They recently also added a bunch of sound cues to help figure out if code is folded or a line contains an error. It's pretty great. Auto completion reads well, the parameter hints read, even the built-in terminal works. So overall I'm really happy with it.

speaking of VSCODE, i wonder if MS acquiring github has anything to do with sunsetting atom.

Re: Sunsetting Atom

#719

Post by Aeolun »

exyi wrote: post #459
fmntf wrote: post #433

Earlier quoted context omitted.

I work on the linux kernel using CLion and the IDE is still fast. I would not be interested in a non-Java IDE for the performance.

Are you using 32-core / 100GB RAM monster machine? I do everything on my rather powerful laptop, but Jetbrains IDEs are just too much. I can't have more than one project open at time, which is limiting. I didn't try CLion, only IntelliJ for Scala and Rider for C#/F#, all on smallish projects and it will still take 3-6GB of memory :| I'd be interested in even lighter than VSCode IDE ;)

I can easily open 20ish projects, but the experience is often still sort of sluggish.

Like, change a file outside of the editor, open it again, and it’ll sit there stuttering for a bit while it realizes the file is updated and it has to re-index.

It’s not the end of the world, but the experience there could be more fluid. Because you do this often (e.g. every time you switch a git branch)

Re: Sunsetting Atom

#720

Post by SamoyedFurFluff »

polote wrote: post #690
ClawsOnPaws wrote: post #561

Earlier 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?

Please consider that implementing accessibility during the design phase is infinitely easier than post implementation. Additionally, accessibility benefits everyone and we should always be advocating for it regardless.

Imagine if you can code screenless. Headaches in response to light? Not a problem. Avoiding screens at night to wind down for sleep? Solved. Eyesight deteriorating (a totally normal thing that comes with age)? No new tech or ecosystem to need to adapt to, everything is already there.

Post reply on HN