91–100 of 230 posts
Earlier quoted context omitted.
VS Code is certainly neat, but with the rush to cram everything into it, it's starting to feel more like emacs than vi.
But?
Earlier quoted context omitted.
You really aren't. Atom runs fine on a Macbook Air. There are definitely performance issues, but we're addressing them; it's just that our team is small and our initial goal at launch was to produce the most hackable text editor possible.
I had to drop Atom when it began launching white flashes when scrolling on a 2011 MBA. I saw that this was a recurring problem. Is that an issue that is being addressed?
Earlier quoted context omitted.
VS Code is certainly neat, but with the rush to cram everything into it, it's starting to feel more like emacs than vi.
I doubt any Electron-based editor is going to feel as snappy and light as Vi. Have you been noticing performance decreases? I haven't noticed any.
this is only true if we're strictly talking editing text wihtout any plugin functionality. As soon as you add code completion features vim shows its age, the Ale extension for async linting for example feels very sluggish on a few only slightly dated laptops I tried out and frequently grills the cpu.
Really cool stuff !
Really gave atom a hard try. Back to notepad after a few months. The add-ons are the only advantage, but are grossly overshadowed by the resource consumption this behemoth requires.
Yeah, someone complains about the resource usage in every Atom post. I feel likes it's a rehash of emacs vs vi debate from 30 years ago. Emacs needed many megabytes more than vi so people wouldn't use it. As time goes on the resource usage becomes less of a problem. My 4 year old laptop has 16GB of RAM and I don't really worry about it. I'll get 32GB or 64GB in my next computer. I never liked quibbling over memory. M…
The thing is, this was in fact a valid critique of Emacs back in the day, and it cost Emacs users. I know I stopped using it back then partially because of its resource use (and because it was a lot slower than vi and because of its finger-twisting keyboard shortcuts).
If Emacs was as light on resources as vi was back then, it would have more users today.
Earlier quoted context omitted.
I would guess that tab -> spaces happens locally, and then the spaces are what's sent over the wire. So it would be whoever inserted the tab. (What other possibility could there be?)
Why would spaces be sent over the wire?
What software would you use to provide group voice chat for a screen share session? Discord?
Earlier quoted context omitted.
Yeah, someone complains about the resource usage in every Atom post. I feel likes it's a rehash of emacs vs vi debate from 30 years ago. Emacs needed many megabytes more than vi so people wouldn't use it. As time goes on the resource usage becomes less of a problem. My 4 year old laptop has 16GB of RAM and I don't really worry about it. I'll get 32GB or 64GB in my next computer. I never liked quibbling over memory. M…
Yes, Emacs stands for "eight megabytes and constantly swapping". How silly this sounds today. I wonder why do those people even care. The only time I look at my resource usage is when apps start to behave funny. Or when it's an app that I am developing. Other than that, why should one care? One argument could be made that they are using memory wastefully. Not sure that's the case. The baseline memory consumption is h…
Well, because if an application you're using is constantly swapping, it'll slow that application down to a crawl. This was especially true back in the day when disk was slow (and expensive.. as was RAM).
People today are used to being awash in resources. RAM is fast, plentiful, and cheap. Disks are relatively fast and cheap.
You have to imagine what it was like to live in a resource-constrained environment where you actually had to care about how much memory and disk you used, and how you were using it. These decisions had severe, immediately apparent practical consequences.
I so want this for visual studio code now :) Really cool stuff !
Earlier quoted context omitted.
Microsoft employee here. Today is also the Connect conference. My colleagues who worked on live share knew all along that Connect is their deadline. Which makes me curious, does Github know what Microsoft is going to announce at their conference, or did Microsoft knew what Github is building?
It looks like one of the main authors of atom is presenting today at QConSF too. Seems like dumb luck. :D