benaiah

This works great if you have all the commands memorized. If you don't, fuzzy matching in ido is a fantastic way to find commands and variables that do what you want (Emacs has a great tendency to name user-facing commands very sensibly a lot of the time). Most of the time I can use C-h f and C-h v to figure out how to configure something without having to read the documentation.

In addition, ido and flx-ido provide more efficient and faster (you don't have to manually invoke it) autocompletion than what you can get with prefix-based tab completion.

Also, I haven't had any issue with ido+TRAMP - everything works seamlessly on my end.

I've heard good things about ivy, but haven't got around to revamping my config in some time. I'll check it out next time I do.

Ah, helm-flx didn't exist when I quit helm, and flx-ido did. Question: does helm-flx sort results, or does it just throw back an unsorted list of matching entries, like normal helm? I consider the sorting an even bigger and more ridiculous drawback than the matching.

I haven't used helm-M-x. That may be better - but it doesn't solve the problem that everything else using completing-read is still on normal helm.

I typically use a small emacs window next to a terminal (or few - I don't run terminals in emacs) and browser in my tiling wm. Helm makes this nearly impossible, since it's very difficult to control where helm windows will go without using popwin (horrifically buggy) or shackle (I never tried this, as I'd already moved to ido by the time it showed up), because of helm's nonstandard way of doing things.

With regards to the bugginess, I can anecdotally say that I've seen more asking about problems with helm on the #emacs IRC channel than any other package - and there are several of equivalent popularity (magit, for instance). I also experienced numerous bugs while I was using helm, including some that broke my emacs config. The only package I've had break my config more than helm is org, but org generally works quite well if you can get it loaded without problems.

Emacs is actually having a bit of a renaissance - ever since package.el came out and became widely adopted, Emacs adoption seems to have increased significantly, and Emacs development is quite active these days.

Helm may be the most flagrant example of a terrible package that remains inexplicably popular. I haven't uninstalled it yet, because there are a few packages that use helm that don't have ido equivalents yet, but I try to minimize my usage of it as much as possible. Issues include:

- Significant performance issues

- Constant bugs - updates often break the package completely, especially if you're using the melpa version (melpa is another rant for another time - standard melpa is totally brain-dead)

- An atrocious version of "fuzzy matching" (you have to separate terms with spaces, which are then turned into ".asterisk" (can't type a single asterisk in HN comments) and everything's concatenated into a regex to match)

- The default helm-mode (what they recommend using for completing-read, which controls execute-extended-command, i.e. M-x, and such) is unsorted. Not badly sorted - unsorted.

- Doesn't use a lot of the standard layout functions, instead replacing them with its own stuff that can't be customized in a standard way.

- Dictatorial maintainers that only allows options and features that they deem the "right way" to do it. This is fine for some projects, but total control of my editing experience is the primary reason I use Emacs in the first place.

ido with a few simple plugins is vastly better, less buggy, more compatible, faster, has better matching, and is easier to customize. I recommend against using helm for completing-read unequivocally.

Most probably got the joke, but that doesn't necessarily mean most thought the joke was helpful to the conversation.

Having installed cygwin, I’m not so sure. :P

It likely stands for Customer Service Representative.

} // This was a good one

> For me, Meteor currently occupies a strange space where it's the web framework I'm the most excited about, yet it's the wrong tool for every project idea I have.

You've precisely captured a sentiment that I've been feeling but unable to express for some time. I think Meteor has tremendous potential, but there are a few very problematic issues, coupled with a severely walled ecosystem (Angular also has this problem, React I'm not so sure of but it seems to have it less) and unclear best practices (React has this in spades).

Re-reading this a couple hours later, I agree. I responded to needless negativity with more needless negativity. Guess my IRC habits have been leaking into my other hobbies. I'd edit it, but it's been too long since it was posted.

> The "POA" heading is misaligned. You can tell they used table-less design - things don't line up right.

Um, that's not the case. Those look like table tags, as they should be (it's a table). The only problem is that that column header is left-aligned, not right-aligned like the rows are.

Most of your complaints are bullshit, frankly, and the rest are about interaction design/UX, not visual design, which is all that this project claimed to be. The visual design and layout look fine, with the exception of that misaligned column heading (the horror!).

Representing yourself is never, ever, ever a good idea. Not even if you are a lawyer (and if you were, you'd know this). "The man who represents himself has a fool for a client" is one of the few legal truisms that is actually true.

That aside, your argument may be "pretty clear and rational," but that does not mean it follows the law (which is rarely either of those things). Without a lawyer you have no way of knowing (self-studying law is a great way to royally fuck yourself if you ever try to apply it in a real scenario).

> I would feel pretty comfortable presenting this argument to a judge, even without a lawyer present.

I'm gonna go ahead and ignore any legal advice you give, then. That's completely bonkers.

> Sure, if there is a real situation like that, the officer needs to use force. If the officer does get to shoot, say, not at point blank range, then the officer should shoot for a limb and wound enough to win the fight but not necessarily shoot to kill.

Please take a self-defense class. You should never "shoot to wound", you should shoot to stop, always at the center of mass. Shooting to wound, as at a limb, is very difficult and error-prone, and a miss can easily wound bystanders or damage property.

We already have enough firepower with standard nuclear warheads to destroy civilization a few times over. I doubt a bigger bomb would fundamentally change the equation at all.

> you don't want a car outside of a garage in snow

Why not? It works fine, and there are few places in the US cold enough to even require a block heater, let alone actually endangering the engine. Just have to brush it off sometimes, but it's hardly a dealbreaker. I lived almost 20 years in Alaska and never had a garage that we used for cars.

The original quote is actually the precise opposite of this.

If airlines could do so, they would. It’s very expensive to fly an empty plane. But those planes are on a tight and inflexible schedule - they’d be flying even if no one boarded the plane at all.

Note that this is a chart of per-comment karma, not a trend of her total karma. Thus explaining the sheer cliff between a largely-downvoted comment and a largely-upvoted one.

    > > You seriously made another module loader?
    
    > Yeah. There are several reasons why:
    > To create a new-feeling environment that is clearly not node,
    > because you’re writing code that runs in node and IE9 and Chrome
    > etc. It shouldn’t feel like any old node.js module.

Why shouldn't it feel like any old node.js module? Nearly all the work in JS packaging of late has been to abstract the differences so that we can use the well-established node packaging system on both ends. We're already able to do it with stuff like babel and browserify.

No, it'd be way faster to just do it all in assembly. These fancy "high level languages" and "memory management" and "libraries" are just cons foisted on poor unsuspecting programmers by middle management and enthusiastic marketers. Real Programmers (TM) don't need any of that shit.

(/s)

Off topic, but I just wanted to say how much I've appreciated the modding of late. It's been prompt, reasonable, and transparent. Thanks a lot.

The independent stdlib is interesting, and I haven’t seen Elixir advocates mention it much before. I’ll have to look into that.

The hard data has been around for years, and is fairly easy to find. Not every blog post needs to have an accompanying statistical analysis.

None of the things that you mentioned, card games excepted, are particularly cheap unless you already have the equipment, and some not even then.

2. I know this is anecdotal, but when I was unemployed I often didn't socialize because I simply couldn't afford the luxury. Many social activities are fairly expensive, depending on your area, friends, and preferences.

The last example you cite is called Superhot, fyi

I believe the parent comment was referring to using “let” instead of “var” - “let” supports reassignment.

What? Opiates are not psychiatric drugs. You don’t get addicted to opiates by tasking other, unrelated drugs. That’s absurd.