Live data from Hacker News

Neovim

github.com

301–310 of 372 posts

Re: Neovim

#301
post #276

Earlier quoted context omitted.

...if you have a leafblower, you have no need for a chainsaw... Yes, but a leafblower combined with a chainsaw... I don't know about you, but that's a tool I could find some uses for.

Like scaring children?

It's not often that I come to laugh out loud while reading (the usually somewhat stuffy) comments on HN.

+1 coffee sputter.

Re: Neovim

#302
post #66

Earlier quoted context omitted.

If that is all you need and expect from a replacement for LaTeX, why aren't you just using LibreOffice?

If we're talking about LaTeX, Word, Markdown and LibreOffice - well, then LibreOffice is a contender for the worst usability, it's superficially similar to a mature product but it's a case of "the remaining 10% of goodness will take more work than the first 90%".

Usability depends on who is using it. I refuse to use LibreOffice because it is so bad, but I would sooner recommend LibreOffice to my father than LaTeX or Markdown.

Re: Neovim

#303

Earlier quoted context omitted.

Or you could just use LaTeX, which has been used for writing books for decades (the word you're looking for is "debugged" and the phrase is either "well understood" or "well documented"). And yes, there are efforts underway to improve it (LaTeX3) but 2e works so well, there's not been much drive there. And if you find LaTeX is so hard, there's always LyX...

> which has been used for writing books for decades Well, mostly math and science books. Very few (if any) fancy and well typespeced books by major publishers have been made with LaTeX. I know, because I know that industry. So, while TeX was once created to be a general typesetting solution, it has been relegated to something math and cs geeks use for their papers. > And if you find LaTeX is so hard, there's always L…

I have to wonder if your average publisher would even know what to do with a book written in LaTeX.

Re: Neovim

#304

Earlier quoted context omitted.

Jesus nothing is wrong. Read my comment again. I'm saying it's an apples to oranges comparison. If BASIC is all you need great. If word is all you need great. If you can get by with importing from gnuplot or R or matlab or whatever great. I'm not saying one is superior to the other. I'm saying that when I want to draw a commutative diagram, I'd rather do it in LaTeX with tikz or the xy package. I'm sick of the "HN st…

What I'm trying to say is that for the vast majority of peoe that have to produce documents, it isn't an apples to oranges comparison. For most proe, Word and LaTeX do the same thing. And one of those is vastly easier to use to get their job done. So while LaTeX is the technically superior, Word will still get the job done. And because of the network effects that working with collaborators has, People like me are stu…

In a similar vein, you might say that to the vast majority of people there is no difference between a screwdriver and a pry bar because most people are content with abusing screwdrivers.

Re: Neovim

#305
post #40
post #29

Thanks for trying to do what many of us secretly wished we could do but can't because of time/skill constraints. I will definitely move to NeoVim the second it's packaged (is it yet?), regardless if you've changed anything yet. I hate the ideas many programmers have about backwards compatibility, that it's more important than development speed and modern concepts. There is nothing holy about Unix era software, chance…

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

I think the problem is we are typesetting at all. By typesetting I mean for the printed page. Most of the result is PDF which is then emailed around. It's a PITA to write, a PITA to generate, a PITA to distribute, and then a PITA to read.

For the one percent (perhaps) of the documents which really end up on paper, I guess LaTeX is fine. Or Word. Who cares?

Re: Neovim

#306
post #235
post #29

Thanks for trying to do what many of us secretly wished we could do but can't because of time/skill constraints. I will definitely move to NeoVim the second it's packaged (is it yet?), regardless if you've changed anything yet. I hate the ideas many programmers have about backwards compatibility, that it's more important than development speed and modern concepts. There is nothing holy about Unix era software, chance…

I fully agree. For me, Vi and Emacs are only when I don't have an option in terms of IDE support, even though I know at least Emacs quite well. What can I say, the world of Amiga GUIs, Smalltalk and Lisp environments spoiled me as an IDE fanboy. It baffles me why in 2014, some developers still prefer to work as if UNIX System V had just been released.

I started with IDE and then moved to vim. Not because it's "cool". It's productive. There are several reasons. First off, movements. Almost any IDE now has some plugin to imitate vim-style keyboard shortcuts, but they honestly suck at it. Next thing is it's fast and lightweight, which surprisingly feels more important than I thought before. I don't have to wait for java-based IDE's GC to stop running or something. Third reason is that I can set any action to any key, I can invoke anything from the vim itself to automate some text-processing, make any visualisations I need, anything. IDEs also provide some mechanism for that but it's way more complicated and obscure. But the key reason is simpicity, really. I know what happens underneath the hood, because I manually enabled the plugins I want, I've set shortcuts. Vim serves me, not otherwise. Back when I used to write programs in Java I tried Idea and switched to Netbeans, because Idea is way too "smart". It tries to do everything automatically, which is OK until it fails. And it did fail sometimes. But when it fails it's me who has to find what did it mess up. So I prefer to write code myself (or let do it some scripts I explicitly authorized to do so), not to fix something my IDE broke. It is especially uncomfortable on some old messy projects with lots of legacy code.

Is vim perfect? Well, for me it's not. Because of vimscript, because it doesn't have mechanism to work with non-text information (for example it has to open up another window to show me rendered LaTeX). Sometimes I even think of switching to emacs. Plugins to do some advanced processing (like rope for python) are slow quite often. But I still prefer it to any IDE in most cases. It's not perfect, but it's the best thing I've met so far in this imperfect world.

Re: Neovim

#307
post #248
post #49

Earlier quoted context omitted.

Yeah, I mean it's not like 'more modern' alternatives haven't been created... They just haven't caught on among this group of people because this group of people values functionality and does not give a damn how old something is. People have made fancy new shells build around things other than bytes through pipes, people have created new replacements for terminal emulators, and people have created fancy GUI document…

Because many of the people that learned those old stuff were young when those tools were new and don't want to learn anything else. Habits die very slow.

I'm not particularly old, but I prefer using tools that are considered "old". Furthermore from where I am sitting, there seems to be no shortage of older developers who are wed to the latest fancy IDE.

I don't think this is something that follows age lines. Whether or not somebody primarily has a background in the FOSS world or in the Windows universe is probably a much stronger indication of what sort of tools they use.

Re: Neovim

#308
post #292

Earlier quoted context omitted.

Then you did it wrong. You should have just factored your thesis in multiple files, for example used one for each chapter.

That sounds like a workaround.

It is, but you have to remember latex is best thought of a programming language that outputs pdfs so splitting into multiple source files is useful, as is source control.

Re: Neovim

#309

Earlier quoted context omitted.

Getting a little ahead of ourselfs maybe? "Nobody knows", lets just compare IRC. #javascript on freenode got 951 users. #clojure on freenode got 651 users. Even tho its not a good comparison, saying "nobody" knows clojure is very far fetched. It has a ever growing community, with several books published, and the whole point on Chris choosing Clojure shows enough of its maturity.

Search Amazon.com books: ClojureScript: 10 results (only one of these actually has ClojureScript in the title) Clojure: 89 results JavaScript: 5,787 results Sorry, there is no comparison. I'm not saying Clojure sucks, I am just saying that it's not mainstream. ClojureScript even less so -- it's an offshoot of Clojure which was designed around the JVM, not browsers.

> ClojureScript even less so -- it's an offshoot of Clojure which was designed around the JVM, not browsers.

Clojure was designed as a Lisp friendly to it's hosting environment. JVM implementation is probably not purely accidental, but it's not the whole of original design either.

And as I write this comment here I might as well add: non-mainstream languages are in many, many places a competitive advantage for those who use them. I know, use and frankly like many non-mainstream languages and the ROI of learning them was universally higher than with the most popular languages.

Re: Neovim

#310
post #303

Earlier quoted context omitted.

> which has been used for writing books for decades Well, mostly math and science books. Very few (if any) fancy and well typespeced books by major publishers have been made with LaTeX. I know, because I know that industry. So, while TeX was once created to be a general typesetting solution, it has been relegated to something math and cs geeks use for their papers. > And if you find LaTeX is so hard, there's always L…

I have to wonder if your average publisher would even know what to do with a book written in LaTeX.

Any publisher that produces books with heavy math will know what to do with LaTeX, and if not then call a vendor that will know what to do with LaTeX.
Post reply on HN