Live data from Hacker News

Atom was archived today

github.com

171–180 of 614 posts

Re: Atom was archived today

#171
post #115

Earlier quoted context omitted.

"VSCode is the greatest productivity tool in the history of software engineering" in a world where vi and emacs exist seems like a bit of an exaggeration, and I'm not even a fan of either (VS Code is my daily driver; I like my GUI editors and I like them to behave like normal apps on the platform I'm running).

Vim and Emacs cannot compare to VSCode when it comes to productivity. With VSCode, you type the name of any programming language in the extension search, click "Install", and you have a world-class development environment for that language ready to go. This is light years ahead of the traditional editors, and saves many hours of time. Not to mention that VSCode has countless other productivity boosters built in which…

>With VSCode, you type the name of any programming language in the extension search, click "Install", and you have a world-class development environment for that language ready to go.

Same with Emacs. `M-x package-install`, type, RET.

Re: Atom was archived today

#172

Earlier quoted context omitted.

Great point. I think the OP would be amazed if you showed them how a car works...

I’m sure they have an understanding of how a car works, and also, that they actually meant “software engineering”.

I did in fact mean all of engineering.

Re: Atom was archived today

#173
post #11

Earlier quoted context omitted.

People hate on electron, but it's a pretty amazing piece of tech if you ask me. I can turn a browser game into a steam game with basically no effort which is nice because browsers change over time and electron helps you get a working offline snapshot of something you created.

> People hate on electron, but it's a pretty amazing piece of tech if you ask me. It really does come down to how people build on top of it. I tried opening a 2gb log file in Atom and it took like 10 minutes before crashing. VSCode on the other hand, while a bit slow, opened it and I could search quickly and scroll it without any issue at all. That was what caused me to switch.

I used VS Code beta and it was slow… I remember an issue in the beginning where the cursor was refreshing at 60fps, causing huge delays. The software evolved really well over the years.

Re: Atom was archived today

#174
post #36

Make no mistake... This project, Atom. Provided the runway that others copied, then improved upon (and on and on... with plenty of funding). Atom provided the seed, excitement and vision for what is possible on this platform, and should be proud of that fact.

People started focussing on text editors again after Atom came out.

Re: Atom was archived today

#175
post #143

Earlier quoted context omitted.

If we're talking about professional tools i'm not sure if setting it up as fast as possible is the best productivity comparison. All good tools need getting to know them, and setting things up yourself (eg. in vim) means you also know how to fix any issues that pop up in the future. Installing a vscode plugin for playing around is great, but it doesn't automatically make you a professional and stable production envir…

> All good tools need getting to know them Wrong. Good tools don't require that. Imagine someone showed you a complicated mechanical contraption and told you "it's a type of hammer, much better than the 'non-professional' hammer, but you need to 'get to know it' first". That product would be dead on arrival. Great tools are obvious in their base functionality and have optional additional layers that can be discovered…

Step inside a woodworking- or machine shop sometime and see how many of tools there you can instantly use with proficiency, with no instruction. (Please stand back from the table saws while trying this experiment.)

It’s wonderful and beautiful that we can get real work done with a heavy thing on a stick, but pretending every tool can be as simple as a hammer is not really arguing in good faith.

Re: Atom was archived today

#176

Earlier quoted context omitted.

> People hate on electron, but it's a pretty amazing piece of tech if you ask me. It really does come down to how people build on top of it. I tried opening a 2gb log file in Atom and it took like 10 minutes before crashing. VSCode on the other hand, while a bit slow, opened it and I could search quickly and scroll it without any issue at all. That was what caused me to switch.

Your specific example highlights the performance difference between VS Code and Atom very nicely, and VS Code is an absolute gem of engineering. But, for large files, I am not sure it has much to do with Electron in this specific case. Notepad is about as native as they come, and famously struggled with large files - anything over a few dozen KB - for a few decades (maybe still today?). Basically, if you're going to…

Loading large files need not have anything with Electron. The file can live in another child process either fully in memory or swapped to the filesystem. When you scroll you can load the required contents into the view (Electron). For searching you can build index or even perform search on the swap and show results accordingly.. It's complex but can be done with Electron (as proved by VSCode).

Re: Atom was archived today

#177

Earlier quoted context omitted.

Why? And what's better?

https://kit.svelte.dev/

I don't like any framework that uses templates. I already know JS, let me use that. Also they usually work poorly with editors and TypeScript since they require custom syntax to be supported. I'll stick with JSX.

Re: Atom was archived today

#179
post #143

Earlier quoted context omitted.

If we're talking about professional tools i'm not sure if setting it up as fast as possible is the best productivity comparison. All good tools need getting to know them, and setting things up yourself (eg. in vim) means you also know how to fix any issues that pop up in the future. Installing a vscode plugin for playing around is great, but it doesn't automatically make you a professional and stable production envir…

> All good tools need getting to know them Wrong. Good tools don't require that. Imagine someone showed you a complicated mechanical contraption and told you "it's a type of hammer, much better than the 'non-professional' hammer, but you need to 'get to know it' first". That product would be dead on arrival. Great tools are obvious in their base functionality and have optional additional layers that can be discovered…

>Wrong. Good tools don't require that. Imagine someone showed you a complicated mechanical contraption and told you "it's a type of hammer, much better than the 'non-professional' hammer, but you need to 'get to know it' first". That product would be dead on arrival.

You mean like a nail gun? The kind that all professional roofers use?

Post reply on HN