Live data from Hacker News

Sunsetting Atom

github.blog

731–740 of 880 posts

Re: Sunsetting Atom

#731
post #658

Earlier quoted context omitted.

When this inevitably happens to VSCode, I'm sure we'll all flock to Sublime Text in droves (or some hip new editor on the block). Contingency planning for this could be a small but wise time investment for dependent teams. VSCode could very well go the way of the Do... Docker.

> When this inevitably happens to VSCode, I'm sure we'll all flock to Sublime Text in droves (or some hip new editor on the block). the normalization of this behavior within the industry makes using emacs or vim even more satisfying. it's nice to having an unchanging cement foundation to stand upon once-in-awhile.

Absolutely. Why continuously reinvent the wheel when there are far more interesting problems to work on :)

Re: Sunsetting Atom

#732

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…

How does it do in comparison to the other upcoming "better VSC"s? Like for example:

https://v2.onivim.io/

https://helix-editor.com/

Re: Sunsetting Atom

#733

Earlier quoted context omitted.

I don't use Visual Studio, so I'm intrigued as to what VS can do in 10 minutes that takes 2+ hours in VSC?

One example could be scaffolding out a CRUD app and DB fairly quickly. Even excluding scaffolding, VS can eliminate a lot of the boilerplate that takes time if you need to type it out yourself. Not saying you can't setup VSC to do those kinds of things also, but VS is a tools included solution out of the box. (I say this as someone who hasn't touched VS in a few years now, but used it daily for a few years before tha…

So a generator tool is built in instead of installed via a package manager? Doesn’t sound like a big advantage, you still have to know that those tools are there and learn how to use them so you’re only saving the amount of time it takes to run npm i —global yo once. Same thing with snippets and emmet and a myriad of other shortcuts. Having a huge selection to choose from gives the advantage to VSCode in my book.

Re: Sunsetting Atom

#734
post #409

Earlier quoted context omitted.

IMO the killer thing is performance, VSCode starts fast and is smooth to write with. It blew away the older set of Electron-based editors. They work tirelessly on performance every release and it shows imo. Allowing extensions without destroying perf isn't easy either.

Which editor did you came from to think vscode start fast? msword?

Comparing it to Atom etc. It takes like 3 seconds to load a medium-sized Python project for me. And I was a long time vim user. The speed of vim is not worth the ridiculous gap in features.

Re: Sunsetting Atom

#735
post #409

Earlier quoted context omitted.

IMO the killer thing is performance, VSCode starts fast and is smooth to write with. It blew away the older set of Electron-based editors. They work tirelessly on performance every release and it shows imo. Allowing extensions without destroying perf isn't easy either.

I said basically the same in a sibling comment but I can't agree with you. VS Code doesn't start fast enough and it's not smooth to write with. It's not exactly bad but you definitely feel the slight delays and slowness all the time . I went back to Sublime exactly to get faster startup and smoother writing than what VS Code was offering. So I'm pretty excited to see how Zed turns out!

I don't percieve any of that but I also don't care if a game framerate is 30 or 60 or 120, it's probably the same type of brain difference! More choices is always a good thing.

Re: Sunsetting Atom

#736

Earlier quoted context omitted.

No almost about it, it's an anti-pattern and I personally would consider it a "worst practice". If you're deploying from an IDE it means you lack visibility, feedback, and automation fundamentals. What I do like is developer ownership and being able to see a change all the way through to production but having a system of record without manual intervention is always preferred.

It's always so interesting to see people who have no concept of your stack/problem-space speak so confidently about what you must be doing wrong. I don't know if you've just chosen to assume the worst or don't care enough to think about it for more than a second but I've been very clear in all my comments that these are developer-specific machines we are deploying to. It's literally no different from running VMs on y…

Your aversion to running shell commands is definitely not helping you and what you're describing definitely doesn't need an IDE to be done so it's not shocking that people are questioning how familiar you are with deploying code and/or leveraging shell programs.

Re: Sunsetting Atom

#737
post #656

Earlier quoted context omitted.

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.

Would you mind commenting on XCode? I heard that Apple really cares about accessibility.

The design of the existing and previous mac mice and the new System Settings app in MacOS Ventura tell a different story.

Re: Sunsetting Atom

#738

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…

You're not going to get it right. At worst you ll make the same mistakes and at best you ll do the opposite mistakes.

No migration, sunsetting, "this is legacy, let s redo it all" will ever fix anything. Fix what doesnt work.

Re: Sunsetting Atom

#739
post #704

Earlier quoted context omitted.

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

I commonly watch dev talks and walkthroughs on youtube at greater than 2x speed because the talkers make an effort to talk slowly for non native English speakers.

Just pop open the console with F12, enter the following and hit enter:

$('video').playbackRate = 2.5

Change `2.5` to whatever number you wish.

Press up in the console to bring back your last command faster with the cursor at the end so you just delete the number, type a new number and hit enter.

Re: Sunsetting Atom

#740

Earlier quoted context omitted.

This is why I continued to use sublime text all the way up to capitulating to TypeScript. Code was slower because of all the intellisense. I've had Code freeze on me a few times. Something that I don't have happen in Sublime or Vim. If you have a lot of RAM and work on a current mainstream OS it may seem smooth, but it's still using 400mb of RAM. May as well use Eclipse or WebStorm FWIW. That said I'm using VSCode no…

> "but it's still using 400mb of RAM" Why does this matter? What is the point of saving RAM instead of using it?

[deleted]
Post reply on HN