Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×
Programming Graphics Upgrades

Atom 1.1 Is Out, With Lots of Graphic Improvements (blog.atom.io) 103

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.
This discussion has been archived. No new comments can be posted.

Atom 1.1 Is Out, With Lots of Graphic Improvements

Comments Filter:
  • 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.

    • by Lisias ( 447563 )

      The thing is useless except by the eventual coder. As long as you need something really sturdy, it fails

      I could not even load 1 megabyte sized files (logs from a system I was analysing).

      The UI is fancy, I give it to them. But even Eclipse is more useful for real life work.

    • Looks like vi to me.
  • Large files were a problem with atom

  • Why Atom? (Score:4, Interesting)

    by mwvdlee ( 775178 ) on Saturday October 31, 2015 @03:21AM (#50837231) Homepage

    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?

    • I find it odd that Atom, the text editor, is built on top of Chromium! As such, it is a 90MB installer under Windows.
    • by DrXym ( 126579 )
      Atom is basically a clone of Sublime and Brackets. So if you like those other editors you'll probably like Atom.

      I use it occasionally because I work on a very mixed project with lots of file types which it handles fairly well. But I don't see the attraction of these editors otherwise. If you edit code all day you should probably be using a proper IDE and if you're just casually editing some random file there are more lightweight editors around.

  • 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?

    • by rocqua ( 4252459 )
      Unlike any modern editor, one cannot open Vim and start typing. Moreover, one cannot explore menus to see what you can do and what the shortcuts for that are. This makes it much harder to learn than modern GUI editors / IDEs.
    • by hey! ( 33014 )

      I think the selling point is extensibility. I've been playing around with it and I detect a great deal of Emacs influence in the editor's features. I think the idea is to provide emacs-like power user features with a basic text editor-like entry level experience.

  • 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.
  • 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?
    • by hey! ( 33014 )

      I think the primary reason is that they want the editor to be extensible using javascript, which of course is possible with a browser based app but then the people doing the customization have to work around browser security policies like single origin which complicate scripting for reasons that don't apply to a native editor.

  • 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.

No amount of careful planning will ever replace dumb luck.

Working...