News for hackers. Stuff that matters.
Re:Slap: Terminal-based text editor by Dolimiter on Tuesday August 26, 2014 @11:38AM (#8227696)
Requires node.js ...

EDIT: oops I'm getting downvoted, sorry for mentioning the platform. For the record, I think that JavaScript is the perfect choice of language for a terminal text editor. I can't think of a single better language and platform.

:|

Re:Slap: Terminal-based text editor by boomlinde on Tuesday August 26, 2014 @12:14PM (#8227945)
I think that what's objectionable about your comment is its absolute lack of information or anything that could possibly contribute to a discussion in any obvious way.

What do we make of Requires node.js...? The sentiment doesn't reflect an opinion, an argument or anything that wasn't obvious from looking at the repo.

Re:Slap: Terminal-based text editor by GhotiFish on Tuesday August 26, 2014 @02:46PM (#8228781)
It's gonna seem REALLY obtuse to install node.js on a machine that doesn't need node.js, just so you can do some regular maintenance.

If there is any value in a terminal text editor at all, it's the ability to operate that editor remotely. Unless the machine has node.js on it already, this is just crufty.

salp's choice of dependencies for what it is, is really oddball. I don't think there's any getting away from it.

I will agree that just dropping a "Requires node.js..." is kind-of a cheap trick. The idea being that people will read what they want and assume that's what the grandparent meant. But just because it's cheap, doesn't mean it's meritless.

Re:Slap: Terminal-based text editor by boomlinde on Wednesday August 27, 2014 @12:38PM (#8233038)
> But just because it's cheap, doesn't mean it's meritless.

It has no merit as a contribution to the discussion (except maybe in the sense that people actually replied to it). For all I care, he could have a very well-founded basis for his opinion, but the fact remains that we will never know that from the body of his comment.

As for your arguments, I mostly agree, but personally I use vim (as opposed to non-terminal equivalents like gvim or macvim) locally since a lot of the work I do happens in a terminal anyway. By using it in the terminal, I can completely avoid managing windows in OS X while I work and either just drop vim to the background or use tmux to do the command line work relatively seamlessly.

Re:Slap: Terminal-based text editor by fiatjaf on Tuesday August 26, 2014 @08:56PM (#8230385)
"If there is any value in a terminal text editor at all, it's the ability to operate that editor remotely."

How can you take this for granted in this Vim world we live in?

Re:Slap: Terminal-based text editor by dllthomas on Tuesday August 26, 2014 @11:59AM (#8227838)
It's not that you mentioned the platform, it's that the ellipsis - in lieu of any other commentary - seemed to itself be commentary on that platform, as if something should follow and the reader should know what.
Re:Slap: Terminal-based text editor by swah on Tuesday August 26, 2014 @03:53PM (#8229143)
No worries, here's the go version :) https://github.com/nsf/godit
Re:Slap: Terminal-based text editor by AlexeyBrin on Tuesday August 26, 2014 @11:41AM (#8227720)
That's because it is written in JavaScript and you need a way to interpret JS on your machine.

I suppose it should be possible to build a self contained executable, similarly with what node-webkit does.

Re:Slap: Terminal-based text editor by matthewmacleod on Tuesday August 26, 2014 @11:40AM (#8227714)
What's the problem with that?
Re:Slap: Terminal-based text editor by bichiliad on Tuesday August 26, 2014 @12:05PM (#8227879)
I think he may be worried that things like Atom didn't do so well, but the lack of a DOM will probably make things much faster.