mcantor

The problem isn't that it's too abundant. The problem is that people make excuses for it every time it happens, instead of just saying, "Yeah, that was really verbally abusive."

I agree with you. The problem I'm seeing in this thread relates to this point:

There could be a debate about what constitutes verbal abuse, on a case by case basis. And that would turn into a mess.

Right now, a lot of people simply do not make the distinction between verbal abuse and direct language. In other words, they are arguing that we should not bother discouraging verbal abuse because it "shouldn't" affect targets any more adversely than direct but non-abusive language.

I guess it's a debate one can approach from many angles. But maybe you're right, perhaps focusing on highlighting why one thing constitutes verbal abuse and others don't is too semantic of an argument, and it's more productive to focus on the fact that just because one person has never been truly bothered by verbal abuse doesn't mean that should be the universal expectation.

This post was about grown men, not fourteen-year-olds. Grown men... as in, people who should know better.

I can't imagine using shame as my primary motivator for improving my work.

"Offending" and "verbally abusing" are not the same thing.

This debate exists on a spectrum of gray areas, but I'm pretty sure "you should be retroactively aborted" crosses the line from "shaking someone's cage" to "flagrantly excessive verbal abuse", if for no other reason than it equate's the target's worth as a human being with their skill as a developer, which is obviously not a healthy viewpoint.

Genuine question: Did you read the article? I feel like the author's main point is that there seems to be a higher abundance of toxic interactions in Open Source than other communities.

Hadn't heard of nvim until today.

Can anyone sell me on this project? I looked at the homepage and README, but they're both pretty hand-wavey.

What problems does nvim solve for experienced vim users?

It's not a choice if you can't afford it or are turned down.

This is true, but who has the time and energy to fight every stupid Kafkaesque battle like this?

It's to incentivize buyers to Buy It Now.

If you know that Buy It Now disappears as soon as someone bids, then you're more likely to Buy It Now because if you don't Buy It Now, you can't buy it later; you can only bid on it later, and then you might not get it. So if you want it, eBay wants you to Buy It Now.

Buy It Now.

Wow. It never occurred to me that when you provide a service like that, someone could use it to literally ruin Christmas.

That is heavy.

The author filtered on questions with accepted answers only.

The author filtered by questions with accepted answers only.

http://xkcd.com/810/

How is anyone even surprised about this? If you're making money off of someone else's platform, it's only a matter of time before they're gonna ask for a cut.

Who cares if they're not actually vulnerable? It's 2012. These password restrictions are arbitrary and anachronistic.

Perhaps "crap sort" is appropriate, in that the performance of the algorithm itself is crap, and the name also evokes similar intuitive parallels to "bubble sort", since (as we know) crap floats to the top just as bubbles do.

I lucked out with this project; it began as a Kickstarter which got incredibly overfunded:

http://www.kickstarter.com/projects/maxcantor/beautiful-vim-...

It hit the front page of "Featured Technology" projects and lived there for almost the entire funding run.

I used UPrinting for the printing, who I'm quite happy with. It cost less than a thousand dollars to do the initial run of 500 posters.

Initially, my approach to shipping was to buy 500 poster tubes from Uline (no relation to UPrinting) and ship them myself. This was an unmitigated disaster; a cataclysm; a miserable shit-show of Brobdingnagian proportions. There is simply not sufficient support for the "hobbyist shipper"; USPS doesn't know what to do with you, UPS and Fedex charge too much (especially for international shipping), and the label-printing tools are across-the-board some of the worst software I've ever worked with. After months of Kafkaesque hijinks with USPS, I gave up and shipped my inventory to Fulfillrite, a third-party fulfillment provider. Thank God for those guys.

I haven't run the numbers to determine my exact profit & loss, but I make more than just beer money. I don't know if I'll ever sell enough to come even close to what the Kickstarter originally made, but the web store has been bringing in around $750/mo in revenue, which translates to something in the range of $350 - $500 of profit.

I tend to make money to the extent that more eyeballs hit the site. Last month, someone mentioned the poster in passing in the comment of a blog I'd never heard of, and I made $300 in six hours. I have no idea how to advertise, though, so that kind of thing is usually just lucky happenstance for me.

I'll probably do another couple of poster projects (bash, emacs, etc.); if they are even nearly as successful as this one, I might eventually be able to live exclusively off the profits! An exciting prospect, but one that is quite far off.

Feel free to drop me a line if you have any other questions. I really ought to condense this stuff into a blog post some time.

I sell posters of a vim cheat sheet I designed (see my profile for link). I ship my inventory to a 3rd-party fulfillment provider who plugs in to Shopify with a custom app, so all I have to do is re-print when the inventory runs out and handle the occasional customer service problem. Digital downloads are a total freebie.

The same plight is shared by any creative person. If programming makes you miserable, you're doing it wrong. The feeling of sublime satisfaction when something finally runs and does what you expect far outclasses any transient misery inflicted by the terse crowing of the compiler.

Any path worth walking is fraught with forks that lead you through brambles and strife before returning to the main road. The painter seeks the one perfect brush stroke that comes next; the carpenter seeks the perfect arrangement of nails and dead trees. If there weren't a thousand thousand ways to do it wrong, it wouldn't feel so wonderful when you finally got it right.

This is a feature, not a bug.

Trying to read this on my Galaxy Nexus was a non-starter...

I like the different adjectives for comments. Almost didn't notice that at all.

Well, maybe. If you can put paint on a paintbrush and transfer it to a canvas, are you suddenly a "painter", or just a guy with Cadmium Yellow smeared on his shirt?

Recording macros correctly and quickly is an art. Text objects help immensely, since they can handle a lot of edge cases in different places across your code.

I opine that we're more productive with our tools of choice because we chose them. And that's perfectly fine. We can claim that everyone else would be more productive if they used our unique cocktail of tools and techniques, but the irreducible fact that they do not want to is proof enough of our error.

No! No, no, no, no, no. The best programmers use whatever they use. You are making the same mistake as the guy you're replying to. There is no one best way. We need to get over this mentality as a community. I don't mean to pick on you, as this was clearly just an off-the-cuff comment, but this kind of dialogue is simply worthless. I agree that the grandparent poster seems pretty clueless about vim and its ilk, but an equal and opposite reaction that's just as subjective and baseless will get us nowhere.

Trivia: This is written by Bram Moolenaar, maintainer of Vim (the trivia part is that he maintains Vim; hopefully it's quite clear that it was written by a guy named Moolenaar).

I know this is bonkers, but maybe some people are more productive with GUI IDEs and some are more productive with vim and a terminal multiplexer.

Most command-line junkie types actually use vim, not vi. vim is quite practical for editing an enormous variety of file types at breakneck speed, and this is coming from someone who used to exclusively use environments such as Eclipse.