So where do I get that nifty terminal they were using in the video?
yeah wow, they put some work into building that 'prop' heh. Jetsons? Needed an octocat 'Rosie'
Atom 1.0
171–180 of 459 posts
Re: Atom 1.0
#172Earlier quoted context omitted.
Yeah this is crazy. I regularly work with log files in the 100mb to 300mb range which open perfectly fine in Vim/Sublime. If I had to invest time in learning Atom I'd have to multitask between editors for certain use-cases. Maybe if they could switch to a light-weight read-only type of text "viewer" for large files, that would even work. But I really do need to open big files on a weekly basis.
Do you really want to open log files in a code editor? It's not unreasonable to say that these are two different classes of programs, with different basic requirements.
A code editor that doubles as a text editor is major benefit, especially if you're needing to consume logs while testing.
Re: Atom 1.0
#173Earlier quoted context omitted.
Welcome to what I've felt with Emacs since I first used it. Might be time to work on some tutorials and examples to make Emacs easier to hack on and contribute to...
Yes. I keep trying to like Atom because I want to have native WebView buffers while I'm editing. Every time I try it, I end up wondering how anyone can be comfortable using it. I'm not sure how much of that is due to instability that will be fixed over time, and how much is because I'm coming from Emacs. Have any experienced Emacs users found that Atom makes them more productive in any dimension? I want to like it bu…
>Have any experienced Emacs users found that Atom makes them more productive in any dimension?
No. Emacs is far and away superior. It doesn't have a flashy web UI, but it is better in every way that matters.
Re: Atom 1.0
#174So where do I get that nifty terminal they were using in the video?
It's here at CodeConf!
https://gist.github.com/jssjr/018717ddcb81b76e1829#file-img_...
Re: Atom 1.0
#175The killer feature of Atom to me is the ease with which it can be extended (via packages) and the openness to community contribution on core features. That's not a knock against any other editor (some of which share similar characteristics in this regard) – it's just what draws me to Atom. It's super easy to hack on and contribute to.
The trick is to not pull them into core. Let others curate a set of high quality plugins. This is exactly what is happening. Examples include Microsoft's Visual Studio Code and Facebooks Nuclide.
This pattern is also not uncommon. There are many high quality linux modules and distributions built on the linux kernel.
It is likely atom will take a similar architectural approach. Make it easy to build and add plugins and let the community shepherd them.
Re: Atom 1.0
#176Earlier quoted context omitted.
I use emacs but might try atom when it's a true replacement possibility. How can I know it's crossed the threshold?
I'm really looking forward to emacs-like tab behavior and also now that the rate of change will slow down we'll likely see the best quality extensions rise to the top and stabilize a bit. Also looking forward to seeing Facebook's fork of Atom for React...
apm install nuclide-installer
it seems to run inside of Atom, not a fork
Re: Atom 1.0
#177Just tried to install Nuclide and Atom complained about atom.io being unavailable. Guess I know why now.
Re: Atom 1.0
#178I am a paying customer of Sublime Text, but I will give Atom a try. They both seem really similar feature-wise, but Atom is open source, something I care about. Also is based on web technologies, which is really cool (although I've heard it's not so fast).
Just recently started switching for ST2 -> Atom. Key things were:
- either I am getting slower or Atom is getting much faster, - some things with linting for ES6 don't work in ST2.
However, for some tasks I need to open bigger files, and for them I still use ST. It's just sad it didn't go open source... (now it is too late).
Re: Atom 1.0
#179I am really tempted to give it a try but I am already all setup with Brackets and I am having a hard time understanding what are the benefits if I make the switch over Atom. I will surely give it a try a some point!
Re: Atom 1.0
#180The killer feature of Atom to me is the ease with which it can be extended (via packages) and the openness to community contribution on core features. That's not a knock against any other editor (some of which share similar characteristics in this regard) – it's just what draws me to Atom. It's super easy to hack on and contribute to.
It's the Cycle of Bloat. 1. Develop tool. It's small and fast and minimal! Woo! 2. It's easy to modify because it's so small! Woo! 3. Look, there's a budding ecosystem of packages! Woo! (Let's not talk about the fact the packages exist precisely because the original product wasn't big enough.) 4. Oh dear, some of them conflict, a lot of them suck. Well, here's some winners, let's pull them into the core. Now the base…
This is true for some projects, but with atom you can strip away core packages as needed. Just go to settings and disable!