Were Microsoft and Github using some kind of collaboration tool? Calendar syncing perhaps?
Code together in real time with Teletype for Atom
101–110 of 230 posts
Re: Code together in real time with Teletype for Atom
#102Earlier quoted context omitted.
Personally I don't mind RAM usage that much. I'm more concerned about excessive CPU usage resulting in unnecessary battery drain on my laptop or annoying fan-spinning.
Atom for me consistently sits at 0-0.1% (mostly 0) CPU usage when idling. You may want to investigate some of the extensions you're using if the numbers are different for you.
It's probably not idle CPU usage that the parent is complaining about.
Re: Code together in real time with Teletype for Atom
#103Is it only a coincidence that real-time collaboration is being announced both for Atom and VS Code ( https://news.ycombinator.com/item?id=15704376 ) at the same time?
Why is there breakneck competition here to offer the best free code editor?
Ballmer's Law: "Developers, developers, developers." If you want to be a platform vendor, you need to have developers. Lose the developers and you lose the business.
Microsoft has been a platform vendor for a long time. VSCode is part of their argument for why they should continue to be one.
Re: Code together in real time with Teletype for Atom
#104This looks really neat. As a side note, it bothers me a bit that they haven't used an actual URI, e.g. tty:xxxxxxxx-xxxx-... That would allow for nice hyperlinks from web pages and chat rooms.
Re: Code together in real time with Teletype for Atom
#105Earlier 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…
A text editor using 600 MB of RAM to open a file is ridiculous. That with a couple of Chrome tabs grinds my laptop to a halt.
Re: Code together in real time with Teletype for Atom
#106Earlier 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.
That VS Code is not Emacs-like, that’s my problem with it. In my experience nothing beats Emacs at editing text. Vim has better shortcuts, but Emacs is just smart about everything. My problem with Emacs is that it’s showing its age, it’s hard to configure and you have to learn an old and obscure LISP dialect for it. On the other hand I’ve heard that VS Code plugins are a joy to develop, MS apparently did a good job a…
> you have to learn an old and obscure LISP dialect for it
As someone who is glancingly familiar with emacs (I have only ever written one elisp function, that too with help) it's a really stupid question, but couldn't emacs have bindings for lua or python or something? That would increase the number of people who can program for it and customize it.
> in 20 years from now Emacs will still be around
I think the real risk for emacs is, over the years, slowly losing the pool of people who care enough to contribute to it -- not just core developers, but also people who write packages, themes, etc. I already see a lot of developers who think Atom / VSCode / Sublime Text is "good enough". You may choose to discount Sublime because it's closed source (I do despite loving it otherwise), but VSCode and Atom are open-source and browser technology is only going to get better.
Re: Code together in real time with Teletype for Atom
#107How does this work? Does the code that is typed go through a cloud service? I guess that would stop a lot of people using it in work.
Re: Code together in real time with Teletype for Atom
#108Earlier quoted context omitted.
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…
A text editor using 600 MB of RAM to open a file is ridiculous. That with a couple of Chrome tabs grinds my laptop to a halt.
Why? Unless that pushes you to swap, that is not the cause for your slowness.
Re: Code together in real time with Teletype for Atom
#109Amazing! Love it :)
Re: Code together in real time with Teletype for Atom
#110Earlier quoted context omitted.
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…
"Yes, Emacs stands for "eight megabytes and constantly swapping". How silly this sounds today. I wonder why do those people even care." 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 c…
Sorry, I wasn't clear enough.
What I meant to say was that "eight megabytes" sounds silly today. Who cares if an app uses 8MB today? The extrapolation is that it will be the same for Atom or other editors (I'd argue that it already is).
I created my first programs with a computer which had exactly 28815 bytes free when it booted up (out of a possible 64k). If you plugged in a floppy drive, the free memory dropped further.
So, I do understand resource constraints.
Btw,