Anything built on elecyron should be archived asap
Atom was archived today
241–250 of 614 posts
Re: Atom was archived today
#242It might sound controversial, but for me Atom was almost a 1 to 1 Sublime copy with worse performance and quality. It was slow and ugly. It’s only quality was that it was 0$. It was the first editor I’ve seen to choke when opening 1M file (it even had a warning that it’s a too big file - lol). There simply was not enough RAM in the world for this memory hog. I’m not really sad to see it go. It was another free toy of…
Both Sublime Text and Merge are great and well worth the price for me :)
Re: Atom was archived today
#243Earlier 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.
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.
I didn't try during beta because I was convinced VSCode would never take off. Boy was I wrong :D
Re: Atom was archived today
#244Used to love Atom back in the day, thanks for everything team.
Re: Atom was archived today
#245Earlier quoted context omitted.
whoa, a whole 4 years ago!! ;-) i want to make a "kids today" joke/comment, but it's more of just the pace of trends/fads not the people per se. you show up at a new job and the people make comments, of course you change. i've never used Atom, so maybe it was a better thing to change, but i've been introduced to some very ingrained workflows that just no longer made sense on so many levels. you can come in guns blazi…
Somewhat unrelated, but why is it that when someone online writes an emoji with a nose, ie ;) vs ;-), I can immediately tell it's an older person? Was that something that was taught back in the day?
Yes.
(Damn, it's hard to find a "list of emoticons" (or even "usenet faq") from back in the day now. So much more recent stuff clogging the search results.)
Anyway, this list of emoticons from '94 (according to the internet archive) is a pretty good representative of the sort of thing that people passed around then:
https://ia802801.us.archive.org/view_archive.php?archive=/23...
As you can see, most have noses.
Also, RFC-1855 (Netiquette Guidelines) from October '95 has one example of a smiley in §2.1.1: "Use smileys to indicate tone of voice, but use them sparingly. :-) is an example of a smiley (Look sideways)." I suspect that at least one of the bibliographical references provided would have contained a decent list of them at the time, but so many links are dead now. (And even if some of the ftp ones still exist, most browsers have dropped ftp support now, so most people are kinda SOL there anyway.)
Re: Atom was archived today
#246Can someone tell me why OSes can't do what browsers do? It seems to me that browsers are the OS of today so why not just skip the middleman and make it first class? It seems to be a layer that exists solely because the 3 competing OSes is incompatible and browsers just happen to be compatible (for how long?).
nothing these days is really stopping you from making a cross platform native gui app, like with Qt, wxWidgets or similar. The only reason you wouldnt do it is because a lack of skilled programmers, and/or time.
Ive built quick little apps in Qt or wxWidgets for my wife, they use a few MB at most, they don't use any cpu unless you click on them (because naturally, theyre suspended), and the code bases are incredibly concise.
It really is, as gen z would say, a skill issue.
Or, said the other way around: Its simple and easy to use, and as a tradeoff you get no performance.
Re: Atom was archived today
#247Such a shame.
Atom was (is?) great. The first editor extension I wrote was for it (in Coffeescript, no less. Terrible idea in hindsight).
Thanks for the good times.
Re: Atom was archived today
#248Earlier quoted context omitted.
Atom predated the LSP and leaned heavily into customizations with all the plugins running inside the UI thread (more like a traditional web page and 3p scripts). At the time they viewed the extreme customization support as a feature, and there was a thriving ecosystem of folks making plugins. That architecture has a major flaw though. A default install was fast, but a real configuration with all the plugins ended up…
VSCode is one of the greatest pieces of engineering of our time. It's really only when you compare it with Atom that you realize how great it is. Atom was built by incredibly smart people, who had full control over the platform and several years of head start, and they were still out-engineered by the VSCode team at every turn. VSCode did almost everything right: The choice of TypeScript as the base language (with wh…
I disagree, even I use it myself, for those reasons:
- plugins are a mess - when working with tech x how do I know from that huge list which plugins to use
- keyboard shortcuts don`t work out of the box in my Ubuntu system
- The ui feels non intuitive and overbloated to me - even IntelliJ Idea feels more clean and easy to use
- I would love if VSCode could detect the technologies my project uses and just install/use the proper plugins for me. And maybe even without asking me so I could be happily writing code, building, running tests and doing debugging right from the start wether it`s Rust, Kotlin + Spring Boot, Node + Typescipt whatever... sadly its not working like this...
Re: Atom was archived today
#249Sad to see this go. I was an early adopter of Atom, and I wrote two extensions for it, one of which while it was still in beta. The Atom developers made some technology choices that in retrospect were ill-advised, CoffeeScript being the worst of them and splitting everything into dozens of packages a close second. They tried to backpedal on both of these later on, but by that time VSCode, with its far superior engine…
I tried Atom for a while in Windows, but a file watching bug made it quite inconvenient. Every time I edited and saved a file in another IDE (at the time, I was stuck using it to compile and debug an embedded system), that IDE would rename the original to a temporary file in a temporary directory before writing the new version. Atom would follow the rename rather than re-load the new file at the original path. It wou…
What editor did you go for after that? I still use Atom (I don’t need an IDE that much)
Re: Atom was archived today
#250Earlier quoted context omitted.
Exactly. The truth is that over that last 15+ years _most_ of the apps that people use _most_ of the time are a perfect and natural fit for the web UI/UX: text, media, hyperlinks, standard form/window controls, with relatively modest standards of performance and responsiveness, etc. Assuming developers avoid resource leaks (and to be fair some notable Electron-based apps tend to be both leaky and long-running) the ma…
I have never, in my life, used an electron program that isn't irritatingly slow on my main computer. Yes, it's not something you'd probably call a fast computer (4th gen i3, 4GB ram), but this same computer doesn't drop a frame in equivalent native programs. Most of the time the CPU is almost idle. I have nothing intrinsic against electron, and I'll take everything back if I see these "natural fits" actually fit.
It sounds like your 8 year old computer can't keep with today's technology. If it's possible, might I suggest upgrading your computer? A more modern system would let you run Electron apps without being irritatingly slow. It seems silly that I had to upgrade my laptop in order to run a text editor, but it seems that's just the world we live in.