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

Neovim

github.com

Post reply on HN
Print view View original

171–180 of 372 posts

Re: Neovim

#171

Post by stusmall »

jnbiche wrote: post #153
nousernamesleft wrote: post #149

Earlier quoted context omitted.

Go has absolutely no claim to being C's successor. It is useless for all the things it makes sense to use C for. That's why it has attracted virtually no C programmers. Go is python's successor if user influx is anything to judge by.

That's a fair argument. Neither Golang nor D give you the control that C gives you. If that's your yardstick, then the only viable candidate at this point is Rust. But Rust doesn't feel or look anything like C, but more like C++ or maybe Scala.

Its not just the lack of control, the bigger problem is features that have been added in. There major use cases for C that go by its nature can not fill. It can not do bare metal programming or real time applications without major changes to the language standard. Go aims to be a superior system programming language than C but not a successor to C. No one will be doing audio codecs or device drivers in go, but I would consider it over C for a greenfield system daemon.

Re: Neovim

#172

Post by ngoldbaum »

jbranchaud wrote: post #133
tinco wrote: post #123

Earlier quoted context omitted.

It's in the list because it's what I would use for my thesis, if I'd do one now :) It's basic, but it has the semantics for most stuff, and can easily be extended for more. I'd do all formula's/drawings in external tools. Word nowadays has semantic typesetting controls too, I think since they started that ribbon thing that it has become useable. If you stick to using their semantic things I think you can do a pretty…

Writing a thesis using only markdown sounds extremely painful. Are you going to create all your figures elsewhere and then include them as images? How are you going to create your list of figures? And your table of contents? How are you going to create, maintain, and organize your list of references? I could go on.

> Are you going to create all your figures elsewhere and then include them as images?

This is what most people do in physics and astronomy. You make the plot in some kind of plotting package and export it to a vector format. In astronomy, the journals only recently started accepting PDF figures in addition to EPS.

In my experience doing all of my figures in LaTeX is significantly more painful than using a real plotting package like matplotlib.

Re: Neovim

#173

Post by im3w1l »

tinco wrote: post #47
glesica wrote: post #40

Earlier quoted context omitted.

> ...should be ashamed people are still using Vim to write LaTeX in Bash running on terminal emulators. First, why? It works just fine. Second, is there anything better? I don't know of anything I would prefer to use. So until someone comes up with something, I'll stick to using Vim to write LaTeX in a Bash shell (might upgrade to zsh, we'll see).

No, it doesn't work fine. LateX is slow, inconsistent and needs to be ran multiple times to give a correct result, it has no API, is not extendable in a sane way, it's source code is so arcane there's books written about it, and if you've read the books the only thing you've learned is that trying to reimplement LateX is a fool's errand. And it's syntax is ugly. Markdown is better. Microsoft Word is better. They just…

The by far easiest way to write formulae I've come across is pen and paper. I could imagine a drawing tablet interface with good computer vision algorithms could be nice.

Re: Neovim

#174

Post by giovannibajo1 »

jbranchaud wrote: post #133
tinco wrote: post #123

Earlier quoted context omitted.

It's in the list because it's what I would use for my thesis, if I'd do one now :) It's basic, but it has the semantics for most stuff, and can easily be extended for more. I'd do all formula's/drawings in external tools. Word nowadays has semantic typesetting controls too, I think since they started that ribbon thing that it has become useable. If you stick to using their semantic things I think you can do a pretty…

Writing a thesis using only markdown sounds extremely painful. Are you going to create all your figures elsewhere and then include them as images? How are you going to create your list of figures? And your table of contents? How are you going to create, maintain, and organize your list of references? I could go on.

None of those features require LaTeX arcane syntax, obscure source code, and multiple compilation steps. reStructuredText is a Markdown-like language containing some of the features you mention, especially with extensions; its syntax is well-defined, and its main implementation is in Python.

The point isn't if Markdown has enough features, but rather that LaTeX lets you a pay a price for those features that you shouldn't be paying, just because it's a 40-years-old software.

Re: Neovim

#175

Post by tarruda »

bigtunacan wrote: post #25

I'm a hardcore Vim user and I just don't see the point of this. Not only that, but Vim is charity ware and requires the license to be included. The license is most notably absent from the Neovim fork. Wonder if that will be added any time soon...

The license removal was completely accidental, I will include it as soon as I get back to it.

Re: Neovim

#176

Post by count »

gkya wrote: post #124
iso8859-1 wrote: post #83

Earlier quoted context omitted.

So why don't all these people get together and fork?

I have only superficially browsed vim sources some months ago. Vim source code is literally disgusting. The number of platforms vim runs on is close to Avogadro's number. It supports 5 or sth languages for customisation. I always had in my mind to fork the thing and remove all those languages, and strip off the compatibility stuff so it will be a pure Unix program, but I never got to do it. Also, the source repositor…

The stripped down version is called 'vi' :)

Re: Neovim

#177

Post by bmj »

nicklovescode wrote: post #158
NAFV_P wrote: post #88

Earlier quoted context omitted.

> Look at SublimeText, it's got 1% of the features of Vim, yet it's converting Vim users left and right, by its sheer usability. I just looked it up, $70 is way out of my pay range. I'll convert when I have a full-time job. > We as developers in the Open Source community should be ashamed people are still using Vim to write LaTeX in Bash running on terminal emulators. Yes, you should be ashamed.

You can use the free version. It's full featured but has intermittent alerts asking you to upgrade[0]. [0] Recent vim convert.

Sublime is only free-as-in-beer. Some use vim because it is also free-as-in-speech.

Re: Neovim

#178

Post by jkrems »

gradstudent wrote: post #150
onli wrote: post #144

Earlier quoted context omitted.

> Usable means an interface which is (i) consistent and (ii) well suited to the task at hand. No it doesn't. Usable as in Usability is defined in the ISO-norm 9241-110 by seven principles, a summary can be found here: http://www.userfocus.co.uk/resources/iso9241/part110.html "suitability for the task (the dialogue should be suitable for the user’s task and skill level); self-descriptiveness (the dialogue should make…

> vim falls short in discoverabilty and, arguably, in user expectation, and suitability for learning. vim fits very well all the criteria you just cited. Moreover, "discoverability", "user expectation" and "suitability for learning" appear to be buzzwords that you just threw in on your own at the end.

They are very really things and relatively well understood. By calling them "buzzwords" that were just randomly "thrown in" you don't really make a good case for your understanding of usability.

Re: Neovim

#179

Post by tarruda »

ribs wrote: post #143

I'm not sure about libuv. Isn't that primarily for async I/O? This is a desktop application. Async I/O isn't going to significantly affect performance. And it doesn't make shit any simpler.

libuv will be used mostly because it acts as a platform layer for many common system functions.
Post reply on HN