Slashdot Mirror
Atom 1.1 Is Out, With Lots of Graphic Improvements (blog.atom.io)
yathosho writes with some good news for GitHub developers: GitHub's new Atom editor sees a first big update in version 1.1. Character measurement has been improved, fonts with ligatures and variable width fonts are now supported. The biggest new feature is probably live Markdown preview, matching the current theme. There's also a 1.2.0 beta available, for those who want to have a look into Atom's future.
That's classified information.
It looks like a javascript emacs. Anyone know how it compares in "hackability?" Are there github sites full of javascript mods for it like the elisp ones for emacs?
I'm not a fan of javascript, but I can see this being handy for someone who is.
Those who can't do, teach. Those who can't teach either, do tech support.
That's classified information.
You know too much....
What does "16 bit" have to do with terminals?
Those who can't do, teach. Those who can't teach either, do tech support.
Yeah, lame product that's not open source. Here are some the features they are touting for the latest release, see which ones of these make you want to pay for a closed-source editor:
* Reduced GC Pauses When Scrolling Editor
* Using Variable Width Fonts
* New Approach to Character Measurement
* Several Find and Replace Fixes
* Settings Have Nice Descriptions
They're not really selling me on it. Incidentally, when I read the headline, I thought it meant that Intel's Atom processor had been given a GPU.
"First they came for the slanderers and i said nothing."
I can't comment on Atom (or Xcode, for that matter).
I can comment on UNIX-based editors and IDEs, though.
There's Eclipse's C/C++ module. It runs fine on Linux.
Emacs might suit your needs as well, but getting it set up with all the bells and whistles of an IDE is a bit of a pain. There are projects that help with that, however, like spacemacs (defaults to vi keybindings, but supports emacs keybindings as well). I use emacs with a custom config, but I haven't done much C++ since I switched from vim. What I have done has worked OK, but I'm sure my config has room for improvement.
QT Creator is cross platform and supports C++. It can do non-QT projects just fine.
There's Anjuta and KDevelop as well, but I haven't used either of those in quite some time and have no idea what the status is. KDevelop used to be used quite a bit for KDE development, which is C++.
Those who can't do, teach. Those who can't teach either, do tech support.
wtf is atom?
A somewhat rudimentary slashvertised text editor that reports what you're doing back to Google.
The first UNIX machines were 16 bits, and TTY terminals were the main interface to them.
Lisias@Earth.SolarSystem.OrionArm.MilkyWay.Local.Virgo.Universe.org
Well, yeah, the PDP-11 was 16 bits. The terminals weren't, though.
Given that vi was developed on a PDP-11, I'll grant you the point.
Those who can't do, teach. Those who can't teach either, do tech support.
GitHub co-founder Tom Preston-Werner specifies, only "Atom core" code will be closed source, while "all the existing MIT-licensed repos under the Atom org will remain so forever." The reasons are purely commercial, as he notes: "Atom won't be closed source, but it won't be open source either. It will be somewhere in-between, making it easy for us to charge for Atom while still making the source available under a restrictive license so you can see how everything works."
Keep your wallets handy, peeps.
The whole was open-sourced in May 2014!
See http://developers.slashdot.org/story/14/05/07/1245259/github-open-sources-atom-their-text-editor-based-on-chromium or http://blog.atom.io/2014/05/06/atom-is-now-open-source.html
Large files were a problem with atom
http://saveie6.com/
Incidentally, when I read the headline, I thought it meant that Intel's Atom processor had been given a GPU.
Same, the only reason I clicked was to see how terrible of an onboard GPU they crammed into atom.
Seems your information from 2014 is not relevant any more, supposedly they open sourced all of it in May this year:
http://blog.atom.io/2014/05/06...
New things are always on the horizon
Looks like vi to me.
I'm still wonder why I'd ever want to use Atom.
Sure, it has some nice things in it, but it's still nowhere even remotely close to other programmers' editors.
Nor does it seem to offer anything that could significantly improve on those editors or that would be in any way harder to implement on those editors.
What is so special about Atom and why are Github pushing it so much?
Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
Except the early terminals weren't even 8-bit. Only 6 bits were needed for upper-case only ASCII.
Atom is but the latest in a chain of editors that do the same thing. It adds nothing new over the last cool. I try them all, then switch back to vim, which has all the same, if not more, capabilities and is installed everywhere.
If they want to reinvent the wheel why not a modern wrapper around Vim?
Well, Unix (or Unics. initially) was developed on a PDP-7, which was an 18-bit processor. However, 18-bit processors would typicaly pack 3 6-bit characters to a word. Teletypes, which were an early form of interface used a 5-bit code. Common VDU-style terminals used 7- or 8-bit codes. I'm not aware of any (western) devices that used more than 8 bits.
I thought it was Atom RSS, that by the way, is still at v1.0.
May of 2014, actually (the blog entry you linked to is dated May 6, 2014)
A lot of Windows users woke up yesterday unable to work on their code because some projects would open and immediately crash. Their github is full of reports.
* Using Variable Width Fonts
I would actually be interested in this, if it comes along with smart tabs. I was initially sceptical of Stroustrup's claims in his book that code (like everything else) is more readable in a proportional font, but I checked the research and he is correct (in objectively measurable ways). I'd love to have an editor that:
Atom, Vim, and EMACS all support some overlapping subset of these. I've not yet found an editor that supports all of them.
I am TheRaven on Soylent News
My mistake.
New things are always on the horizon
Atom is completely built upon web technologies -- javascript, chromium, etc. It even phones home to Google analytics. It seems bizarre to have it solely as a desktop application -- why wouldn't this be implemented as a web app, or at least as a Chrome extension?
Emacs with vi keybindings? Clearly they just like to watch people argue...
My first program:
Hell Segmentation fault
hmm i'm trying to do :wq but no command line appears. thus no search and replace either. no proper visual block selection. yeah, this vim emulation isn't for me.
Getting Emacs set up is a good bit better since they added package support. You can mostly just package install a bunch of packages and they seem to work sensibly. Stuff like vi style paran matching in edit mode takes a bit more work, but there's a function you can bind to a key on the Emacs Wilki.
I'm trying to teach myself to set people on fire with my mind... Is it hot in here?
Yes, except for the "more roundness" part. Lots of better editors out there, plus they don't have the downside of being on the other side of a WAN connection.
Too bad Github doesn't find it worthy to improve their markup handling. Markdown is really, really limited, and their mechanism for supporting other markup comes with designed-in inertia that makes it impossible to use for markup-projects. You can't change fonts, the <TT> tag is bedeviled by a visual style that changes its backdrop color, you can't use different fonts, you can't use different font colors, (imagine trying to document examples of font color change and font face changes with those limitations), you can't do image captioning worth a darn, much less embed them sanely in the context of the paragraph that references them...
I understand why they want to limit scripting on site; but fonts??? FFS.
I did one fairly large set of docs in Markdown so as to get familiar with the territory, as it were. It was a huge waste of time. The more I learned, the more limits I ran into. And Github... they were... less than helpful.
I don't mind posting my open source stuff up there, but I won't be putting any more documentation for same on the site in a "you-can-read-here" format unless they step up to the plate and handle custom markup schemes on a per-repo basis.
I've fallen off your lawn, and I can't get up.
I'm sure it's better (I didn't use emacs before packages), but going from vanilla emacs to working IDE still takes a quite a bit of research and work.
Company or ac? Ido or Helm? Built-in CEDET, development version of CEDET (hope you don't do scheme development, 'cause semantic shits on it), or clang-based autocomplete? CEDET project management or projectile? Don't forget flymake - oops, that's outdated, now use flycheck, but wait, that's not compatible with...
Emacs is great, but for someone like OP who is used to "install xcode and run with it," roll-your-own probably isn't the way to go. That's why I mentioned spacemacs.
Those who can't do, teach. Those who can't teach either, do tech support.
Ever heard that saying, "Emacs is a great OS but it lacks a decent text editor?" Well, thanks to evil-mode, now it has one.
I haven't seen much argument about evil-mode vs vanilla emacs. I think the consensus is pretty much, "it's all emacs." Emacs users generally customize their keybindings anyway - evil-mode is just a bit more extreme than most.
As for me, I like vim. I instinctively use vi keys when editing. However, I need custom scripts for some of the work I do, and I hate vimscript. Emacs gives me an editor that uses vi keys but lets me do customizations in elisp. It also has some other kick ass features I've come to like (org-mode is amazing). I still use vim for quick editing and sysadmin type stuff, but I write code and documents in emacs.
Those who can't do, teach. Those who can't teach either, do tech support.
It's the most basic particle that constitutes all matter, and is composed of protons, neutrons and electrons.
It is also the name of an entry level CPU line from Intel. In fact, seeing this headline, I was under the impression that Intel had tossed in new GPU functionality into the Atom
It's a text editor, built with web-based technologies and packaged as an app-specific browser that looks like a native desktop app, which offers a user experience similar to most desktop programmer's editors but with emacs-like extensibility (only in javascript rather than elisp).
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
I was initially sceptical of Stroustrup's claims in his book that code (like everything else) is more readable in a proportional font, but I checked the research and he is correct (in objectively measurable ways).
I don't have trouble reading code because of the font, so that is a non-issue for me. When was the last time you had trouble reading code because it was fixed-width? However, a proportional width font makes things extremely difficult to line up vertically. Tabs help a little, but often I want to line things up on a non-tab-stop point.
"First they came for the slanderers and i said nothing."
If it's anything that is actively developed, I don't read anything unless I can see a date somewhere in the google search blurb.
Laws are rules for the court, but merely a bottom bar to hit for life. Think beyond laws in your actions always.
I don't have trouble reading code because of the font, so that is a non-issue for me
Define 'trouble'. Comprehension is not a binary thing. It's relatively easy to measure reading speed and retention. There's a lot of research showing that proportional fonts (and syntax highlighting) increase both, for all test subjects, including the ones that claim before the study that fixed-width single-coloured text is the best for them. Most of these apply equally to natural language, yet programmers insist that code is special and magical. This is even true of syntax highlighting - tagging different parts of speech in natural language has improves both reading speed and retention by 5-10%.
However, a proportional width font makes things extremely difficult to line up vertically
Nonsense. Tabulators exist for precisely this purpose. Oh, and read the rest of the post that you're replying to.
I am TheRaven on Soylent News
omg closed source means terrible eeeek
Actually, it means not free. Obviously freedom isn't something you value.
"First they came for the slanderers and i said nothing."
Define 'trouble'.
Meaning, being able to read faster would not help me in any noticeable way. When it comes to understanding code, deciphering character shapes is not the bottleneck. I solve that problem in milliseconds, then can spend minutes or hours or days trying to understand it.
"First they came for the slanderers and i said nothing."
Meahnwhile I switched most of the syntax highliting in Java/Groovy/C++ off. ;)
At least the colours I switch off.
I find 'modern' syntax highliting more causing eye cancer to me than helping in any way.
Regarding reading speed: I doubt you can make me read faster by any swich in fonts etc.
You can make me read slower perhaps, e.g. while I can read Fraktur, I prefer ordinary letters, and especially I prefer sans serif above seriv fonts.
The only colour highlighting I did not switch off yet is the 'desert' theme in vim for Shell scripts.
But I'm working on that
I would assume if tests show better reading and better retention even, the test subjects are 'relatively' bsd readers?
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
I met with some friends yesterday, to either found a new company, or work as a team of contractors for a potential customer. ... Emacs? I tried it a few weeks, because I did not know about VI. Some retarded teacher thought Emacs is the best thing. But I could not stand to have to write all key-board-short-cuts on a piece of paper and look them up every few minutes *again* because they are completely unmemorizeable. ... I have to relearn vim/vi every time I start working as admin/devops again because I use it to rarely on my macs.
That customer is is notorious for having a multiple choice/written test about computer science topics.
The story goes that the typical 'high flyer' manages to answer 20 - 25%?of the questions correctly in the alotted time.
A russian guy answered everything, correctly!, in half the time and was asked if he need help (as it was assumed his german was to bad)
Anyway this morning, I thought to myself: when the mandatory VI vs Emacs question comes up, I could make a joke: Emacs with a Vim mode.
A few hours later it pained me, and I googled for Vim mode for Emacs, and figured it was not a good joke, considering the amount of hits.
Alas, I use Vim only for Unix stuff, and an IDE for 'real programming'
Anyway
However it is quite fun as everything is so 'round' and 'wholesome' thought out in it.
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
I don't know if this can be fixed, seeing as how it's based on Electron and therefore a Chrome Browser, but I would hope that it would use less RAM and take up less room on the hard drive.
Democracy Now! - your daily, uncensored, corporate-free
Emacs and vi are mostly useful to people who have to edit a lot of text. If you're only editing occasionally, or you usually use a "normal" editor, you'll never learn them.
I learned vi because I was a sysadmin and worked with UNIX all day. Every UNIX machine has vi, and it used to be common for it to be the only visual editor on the system (especially if you were working with commercial UNIX like HP-UX or Solaris, like I was). I would never have put in the time to learn it otherwise - I was happily editing files with pico before I learned vi.
I only learned emacs because of vi - I needed something with the power of an IDE, a good macro or scripting system, and vi keybindings (my fingers have hit the escape key three times so far while editing this comment - it's burned into my brain). Editing text was the primary part of my job. Emacs with evil-mode does that for me. Of course, I had to learn elisp, but I'll take that over vimscript any day. I find I actually enjoy the language.
Those who can't do, teach. Those who can't teach either, do tech support.
I use Atom (and TextMate before that). It works fine with rmate, just have to do port forwarding on ssh. I use the rmate bash script so I don't have to install anything else on remote servers.
SWM seeks new sig for a brief fling
Yeah, understandable. Neither vim script nor the vim rc file really looks easy, that is an area I never will really dig into. ... regardless what language.
Under those circumstances I understand why people write new editors that are scriptable with java script.
Nice on unix however is that you simply pipe some part of your edit buffer through external commands
Standard Emacs is incomprehensible to me. I can't get what sick mind desided on the keyboard short cuts.
In vi/vim however as soon as you have learned the basics, you easy discover new commands yourself.
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
Standard Emacs is incomprehensible to me. I can't get what sick mind desided on the keyboard short cuts.
The same sick mind that used to spend a lot of time working with Symbolics LISP machines. Look up the "space cadet" keyboard sometime.
The tutorial really tries to get you to ignore the special keys on your keyboard. Page Up/Down, the arrow keys, Home, and End all work fine in Emacs, but the tutorial will have you doing C-v, C-n, etc. That makes sense if you're working with antique terminals. It doesn't make much sense today. Except for the glaringly obvious cut-and-paste commands, for normal use it acts more or less like any "normal" text editor.
There is some semblance of sense in the default keybindings. C-x is full of (usually) global functions. C-c is for mode-specific keybindings. Very common things have their own single combination keybindings (movement, saving, cut/paste, etc.). There's also some really confusing ones that require you to understand how Emacs works (like C-u for "prefix argument" that does different things to different commands). And of course, C-g, which stops Emacs from doing whatever it's doing to piss you off at the moment.
Honestly, I don't bother with most of the Emacs keybindings. I've memorized the ones I need (like C-c C-e l o to export an org-mode document to pdf) and use the vim equivalents for regular editing. I've got evil-leader installed, which will let me bind functions to the comma (as in, ",e" to export to pdf), but I never get around to actually setting it up.
Those who can't do, teach. Those who can't teach either, do tech support.