Legion

I don't think you're looking at the project the right way.

Think about it like FreeDOS. FreeDOS facilitates running DOS software on modern hardware, and by its open nature, it can continue to evolve and make DOS software runnable on the next generation of hardware.

Think about 10, 15, 20 years from now, and all that software written for XP. That is where ReactOS comes in. A sustainable, maintainable platform for running XP-era software on hardware systems yet to come.

At least, that's how I see the project, as someone who is neither involved nor a close follower of it.

> Learning Vim is a side project: something you do casually, slowly, until and if you are able to do the actual switch.

No one appointed you the director of how one learns Vim.

This is one of the most obnoxious parts of Vim threads: that guy that responds to people talking about how they learned Vim (past tense, as in already happened) and tells them that they learned it "wrong".

Is it really preferable, hardware-wise, to something like the HTC One?

That is, assuming the user is capable of flashing the HTC One with a third-party firmware to get a vanilla Android experience. Is there a draw to the Nexus in comparison to the likes of the One other than being vanilla out of the box?

One linking post is fine. Three comments full of Passenger links is pushing good taste.

Worst work day. The post is clearly titled as such.

Reading 24 books seems like an awful lot of time committed to doing something other than actually making a product.

One of the books was marked optional, though, so there's that.

> seeing a piece of code that was specially written for a very narrow and specific use case, and needing to extend it to some scenario that the original author did not envision

There's pain in both options: making something specific that has to be made more general later, and making something overly general and never actually having a use for the additional complexity.

The former, though, is solving problems you have, and the latter is solving problems you often don't end up having. Given the choice, I would always prefer the former.

The problem with YAGNI as a development slogan is that it can be too broadly applied.

I think a better wording might be, "don't increase complexity writing code you may not need". The issue is usually not the presence of additional code. Rather, it's making design decisions based on requirements that may never in fact come to bear.

Using Vim mode in other editors is like replacing all your silverware with only spoons. It's much nicer, shinier silverware, and everything's going great at first, until I subconsciously reach for a knife.

Dokku has begat Flynn, aka "Super Dokku": https://flynn.io/

Anyone interested in this kind of content should see Pat Shaughnessy's Ruby Under a Microscope book: http://patshaughnessy.net/ruby-under-a-microscope

It's the closest thing we have to a new Ruby Hacking Guide. It's a somewhat gentler, more approachable treatment of the subject matter, but no less awesome.

Shaughnessy also has a number of blog posts on his site that dive into the same kind of details covered in his book (and RHG).

I've become a fan of the micro-paywall. A one-time fee of $5-10 is an amazingly powerful filter.

Metafilter, as you said, is one example. Another is the Ruby Rogues Parley mailing list (now Discourse site). I can only imagine what a HN with similar filtering-of-the-noise would be like.

I so badly want to learn how to really play roguelikes like DCSS. I've never gotten past the wander-around-first-few-levels of NetHack and DCSS. There's so much there!

At least they live in a place not ravaged by war. I feel bad for the people stuck in war zones.

At what point do we stop with the one-upmanship and accept that we can feel bad for people on various levels?

It was a mistake to leave that bug unfixed for so long. I'm glad they came around to fixing it. Hopefully this is a sign of a team and project maturing.

> But lead by itself can't be the major factor behind the crime drop. Countries such as Brazil have banned leaded gas even before the United States, and crime rates are still rising dramatically.

This is not logically sound. Brazil could have other factors which increase crime more than getting rid of lead reduces it. The fact that Brazil's crime has increased does not, in any way, tell us that the lead ban couldn't possibly be a major factor in the US's drop in crime.

What separates this from Nokogiri? (Don't take that as critical, more working code out in the world is better. Just wondering, as I use Nokogiri heavily for our company chat-bot, and couldn't tell the answer at a quick glance.)

I think this observations was much more true of Rails 2.x and before than Rails 3 forward.

People forget that "Rails 3" was actually Rails merging with Merb. A lot of hard-coded inflexibility of Rails 2 had to be extracted out, and the framework became much more malleable as a result.

When I hear people talk about being stuck to a certain path with Rails, I wonder what they are talking about. Then I think back to Rails 2 and think, "oh, right....".

Rails still encourages a certain path by convention, but it is much easier to deconstruct than before.

> according to some opaque criteria that I don't get to define or tweak

Exactly this. When I saw the tabbed inbox, my first thought was, "oh, this will be cool", followed shortly by, "wait, I don't get to control or customize this at all?"

Really, why can't I define my own tabs for specific searches/labels? The black box tabs they provide now should just have been defaults within a customizable feature.

I for one would kill to see an ESPN that has to court direct subscribers.

Getting people to pay to subscribe to you is a whole different beast from chasing ratings among an audience that pays for you either way.

ESPN may get ratings doing endless Tim Tebow stories, but I posit that the viewers that generate those ratings aren't the same people the network could successfully convert into subscribers. Fluff crap may get people to stop while flipping channels, but nobody is going to be directly subscribing to get it.

I'm a sports fan, yet like many other sports fans, I consider ESPN to be borderline unwatchable. The only thing I care to watch are actual game broadcasts. And what happens when wider direct distribution means that the sports world no longer needs ESPN's cable reach to get to viewers?

Just ignore him. I'm a little sad to see the comment get so many replies, instead of simply being downvoted into oblivion.

I'd love if we as a community could endeavor to give troll responses like that as little attention as possible.

Neat. I like seeing people try new things with terminal emulators, even if a certain cluster of boo-birds shows up every time.

I noticed that the terminal does not work well with my zsh right-prompt (ends up printing on the left and getting overwritten by what I type), and has some issues with my prompt when my little Git status line appears when browsing inside a repo. But I will be keeping an eye on this project.

I use NeoBundle to run the YouCompleteMe module build upon installation. Works great. Especially since the build is triggered by a single simple command. (People really complain about that being hard?)

The delay in leaving insert mode used to drive me nuts in vim-powerline. I posted an issue and the author pointed me to this helpful Vim config snippet as a workaround (original link gone as the vim-powerline issue tracker has been removed, so reposting as a gist): https://gist.github.com/brendonrapp/5944296

I imagine the delay that the README for this project is referring to might be the same thing, so hopefully it can be alleviated with this same trick.

EDIT: Looks like the official Powerline docs share this little trick now: https://powerline.readthedocs.org/en/latest/tipstricks.html

Rarely am I so torn about a project's name. The play on PHP's name makes me cringe, but the (not sure if intentional?) play on the California Highway Patrol's acronym makes me thumbs-up.

I would start with a provisioning process that isn't completely opaque about such things.

To me, that's an infrastructure smell.

Exactly. The web had to bend to IE, not the other way around.

The fact that that bending resulted in IE6 still being able to mostly display websites today is not any sort of testament to IE6's quality as a browser.

This capability is what took me from trying the Dash demo to paying for the app.

Once the content became something I could use on all my computers and not just the Macs, it became worth the money.

Being cool and cooperative with Zeal earned the Dash developer at least one sale.

> Do you think it's possible some people just aren't wired like this?

Absolutely. Well, maybe I wouldn't call it "wired", but no one tool is right for everyone, and no one should feel bad or wrong for using something different.

I am a Vim lover. You can pry Vim from my cold, dead fingers. But of course it's not for everyone, for the same reason that we don't all use just one programming language or one web framework.