The more I see new editors floating around, the more I'm sticking to VIm. I am getting old, or it's a just a survival instinct. On the other hand, the more the better, but we have already too many editors around.
I've sworn by SublimeText until now. And Atom is getting released during a time when I'm increasingly learning to love console-only computing. I envision a day when I can travel the world with a cheap laptop/chromebook and do all my coding remotely via SSH.. and Vim is very much at the core of that dream. Now I just have to master it.
Atom
181–190 of 662 posts
Re: Atom
#182Earlier quoted context omitted.
Welp, makes that decision easy. Not making the most important tool in my toolbox one that I can't hack to my liking.
But in some degree you can't hack the heart of Emacs and Vim as well: its too complicated.
Re: Atom
#183Earlier quoted context omitted.
> Atom is free during the beta period. Where does it say it won't be free after the beta period?
Well, one can only assume, based on the wording they use here: https://github.com/atom/welcome/blob/master/lib/welcome.md > Atom is free during the beta period.
Re: Atom
#184There's real opportunity here for Github and I hope they take it. Why is the basic workflow of the modern-day programmer split over multiple tools and over multiple systems? Aspects of Github could be modularised and added to the editor while still keeping the underlying tool simple and this could change our user experience for the better. Imagine flipping through your pull requests in the text editor and then seeing…
Re: Atom
#185No mention of supported platforms, but the documentation refers to keyboard shortcuts like "cmd-shift-P". This isn't Mac-only, is it?
I just got an email inviting me to download the beta. The only download link in there is a button labelled "Download For Mac".
Re: Atom
#186Earlier quoted context omitted.
I've sworn by SublimeText until now. And Atom is getting released during a time when I'm increasingly learning to love console-only computing. I envision a day when I can travel the world with a cheap laptop/chromebook and do all my coding remotely via SSH.. and Vim is very much at the core of that dream. Now I just have to master it.
Try using the Vim plugin (Vintage or the newer one, Vintageous) with Sublime. That way, you can gradually get used to modal editing. I worked like that for 8-10 months then made the switch to Vim. I've gotten so used to modal editing (not to mention window management etc.) by then, that I didn't even skip a beat.
Sublime never gave me a reason to go all the way, though :p
Re: Atom
#187I was all ready to be skeptical and everything... but this could actually be amazing. I currently use Chocolat for code editing, which is beautifully elegant and I love it, but there are 25 little tiny things that I really wish I could fix. I file issues, but the developers rightly have their own priorities. It's closed-source, but even if it were open source, I'm not about to learn how to use XCode and Objective C a…
> and there's no compilation step or anything -- then it's almost a fundamental paradigm shift for what desktop software could be. > It already makes me dream of a word processor I could hack like that, or a music player. Just by opening up a text editor. It's an inspiring thought. Not to rain on your parade or anything, but you can already do this with Emacs, not to mention that Emacs is free, open source software.…
Far more people can program in JavaScript than Lisp, and far more people use GUI desktop software that follows traditional GUI user-interface paradigms, than do things inside their terminal. (Edit: or terminal-style buffers/frames.)
So that's why my statement was limited to what "desktop software" could be. :) I mean, I use LibreOffice, which is FOSS, but I am never going to touch its code in a million years. The cost-to-benefit ratio is too high. But Atom makes doing that sound almost trivial. That's the paradigm shift.
Re: Atom
#188There's real opportunity here for Github and I hope they take it. Why is the basic workflow of the modern-day programmer split over multiple tools and over multiple systems? Aspects of Github could be modularised and added to the editor while still keeping the underlying tool simple and this could change our user experience for the better. Imagine flipping through your pull requests in the text editor and then seeing…
Why is seeing your friends comments and code reviews in the text editor any better than seeing them in the browser? Are we becoming this lazy? or this busy?
Re: Atom
#189There's real opportunity here for Github and I hope they take it. Why is the basic workflow of the modern-day programmer split over multiple tools and over multiple systems? Aspects of Github could be modularised and added to the editor while still keeping the underlying tool simple and this could change our user experience for the better. Imagine flipping through your pull requests in the text editor and then seeing…
IDEs, while they have fallen out of favor somewhat in the web development community, offer such a "holistic" development experience already - complete with deep integration into GitHub, in some instances.
Being modularised allows the basic user experience to be kept very simple. It does not need to grow into something like an IDE. Hell, according to Packages [0] even tools like find-and-replace have been modularised so I do not think it follows that Github would carelessly decide to create a big ball of mud!
And additionally this tool has removed barriers that previously existed before.
Since it was created by Github they will be able to expose APIs to create features which are currently not possible.
Likewise the UI being implemented with WebKit means that the user interface can tightly represent what a user is used to seeing at different stages of their development process.
You might have read "The Design of Everyday Things" [1] before. There are certain elements which you need to control to create a good user experience: (1) discoverability, (2) feedback, (3) the conceptual model, (4) affordances, (5) signifiers, and (6) mappings. Without ease in changing the UI, and the possibility that Github will have self-interest in exposing extra APIs, it would be a lot more difficult to control for each of these.
It's just an opportunity to try new ideas. I'm not suggesting that this would be preferable to everybody.
[1] http://www.amazon.com/Design-Everyday-Things-Donald-Norman/d...
Re: Atom
#190There's real opportunity here for Github and I hope they take it. Why is the basic workflow of the modern-day programmer split over multiple tools and over multiple systems? Aspects of Github could be modularised and added to the editor while still keeping the underlying tool simple and this could change our user experience for the better. Imagine flipping through your pull requests in the text editor and then seeing…
Why is seeing your friends comments and code reviews in the text editor any better than seeing them in the browser? Are we becoming this lazy? or this busy?
Plus, it's cool.