Live data from Hacker News

Sunsetting Atom

github.blog

261–270 of 880 posts

Re: Sunsetting Atom

#261

Earlier quoted context omitted.

You're deploying via VS Code? If so, that's a weird pattern. I've been using VS Code for years to write JavaScript/TypeScript, Python, Go, Terraform, and CSS. My settings file is 60 lines, 42 of which are "for file extension X use autoformatter Y" configs. When I first switched to VS Code I was frustrated trying to make it conform to random expectations I had. Eventually I learned that it's easier to embrace VS Code'…

> You're deploying via VS Code? If so, that's a weird pattern. I don't think it's a weird pattern, maybe a slightly legacy one but not out of the ordinary. I've seen this pattern used at multiple places (not implement by me). It makes sense if you have special use-cases where you need to use physical hardware and/or a local stack is too heavy or complicated to run.

Though why does it need to be in your editor vs some command line tools or something else?

Re: Sunsetting Atom

#263

Earlier quoted context omitted.

Atom predated VS Code and was the impetus for Electron, which VS Code uses. You may know this, but this comment makes it seem like they tried and didn't have an opportunity. They literally invented what the majority of new "desktop" apps uses to render UIs, they just couldn't compete with Microsoft (before they were bought out, after which of course Microsoft wasn't going to invest seriously in it). Edit: Fixed typo…

impotence means powerlessness or inability; the state of lacking potency. It's usually used to refer politely to erectile dysfunction. Perhaps you meant impetus ? https://www.merriam-webster.com/dictionary/impetus

Lmao, you're right indeed. My mistake!

Re: Sunsetting Atom

#264
post #179
post #28

Earlier quoted context omitted.

They embrace, extend, and extinguish products they don't make money on, so that people are forced to use products that they do make money on.

Microsoft doesn't make money from VS Code. Atom was retired due to a lack of activity with the project. I've never even seen anyone use Atom, since the time it was released 8 years ago.

Hence the parent comment:

> We should be counting down the days till they sunset VS Code to focus on VS Code "Pro".

I don't think it would serve their interests, so I'm not worried about it, but who knows? This cynicism is directed towards Microsoft because they've earned it.

Re: Sunsetting Atom

#265

I know a lot of people love vscode but are there any people who have tried something like IDEA/WebStorm/PHPStorm/etc that then went back to vscode? I had to help a developer setup deploys to a dev server from vscode the other day and I wanted to pull my hair out. I'll admit it's at least in part due to not using vscode myself but I was a heavy Sublime Text user which is very similar to vscode when it comes to how you…

I come from an era where the more fully featured your IDE, the less likely you were to truly understand what was going on under the hood. I strongly recommend everyone spend their first ~5 years coding in vim or some other basic text editor (preferably through the terminal), before leaning on an IDE to solve their problems for them. That said, VSCode is now my go-to IDE, and I haven't opened WebStorm in probably ~6 m…

Would you even do that with C# ?

I actually dislike computer science classes which won't let me just use an IDE.

No one can memorize the .net 7 API

Re: Sunsetting Atom

#266

Earlier quoted context omitted.

Why not pop out an integrated terminal and execute commands there? It's still within the editor and you could have a shell script that runs to deploy.

It all comes back to that "development cycle" and wanting to make that as short as possible. What you suggest is absolutely fine, it's just my personal preference (and something that I've seen help other devs) to make the "write code"->"see results" as tight as possible. If you add any delays, any potential chance of forgetting a step, etc then it breaks my programming flow which can kill my productivity.

I generally make a "run.sh" script or Makefile to build and deploy. Then it's just a few tappity taps in the terminal to run it again. Still not as good as a "play" button, but easier to set up in many cases.

Re: Sunsetting Atom

#267

I know a lot of people love vscode but are there any people who have tried something like IDEA/WebStorm/PHPStorm/etc that then went back to vscode? I had to help a developer setup deploys to a dev server from vscode the other day and I wanted to pull my hair out. I'll admit it's at least in part due to not using vscode myself but I was a heavy Sublime Text user which is very similar to vscode when it comes to how you…

I come from an era where the more fully featured your IDE, the less likely you were to truly understand what was going on under the hood. I strongly recommend everyone spend their first ~5 years coding in vim or some other basic text editor (preferably through the terminal), before leaning on an IDE to solve their problems for them. That said, VSCode is now my go-to IDE, and I haven't opened WebStorm in probably ~6 m…

Honestly, I don't think VSCode hides much of what's going on from you. Generally I use it to edit code and then run "go run ." on the side.

Re: Sunsetting Atom

#268

Atom has been dead for years, this is just the state funeral. The situation now is: * Sublime for the Williamsburg corpo-hipsters * emacs and vim for the wizards and furries * VSCode for all the normies who just want to get on with doing their job and don't feel a need to express their identity or politics through choice of editor * WebStorm for the chads with the monster rigs to run it

I disagree with these labels, I would say the choice of editor is more religion than politics.

Religion and religious conflict is often an expression of politics.

The conflict between Catholics and protestants in northern Ireland is not actually about subtle differences in religious doctrine.

Re: Sunsetting Atom

#269

Does anyone know the current status of https://zed.dev/ , the editor by former Atom devs?

Editors are like browsers, huge amount of upfront work to even get parity with decades old editor and no commercial potential to sell product. Charge a little bit of money and a million of well paid IT workers suddenly become so poor to pay for tools they need for work. They would further spend productive time haranguing maintainers on why editor need to be open source (code word for just free as in beer) or how 60-70 dollars / year is too much for a code editor and so on.

So end result is only editors exist are feature complete long time back/ or maintained by companies who could just give it for free, compensating it with cloud revenues. Besides a couple of paid editors with insignificant market share of course.

Re: Sunsetting Atom

#270

Earlier quoted context omitted.

It all comes back to that "development cycle" and wanting to make that as short as possible. What you suggest is absolutely fine, it's just my personal preference (and something that I've seen help other devs) to make the "write code"->"see results" as tight as possible. If you add any delays, any potential chance of forgetting a step, etc then it breaks my programming flow which can kill my productivity.

But aren't you executing a task either way? Either running a script, or executing a command through Ctrl/Cmd+Shift+P, you have to do something to deploy. I mean, hell, just set up gulp/grunt/another task runner to watch your files and run scp if you want it continuously running? Why involve your IDE at all at that point?

Ahh, I see the disconnect.

I set it up to deploy on save of the file or when the editor loses focus (when it auto-saves). So while you are correct I have to do “something” to make it deploy that “something” is either a hot key or me clicking out of my editor into the browser to refresh the page (talking about PHP here, all my frontend Vue work I do locally with a watch script to rebuild on changes).

Post reply on HN