Live data from Hacker News

Sunsetting Atom

github.blog

841–850 of 880 posts

Re: Sunsetting Atom

#841

Earlier quoted context omitted.

Sublime Text came pretty close to dying during the Sublime Text 2 years. I recall development slowed down substantially (it was a solo dev, IIRC), and it being pretty surprising when Sublime Text 3 came out.

Sublime Text has never came close to dying. It was only adderal driven developer crowd making mountain out of a mole because they felt uneasy their frigging text editor hadn't been updated every other week.

Ha. Fair point!

Re: Sunsetting Atom

#842

Earlier quoted context omitted.

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…

I would argue that boilerplates should be minimized in the first place. Regardless how fast it is to generate them, reading them over and over again together with the code human write is a huge waste of energy.

I would point out that there are places where having boilerplates is a significant time savings. I'm not disagreeing with you, just pointing out the practical application sometimes outweighs the cons.

Re: Sunsetting Atom

#843

Earlier quoted context omitted.

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.

Just a single advantage, I should allow others that use VS more regularly than I. VS also has all of the same types of things you mention as advantages for VSCode as well.

I'm not advocating for people using it necessarily, just saying it is a really high quality IDE if you need or want to use an IDE.

Re: Sunsetting Atom

#844

Earlier quoted context omitted.

I wrote Java for multiple years in vim with no extensions installed.

I don’t think that is smart

I was more productive than I suspect someone with just an IDE would have been, considering the volume of complex non-coding issues I needed to learn about and solve.

Re: Sunsetting Atom

#845

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…

A new approach with native speed and incorporating LSP and easy extensibility at its core instead of bold-on – as in older editors – sounds interesting. LSP and across-file editing doesn't always fit nicely into the old tab-per-file or view-per-file paradigm. Is there going to be an open-source version with free license available for Zed, or will this be a commercially licensed project?

Re: Sunsetting Atom

#846

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…

We have an entire industry, devops, that opposes this world view. Manual processes, snowflake developer machines, not testing the deploy piece as part of the process, throwing code over the wall for others to validate. I'm not trying to be a jerk, these are just well known and well documented anti-patterns.

Re: Sunsetting Atom

#847
post #736

Earlier quoted context omitted.

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.

I'm tiring of this thread.

I never asked for or requested input on how we deploy code/manage our servers. I was asking questions about an IDE vs vscode and gave 1 example of trying to do the same thing in both of them. Had I known so many people would come out of the woodwork to tell me I'm doing it wrong without any idea of how our stack works I wouldn't have mentioned it.

I have no aversion to running shell commands and you are being disingenuous by saying that. I have a problem with manually doing a step that I can automate. I write and run shell scripts all the time for one-off process but seeing the code I've actively writing in an environment that can run it is not one of those cases. In fact, anyone doing that manually is just being silly or obstinate. If you aren't automating something that you do 100's+ times a day then I question your skills.

Re: Sunsetting Atom

#848
post #150

Earlier quoted context omitted.

> And even if it were, VSCode is basically a rewrite of Atom that reuses a big chunk of the original codebase Atom and VSCode projects have always been separate projects. Both using Electron does not mean they share a codebase, not in the normal sense of the phrase.

If I remember correctly, Electron was made for Atom (by GitHub).

Atom Shell, which was renamed to Electron, was made for Atom. Electron is not Atom. They both use javascript, too, but that doesn't mean they share code.

Re: Sunsetting Atom

#849
post #327

Earlier quoted context omitted.

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

We do have plans. Stay tuned!

Rust on Mac with an open source UI - wow! If nothing else, you guys are ambitious as heck. Can't wait to see more. Also, loved the youtube video you linked to earlier in the comments - great to see an actual working demo instead of just an announcement.

Re: Sunsetting Atom

#850

Earlier quoted context omitted.

I cannot comprehend being blind and developing for my existence. I think I would die, or else become a lecturer .

What an exceptionally unhelpful comment.

It was. I was in a particularly moody state and my filter was gone. It was meant in a way to be sympathetic to the challenges of that situation but is phrased badly. I'd delete it but I can't.
Post reply on HN