Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Moving Atom to React

blog.atom.io

Post reply on HN
Print view View original

111–120 of 142 posts

Re: Moving Atom to React

#111

Post by kalops »

TheZenPsycho wrote: post #108
silversmith wrote: post #100

Earlier quoted context omitted.

This just shows how hard it is to please everyone - when I was using ST, disabling the open file persistence was the first thing I did. My usual workflow has me editing / looking up information in many different files, usually just a bit here and there, so at least once every two hours I'd cmd-q the whole mess and `e .` in the project directory and re-open the files as I need them.

I think it just shows that you do computers wrong. Okay sorry that sounds snarky and unproductive- What I mean is, as a model for how human evolved navigation works- a persistant work space with effectively no need to "save" work is more like reality. If you scribble something on a napkin, and leave it on your desk, the desk doesn't demand you name the napkin when you try to leave the house. At the exact moment you n…

actually, several programs of the OSX stack behaves like this, take the Notes app for example

Re: Moving Atom to React

#112

Post by Dewie »

taeric wrote: post #58
elwell wrote: post #20

Not trying to start an editor war, but I've been trying to learn Emacs for the past week. The learning curve is still at the point of being frustrating/painful. Should I stick with it or download Atom? (Anyone have a solid opinion between the two?)

When you say "trying to learn", what do you mean? If you are trying to dive into everything that emacs can do, I'd imagine you will be in a world of pain for quite a while. Instead, just use it to edit files. After a while, if there is something you are finding would be convenient, search for and or build it. That said, some obvious points that you will find nice do come by default if you start out with something lik…

I'm still an emacs rookie, but I've already been 'converted' to the point that I try to use emacs every time I need to write text - programming (at least if no IDE is available), text files, LaTeX (what little I've written of it, anyway), word processing if it is feasible to write the text in the editor and then copy paste into a word processor to do the formatting later, editing text boxes in web browsers via a Firefox plugin (`It's All Text!').

The primary reason, at least for non-code text, is that I find it annoying to go back to using stuff like the arrow keys for navigating now that I'm kind of used to the arguably more ergonomic C-f, C-b and friends. So I can echo the sentiment that sticking to the basics of emacs at first can be well worth it.

Re: Moving Atom to React

#114

Post by xienze »

adrusi wrote: post #79
xienze wrote: post #76

Earlier quoted context omitted.

Log files.

I'm curious, do you really need a text editor for log files? It seems like the wrong tool, after all, you're not editing your logs. I have never found a case where `cat example.log | grep Error | less` is insufficient. Granted, I think a good editor should be able to handle files of any size, but if atom sacrifices that for the ability to let an extension display anything it wants inline with the text, it doesn't see…

> I'm curious, do you really need a text editor for log files?

Well, it doesn't always boil down to "grep for one specific thing." Usually you find one thing, then you have to locate the next couple instances of it (I use vim, so I'm used to just doing nnnnnnnn... to keep finding the next occurrence). Or perhaps you grep for one specific thing, find out something is related, need to search for some other thing, etc. Maybe you need a little bit of context around the thing you grepped for. Text editors work pretty well for combing through log files...

Re: Moving Atom to React

#115

Post by Kiro »

exogen wrote: post #70

The new rendering method kills subpixel font rendering, I suspect due to the translate3d hardware acceleration. Unfortunately noticeable for those of us not yet on retina-resolution screens.

So it's a change for the worse in other words.

Re: Moving Atom to React

#116

Post by Kiro »

exogen wrote: post #70

The new rendering method kills subpixel font rendering, I suspect due to the translate3d hardware acceleration. Unfortunately noticeable for those of us not yet on retina-resolution screens.

So it's a change for the worse in other words. This should be the top voted comment.

Re: Moving Atom to React

#117

Post by currysausage »

srcreigh wrote: post #78
rdtsc wrote: post #74

Earlier quoted context omitted.

I tried and it didn't make sense to me. Having to switch modes is silly to me. > For example, if you know how to jump to the next occurence of character x (fx), you already know how to delete from cursor to character x (dfx). Yes but if I have to start typing I have to press some key to switch modes (i?). That is a no-go for me.

Well, there's no perfect solution. Either it's a modal system like vi, or you have to use modifier keys whenever you want to do something that isn't enter text. That said, there are tricks to make modal editing less annoying. For example, mapping your CAPS LOCK key to ESC makes switching out of insert mode much easier. Some commands perform actions and then switch modes all at once for you. To extend the grandparent…

Minor nitpick: c is delete and switch into insert mode, so it would be cfx.

Re: Moving Atom to React

#118

Post by Cthulhu_ »

toxicFork wrote: post #67
flyrain wrote: post #66

Why we need another editor? We already have vi, emacs, st, ... Why Atom?

Why do we need cars when we have horse carriages?

Maybe more like why do we need electric cars when we have petrol engines, maybe? IDK.

Maybe we just don't need it, but it's nice to have a different approach / a choice.

Re: Moving Atom to React

#119

Post by cbp »

kolev wrote: post #30

I've used React since it became available and the editor is still pretty slow, to be honest. Can't imagine using it with the option enabled. Honestly, Sublime Text is great, I've purchased a license, but the speed of development will kill it. Every day I "Check Update" and I get disappointed. Not that it needs that much new stuff, but still. You don't feel the heartbeat, if you see what I mean. One great feature of S…

Use emacs and melpa and you'll really feel the thrill of constant updates.

Re: Moving Atom to React

#120

Post by jackweirdy »

shurcooL wrote: post #62
Sir_Cmpwn wrote: post #43

This is a natural consequence of forcing an editor into the browser. Everything about Atom just seems so unneccessary to me. What's compelling about Atom that draws people in, compared to Sublime or even vim (my editor of choice)?

> compared to Sublime It's open source; Sublime isn't. I can't do anything to make Sublime better.

Except for writing plugins in a way that seems to be tacked on at the end - whereas atom's packages are at the core of the editor.
Post reply on HN