Live data from Hacker News

Sunsetting Atom

github.blog

871–880 of 880 posts

Re: Sunsetting Atom

#871

Earlier quoted context omitted.

You've never run them in a terminal?

You can’t run VSCode or Atom in a terminal, so I don’t think that’s a fair comparison.

???

I'm not making that comparison.

GP's post was in response to the complaint that Emacs/Vim are hard to exit. They said that "Or, you know, you could just click on the File menu and click on Quit."

And I'm just saying you can't do that in the terminal.

Not sure what you're going on about.

Re: Sunsetting Atom

#873

Earlier quoted context omitted.

You've never run them in a terminal?

> You've never run them in a terminal? When I run Emacs with a blank config, the default display has this: Get help C-h (Hold down CTRL and press h) Emacs manual C-h r Browse manuals C-h i Emacs tutorial C-h t Undo changes C-x u Buy manuals C-h RET Exit Emacs C-x C-c Activate menubar M-`

> Or, you know, you could just click on the File menu and click on Quit.

and in Vim, there is no such display.

Re: Sunsetting Atom

#874
I used Atom for a long time after it was cool. I just loved the idea of an editor I could extend using the standard web tools and frameworks. Overall love this project, and still am a little miffed that VSCode ate their lunch. Best of luck on everything Nathan and the team do.

Re: Sunsetting Atom

#875
post #467

Earlier quoted context omitted.

Minification helps the parser too, try running VS Code from sources and you’ll notice startup is significantly slower.

huh I would think there is no measurable difference there. However I honestly have no idea how much time does JS parser spends on what exactly. Are longer variable names and less tabs that big of a deal? It’s all in memory anyway, no… the lexer or tokenizer or whatever (…I never finished my compiler course…) just goes through that

Without nonlinearities like optimization/type checking/etc, the runtime is basically just the time to loop through the bytes. Make the input a quarter the size and you have a quarter the bytes to loop through. College classes will say “oh it’s all O(N) anyways, no big deal”. Industry on the other hand says “why make tens of millions of people wait 4 seconds for this to start when we could make them wait 1 second just as easily”.

The product’s source maps are publicly available in a way the debugger understands and the original code is freely accessible so there’s no real downside.

Re: Sunsetting Atom

#876

Earlier quoted context omitted.

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

I made a website that uses bookmarklets just for that.

https://www.videospeedup.com/

Re: Sunsetting Atom

#877

Earlier quoted context omitted.

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

Not likely, GitHub is a separate business and makes their own decisions. MS also competes with GitHub also; Azure Repos are a thing, as is Azure DevOps and those are just two examples. MS has plenty of products that compete with each other. In some spaces this is a good strategy as you will capture more market share with two products than you will with one and you can avoid to an extent monopoly claims. GitHub Codesp…

Microsoft has moved essentially the whole development team for Azure DevOps to GitHub. GitHub is what they consider the future.

Re: Sunsetting Atom

#878
I wonder how much of this is about not wanting to have to deal with and be ultimately responsible for the security implications of a plugin system built on top of npm packages and tooling ... It's a great editor but seriously vulnerable.

Re: Sunsetting Atom

#879
post #327

Earlier quoted context omitted.

Do you have any plans of open-sourcing the UI framework?

We do have plans. Stay tuned!

Also with your custom UI framework, you will need to re-implement a text editor from scratch which is a pretty daunting task by the way [0]. Do you also have plans to open source the text editing / make text editing a part of the framework? Text editing (right there with accessibility) is the core reason why one would not go with a pure immediate mode GUI for any app. I guess you are baking immediate mode with some extras?

[0] https://www.construct.net/en/blogs/ashleys-blog-2/simple-sof...

Re: Sunsetting Atom

#880

Earlier quoted context omitted.

> One could imagine a world where strong standards have been established which would allow you to easily deploy lean native applications across a wide variety of platforms. Here is a unified binary format that can run on Linux, MacOS, Windows, FreeBSD, OpenBSD, and NetBSD too. They also boot from the BIOS. But it doesn't support GUIs (yet?). https://justine.lol/ape.html

That’s more of a hack than anything actually serious.

Redbean 2.0: "more than a hobby project"

https://justine.lol/redbean2/>

https://news.ycombinator.com/item?id=31764521>

Post reply on HN