6cxs2hd6

I'm downvoting your comment because

- that seems to be copy and pasted (i.e. plagiarized) from the original blog post http://danluu.com/clwb-pcommit/

- your submission history suggests you are associated with improgrammer.net

> If you're a landlord or hotelier,

Yes. Also: Parent of teenagers.

Why is /usr/local bad advice?

There are quite a few introductions to macros. Maybe like monads, it's a topic where people need to read a few until one "clicks" for them.

Having said that, I think this is among the best. The writing style is friendly, the examples are meaningful, and it builds up in digestible steps.

Yes. Also: this recent blog post claims Google is willing to remove apps that increase privacy (not just ad-blocking) in a way that undermines Google's business model: https://news.ycombinator.com/item?id=8240450

> tend to list prices inc VAT in Europe

I was under the impression it's a legal requirement to show the inc VAT price. (And, show it as the most-prominent price -- no trickery like showing exc VAT bold, and inc VAT in fine print.)

Would "responded" include only actual replies, or also no-reply downvotes?

I ask because lately I'm experiencing an increasing proportion of the latter. Apparently pg has endorsed these on the grounds that they are the pure logical inverse of no-reply upvotes. Although I disagree, that's the official stance, and if it is to continue to be the reality here, I think any new notification feature ought to include those, too.

Because that way, if a comment is being downvoted, then I'd know sooner. I'd have the option of adding clarification -- just like if someone took the time to reply with an actual comment and I were to get notified.

I think another difference is that the bulk of FedEx and UPS customers are businesses -- who typically are smart enough to allocate business among at least two vendors. Short-term this keeps your suppliers honest on price and service. Long-term it hopefully sustains more than 1 supplier. Even when an industry has one "gorilla" (e.g. Intel), business customers will try to sustain at least one "chimpanzee" (e.g. AMD).

However this dynamic is missing from consumer businesses.

Somewhat related: Some who advocate for workplace diversity are suspicious that "culture fit" is often a dog whistle meaning something like "young white brogrammers". I believe that suspicion is justified. At the same time, this post reminds me that company culture isn't always only that. It's rewarding to look at any organization through the eyes of an anthropologist. The idea that mid-size startups are actually closer to religions than tribes, for example, is something I find especially interesting.

It is disappointing that you got downvoted. Hopefully it was an accidental downvote due to HN's poor mobile browsing support, as opposed to someone being unwilling or unable to explain why they disagree with you.

That's not how I understood it. It says they're doing a hybrid STW and concurrent GC.

(a) A mutator may be stopped for up to 10 ms of every 50 ms by the STW collector.

(b) If more collection is needed, it will transition to a concurrent collector for the remaining 40 ms. Concurrent may pause stop a mutator for up to an additional 1 ms.

Therefore the worst case is 10 + 1 = 11 ms, not 1 ms.

My new habit: Automatically up-vote every greyed-out comment I encounter. I don't go searching for them, but when I see one, I upvote it without even reading it.

I used to read them carefully first, to decide whether I should up-vote. But from that experience, I've learned I almost always should -- the downvotes were rarely warranted, and almost always lazy and brainless. So I may as well save time and cut to the chase -- just upvote.

(If enough of us do this, maybe we can minimize the problem HN is seemingly unwilling and/or unable to address.)

I saw a nice attribution at the end of the post. (But possibly it was added belatedly, e.g. after seeing your comment.)

Module systems really ought to allow renaming on import. (Such as: rename individual functions, add a prefix to all of the functions, or even do a regexp style replace of all existing prefixes if any.)

But unfortunately, from a quick glance it looks like Go's doesn't, is that correct?

^ Q.E.D.

> Don't know why you're being downvoted

Perhaps because someone who downvotes without replying is the sort of person who would rather click than think.

Ironically.

Does this study have any bearing on "hammock-driven development" vs. the compulsion to start writing code (with or without TDD)?

Yes, but experience in the project domain(s). Which doesn't correlate with experience using HN. Not even for $tech_du_jour_popular_on_HN.

It seems like this fits two needs, for smaller companies and/or people just getting started with EC2.

1. Laziness. Which I don't necessarily mean in a pejorative sense. Maybe someone just doesn't have time, yet, to learn/configure/maintain spinning up an instance for limited times.

2. Single instance. To spin up an instance, you need another computer. If you want that "manager" computer to be an instance at EC2, too, now you need two instances. With this approach, you can set up just one instance and get much of the same economic benefit.

EDIT: Also...

3. Predictable cost. If your manual spun-up instance turns out to need to run for 4 hours instead of 2, you get a bigger bill. With the t2 instances, you'll get a slower compute (if you run out of "credits") but not a bigger bill.

Again, this probably appeals most to small/new customers?

> So, I think a better naming would have been...

Often I like to use past participles as names for stream or signal combinators.

So instead of `map`, `filter`, `fold` -- the names are `mapped`, `filter`, `folded`.

For example, given a stream, `(mapped stream f)` returns a new stream with f mapped over it. It returns a mapped stream.

Yes. And yet, still a better tech story than Yo.

If you're in the US, I think the ADA means your employer needs to accommodate you in this regard.

(To be clear, I'm not suggesting you get "all lawyered up" and obnoxious. Just ask for a meeting with HR, to discuss ways to make it work for both of you. Pointing out that you use a medical device should help get across the point that this isn't a frivolous request to doze.)

I think your point is broader. It applies to spreadsheets, Prolog, SQL. A declarative system needs to be "contaminated" by non-declarative pragmas for real-world use. (I think OP made this point.) To do something faster, or to do it at all.

SQL is a good example. You can get the desired output from a variety of queries... some of which might complete an order of magnitude slower than others. At some point you will need to peel back the "what" abstraction and consider the "how" -- what execution plan will the engine make for a given query.

Regardless, it's still a win. Even if it is no longer purely declarative, you still have leverage. i.e. You're expressing the solution concisely and with satisfactory performance, both.

To be fair, the OP says it is 23 years' worth of tips. I think the intended audience is probably people already using vim for 5+ years, who are ready for this stuff?

(As for "just use Sublime", I'd say just use Emacs :P -- but seriously both are probably OT for this.)

Although I agree it's possible (and so "dilemma" is hyperbole), in my own experience it's quite challenging to pile on the features while retaining a simpler experience for more casual users.

Realistically: The early-adopter power-users will want their new features relatively quickly. It takes significant discipline and foresight to add them in a way that won't complicate and compromise the simpler experience. Yes you can hide options, etc., but eventually the complexity can start poking through.

Of course that's just my experience as a developer and user of many programs; you may be smarter and/or luckier than me.

There's also a "market" of ideas and opinions. The OP expressed one.

The OP isn't a jack-booted right-thinking enforcer. The OP isn't even a "moral crusader", as you put it. In a free society, it is perfectly reasonable to gently mock people you believe are engaging in stupid and/or pointless pursuits. As the OP did. Of course the people doing the dumb stuff are free to scoff and ignore them. As you are.

Anyway, I think the OP has a perfectly valid point. Just because there is some market demand for an app like Yo, doesn't mean that we are predestined to make building it our life's mission. Some of us, if we slow down and reflect, might opt to be remembered for doing something other than: "Invented an app that no consumer was willing to pay for, and which solved no meaningful problems for anyone, but which some investment bankers managed to persuade some big company had strategory value. RIP".

That's fine if all y'all want that on your tombstone (the other kind of tombstone), but it's also fine to at least reflect on whether that's really what you want.

This seems like the Innovator's Dilemma as it relates to any product or service that can be used casually but also has "power users".

Power users are a mixed blessing.

Pros: they give you many ideas what to do. Often they're your best word-of-mouth evangelists.

Cons: If you take their requests too literally, they can drive the product/service into becoming something with too-narrow appeal and poor learnability. (However, if you don't listen to them, enough, they get mad and maybe you lose their evangelism, or worse it turns into anti-evangelism.)

Good point. You're right, it's not as bad an idea.

(I still think it's not a great idea. Being regular isn't necessarily the same as being parseable with a maintainable regex.)

Exactly. Isn't this as bad an idea as trying to parse HTML with regular expressions? [1]

[1]: http://stackoverflow.com/questions/1732348/regex-match-open-...

The phrase "would you mind me asking" is simply being polite and respectful, not obsequious (IMO).