nsmartt

You're being downvoted because of your tone and because you dismiss him by comparing him to authority figures.

Huh. I was basing my comment on the knowledge that Mozilla feared IE would become the way to browse the web. I should have double checked.

> How can open source software be in competition with anything?

Market share is power. Popular open-source projects can, and do, shape the industry. If you believe your trajectory is the right one for the industry, competition matters a lot.

As an example, Mozilla's Firefox was created to compete with Internet Explorer. It succeeded, and now Mozilla is working to defend the open web, so market share is still crucial for Mozilla even today.

From the article:

> The function is short enough to paste below. It is pretty unique to Neovim, as it was wrought for its brand new event-oriented nature:

I didn't take your use of “documentation” to be so loose, but I agree that it should have an explanation for the use of “magical” in the title. The author has since added an explanation.

There are 61 commits and only one contributor. This isn't a good complaint, and the snark makes it worse.

The point of TL;DR is to summarize a longer piece. It literally means “Too long; didn't read”

That's a good reason to downvote or stop reading, but I question whether attacking the author for having the audacity to publish the post is a good move.

People don't need to be experts to recognize flaws in tools aimed at consumers.

Writing bad articles is a great way to move toward writing good articles.

Writing in the public view is a great way to get feedback on your writing and the subjects you discuss—e.g. corrections, further education, etc. For some people, it also increase the pressure to improve.

Vanity is only one possible reason for writing in the public view, and it's an exercise with large potential gains. Your perspective is entirely off, and you've decided to take an opportunity to attack someone who was either brave enough or indifferent enough to risk being attacked in the first place.

It's a single file. It works with or without the ruby-dependent parallel plugin installations and upgrades. It allows for plugins to be loaded only when they're needed (e.g. only for JS files). That's minimalist.

I switched to vim-plug from Vundle a couple of weeks ago, and I'm in love. Lazy initialization and, if your vim is built with ruby, threaded plugin installations and upgrades. As a bonus, it's beautiful.