skysight-inc/HackerNews huggingface dataset:
Just like every other CDN or network service out there that is a proxy. Using a load balancer from a cloud provider that does TLS termination is the same risk. Of course it's by design because that's just how it works. You can't proxy TLS traffic without being MITM.

Please stop repeating the same exact thing instead of actually understanding what you're talking about, it's just misinformation and FUD at this point. You still havent replied to any of the other questions.
Resemble: have qualities or features, especially those of appearance, in common with (someone or something); look or seem like: some people resemble their dogs | they seemed to resemble each other closely.

Resent: feel bitterness or indignation at (a circumstance, action, or person): she resented the fact that I had children.

I think the second one fits better, you resent that the parent poster called MailChimp "spam"
How is DDG meant to detect that there are 'missing' bits of information from the returned results, and then 'insert' the missing stuff? Do we really expect a secondary search engine to hit all the returned search result websites and grep them for the terms, as Stallman suggested? How long would it take people to abandon DDG if they implemented that, given that it would make search intolerably long?
The 10,000 hour rule does more damage than good. Guitar is a perfect example to illustrate why.

a) It doesn't take 10,000 hours to be halfway decent at guitar. If all you want to do is be able to strum the chords for most popular music, you should be able to do that in way less than 10,000 hours.

b) Even 10,000 hours isn't going to turn you into Stevie Ray Vaughan or Walter Becker. There's lots of guitar players out there with way more than 10,000 hours who are damn good and still aren't those guys. The 10,000 hour rule as Gladwell presents it makes people believe that time investment is key in developing a skill and that's just not true for all skills.

c) 10,000 hours is such an arbitrary number as to be totally meaningless. As guitar perfectly illustrates, it's almost never going to be the right number. For most people who just want to be able to strum some Beatles tunes, that's way too much time. For people who want to be Yngwie Malmsteen, it's not enough.

But it's not just guitar, most skills are like this. The 10,000 hour number is totally meaningless. How much time you need to invest into a skill depends on what your goals are with that skill, and also how good you are at related skills that feed into that ability already.

The 10,000 hour meme needs to be taken out back, hit with a shovel and buried. It's awful.
That's one of the downsides of over-abstraction and over-generalization: instead of a tool, a library gives you a box of kit components and you have to assemble the tool yourself.

...and a framework is likely to give you a box of components to build a tool-making factory factory factory...

http://discuss.joelonsoftware.com/?joel.3.219431.12
tl;dr: prefer callback hell instead of straight forward ifs and somehow that's progress.
They do handle a lot, doesn't mean you're not responsible for the settings you choose. Lack of understanding or effort on your part doesn't mean you get to just blame the vendor.
In occident there is a general consensus that black is the normal color for death, but in some parts of Asia death is represented by white. This is the reason of karategi being white for example.
Braid Code Cleanup (part 1)
> I know! That's why I am asking. I have found surprisingly difficult to find a package that does this.

scrypt, with an output length that suits your use-case? (as Filippo points out)

Note: I wrote https://github.com/elithrar/simple-scrypt, which wraps Go's scrypt package and gives it a friendlier API (mimicking the bcrypt one). Handles salt generation for you and has sane default parameters, outputting a 32-byte derived key by default. e.g.

func deriveKey(key []byte) ([]byte, error) {
return scrypt.GenerateFromPassword([]byte("plaintext"), scrypt.DefaultParams)
}

You can pass your own params, or modify the defaults to get a different key length depending on your use-case.
It's one thing to bring a military force to a battle. It's another thing entirely to call out unarmed civilians to deter a military force.
Gladwell is not even a journalist:

http://www.alternet.org/story/155770/is_malcolm_gladwell_ame...
Just because someone is proclaimed "expert" doesn't mean they are good at what they do. This is especially true for the softer fields that Gladwell writes in.

At the end of the day it's up to you to determine if what you are reading is accurate. And if you don't have the tools, resources, or time to do so, you trust in experts at your own risk.
The problem with adopting “bleeding-edge” tools
3D printed contactless payment ring – Tutorial on NFC antenna design [video]
The browser would time out after a few minutes. However if the user stops loading the page and hits Reload, the browser will try another IP and the page will load successfully. I verified this behavior with Chrome. For a personal blog, that's definitely "good enough" HA.
The more I write code the more I realize that the entire purpose of the code is to have some effect on reality, and the more reliably it can do this, the better the code.

Very nicely put. The only "principles" I keep in mind when I write code are simplicity, correctness, and efficiency, and those tend to all be correlated.
yes, that is what I was looking for. Thank you!
Nobody's asking for help, all I said was that it could've been a mutually useful relationship, but it didn't. Also, there are only two actual coups in turkish past, 61 and 80.

I'm sorry, I shouldn't have responded to you, as your arrogant and ignorant attitude was obvious from your initial comment on the thread, and your past comments clearly show that you're tendent to blindly post offensive, low-quality stuff. I won't respond to you any further.
> There is no isolation with cgroups in Linux
> containers are resource constraints

I'm going to say this one more time:

Linux containers use namespaces as the primary isolation mechanism -- NOT cgroups. You can create containers without cgroups. This happens to be my problem space too, and you're not helping by spreading ignorance.

> equating cgroups and namespaces with a lightweight virtual machine technology is conflating two different things.

Finally you mention namespaces. Who mentioned "lightweight vritual machines"? Namespaces are just tags for a process that are used to scope operations to provide isolation. Cgroups are different tags used to provide resource constraints. Just because people use containers in that way at the moment doesn't make the underlying technology just about that.

> an operating system I very heavily use, develop on, and engineer for, I would be interested to learn of them.

Arrogance is not an endearing quality.

> If they exist, I have not heard of them

We can play that game all day. I don't care who you have and haven't heard of, Linux has talented kernel engineers as evidenced by the fact that Linux is widely used for production deployments. You might not agree with what has been built, but you can't deny that it does exist and is being used to power production systems. Please calm down on the saltiness, sodium is bad for your health.
How I Could Steal Money from Instagram, Google and Microsoft
FWIW, I'm pretty unimpressed by the anti-if campaign's website. They've clearly put style over substance. It's a beautiful website, but I spent some time poking through it and I can still only guess at what exactly they're on about. It seems to be something about if-statements being bad, but beyond that it's rather a muddle.

I'm trying to be charitable, though, so let's assume that the core of their idea is something coherent. I'm guessing it's really about something I do think is an important point: How inversion of control is a design pattern that lets you create code that's much easier to manage, because it greatly limits the extent to which certain kinds of decisions need to be federated throughout the codebase.

If that's the case, then real sin (and the article author's) is mistaking if statements for the problem. Conditional branching is not a problem; I think most of us can agree it's an essential operation. The real problem they should be after is poor encapsulation. Where if statements come into it is that, if you've got badly architected code with poor encapsulation, one of the symptoms you'll see is that there will be a proliferation of if-statements that crop up all throughout the code. Every single frobinator will need to stop and check whether the widget it's operating on is a whosit or a whatsit before it can take any sort of action whatsoever. Lord help us if we ever try to introduce wheresits into the system; we'll have to go modify 50 different files so we can replace all those if-statements with switch statements.

It's probably nowhere near as fun to write an article that advocates a high level design methodology as it is to write an article that makes a bold contrarian claim like "If statements bad", though.
Death is a change of state. When a car runs out of gas, what color is that situation? What is the color of an arriving email? The concept doesn't apply well.
That still has the problem of boolean blindness. The boolean you get back doesn't tell you what it means, you have to go looking for that information.
Indeed it does. I'd forgotten it was AOL that ended up with it though, that's rather discordant.
Unearthing the Secret of New York's Mass Graves
This story originates on coding horror and when gwern of gwern.net, active on this website checked the chain of citations the claim was not supported.

It may be true but there's no evidence for it.
I would disagree with this analysis. Since the bog is so successful at preserving the remains it would be a horrible place for "gangsters" or anyone murdering someone else, to dump a body. A body which years later would still be recognizable as the victim.

The notion of it being a "cheap" way to bury people which was unlikely pass disease along to the village and would be nominally odorless is more compelling to me. You need look no further than a modern equivalent in New York (http://www.nytimes.com/interactive/2016/05/15/nyregion/new-y...).

So I am more likely to believe that it contains people who the elders dispatched or perhaps died in a crime without any family to claim.
In a world where every market participant was perfectly informed and perfectly rational, and always acted in perfectly enlightened long-term self-interest, then you might have an argument.

We do not live in such a world. Your Feynman anecdote is a rare exception rather than a norm. Tech companies and software engineers will give up their racial and gender biases only when absolutely forced to, and at the moment nothing in the market is forcing them to -- you might not become the most profitable company in the world, but you can have major bias and still do well enough that it's simply not perceived as a problem for the companies which do it.
sounds like what's really being said is..

It is recommended that programmers use abstractions whenever suitable in order to avoid duplication, and associated errors
only a sith speaks in absolutes
This comment violates the HN guidelines, and we ban accounts that do so. Please stop.

https://news.ycombinator.com/newsguidelines.html
Yet "black tie event" does not imply death, instead it implies a fancy party. In auto racing, a black flag is a penalty, but it's not fatal. The American Express Black card is a symbol of vast wealth, not mortality.
"I resemble that remark" is a common English language expression used humorously as a play on the sound similarity of "resent" and "resemble."
Reputation among journalist circles is worthless if Jonah Lehrer can get a job at any newspaper after being outed as a faker and a plagiarist. He can and it is.
Personal attacks are not OK on HN. Please don't do this.
Problem is, a decision has to be made somewhere about which function to pass into that "if-free" block of code. The if-like decision has just moved elsewhere. That is a win if it reduces duplication: if a lambda can be decided upon and then used in several places, that's better than making the same Boolean decision in those several places.

Programs that are full of function indirection aren't necessarily easier to understand than ones which are full of boolean conditions and if.

The call graph is harder to trace. What does this call? Oh, it calls something passed in as an argument. Now you have to know what calls here if you want to know what is called from here.

A few days ago, there was this HN submission: https://news.ycombinator.com/item?id=12092107
"The Power of Ten – Rules for Developing Safety Critical Code"

One of the rules is: no function pointers. Rationale: Function pointers, similarly, can seriously restrict the types of
checks that can be performed by static analyzers and should only be used if there is a
strong justification for their use, and ideally alternate means are provided to assist
tool-based checkers determine flow of control and function call hierarchies. For
instance, if function pointers are used, it can become impossible for a tool to prove
absence of recursion, so alternate guarantees would have to be provided to make up
for this loss in analytical capabilities.
Best Sushi Places in Las Vegas – Marc R. left tips and reviews on 3 businesses
If you wrapped that "unique" implementation in some kind of reusable construct, it would be even easier to use, and it would be easy to replace with a more efficient implementation. Hmm.
No, DDG doesn't have its own crawler. And such censorship as described is impossible to distinguish from results being pushed up or down the rankings by more focused terms, without some computation that would slow your search down, as well as more queries to more sources, resulting in more network roundtrips, that would slow your search down even more, doing so causing a massive slowdown on all searches, for a check that is irrelevant 99% of the time. That kind of slowdown is unacceptable.

But then, who was surprised? RMS has long been known to put purity before practicality, and to say that network and computing time is cheap, a very MIT attitude, and one that does not serve people trying to run a service for hundreds and thousands of people, who all expect their response to come back fast.
I've made it for my brother who is in wheelchair :(
Ohjah Las Vegas (ohjahlasvegas) • Instagram photos and videos
I've noticed I am now getting hit by targeted ads relating to searches I do on duckduckgo..

the question is.. what search engine do I switch to now?
This price point doesn't work, it only hurts small clients who want to send some email.

Pricing in general isn't an effective strategy to stop this unless it becomes more prohibitive than the profit margins - and that's a very big number.
Apparently you missed the leftpad drama a couple of months ago.

(It was ridiculous then, and it is ridiculous now)
If a dead comment appears in a thread, users with vouching privileges and 'showdead' turned on in their profile can vouch for it to make it visible if they believe it to be substantive. Please do this instead of reposting.
The "technical debt" metaphor gets so much better if you take the analogy more literally than most people do. Like for financial debt, the optimal amount is not necessarily zero. Oftentimes taking on or carrying debt allows you to generate more profit than you could by avoiding it or paying it down.

That said, most places I've worked manage it poorly. Few people really understand that, just like financial debt, it's something that needs to be taken on and managed in a mindful and deliberate manner.
I'll beg to differ. I've been running my own email for almost two decades and although the environment has changed, it is still perfectly accommodating of small operators that keep themselves up-to-date with context (e.g dnswl listing, notifications to major recipients, signed headers, best practise DNS records etc etc).

I changed IP address in the last 18 months and despite great trepidation, was pleasantly surprised that deliverability was not degraded.

Paying a bond feels like protection money for something I think my domains/hosts already have: a good reputation.
This.

Obviously having massive troop presence prevented war with the soviets, but it can't be overestimated what stuff like the European Coal and Steel Community, the EEC and other following integration steps did after WWII in terms of getting France and Germany to "need" each other, instead of wanting "revenge" and repayment.
The first problem is that the "match" function is considered in the first place. It's too general. It should only be used in higher order constructs where its flexibility is actually needed.

Second: The enum based refractor is actually valuable and fine IMO. If you need string functions, stop there.

Now, shipping control flow as a library is a cool feature of Haskell. But, if those arguments are turned into functions, the match function itself isn't needed! It just applies the first argument to arguments 3 and 4, then passes them to the second argument.

match :: (a -> b) -> (b -> b -> Bool) -> a -> b
match case sub needle haystack = sub (case needle) (case haystack)

Does that even need to be a function? Perhaps. But if so, it's typed in a and b and functions thereof, and no longer a "string" function at all. And, honestly, why are you writing that function?

Typing it out where you need it is typically less mental impact, because I don't need to worry about the implementation of a fifth symbol named "match."

sub (case needle) (case haystack)
I guess if you give someone a puzzle, there's a possibility they might solve the puzzle from memory. If you give an unsolved problem, you know they won't have seen the solution before and can see their thought process better(since you know thinking will be required).
Generate masks, look at them and validate that they only implement the circuits your VHDL synthesizes. Make a wafer and validate that the silicon is the same as the masks. Get your wafer diced and hand carry it to Malaysia to have it put into packages for you. Pretty time consuming though.

You might be able to get away with a strict characterization of the diced chips to give yourself a very high likelyhood that different die were not substituted at the packaging step. You could also decap a random selection of chips coming back from the factory to validate they used your die rather than a different one.
Well, that's exactly what I was saying: any visual language for which a text editor is non-viable is unacceptable. And it doesn't so much matter who learns what. What matters is that some time in the future, that data is extractable, and viewable, long after the visual environment has been lost to the world. Maybe it isn't easy, but it's doable.
It boils down to what you mean by "equal."
Spy or Whistleblower? Should Obama Settle with Snowden?
Amazing. The western world was all pro "internationalism" when it came to exploiting the east and Africa (centuries of colonialism), but now, want to go back into their shells.

Can't have it both ways.
date.if_weekday looks like something one would find in Smalltalk class library, but (at least for GNU Smalltalk) only such construct I've found is this: http://www.gnu.org/software/smalltalk/manual-base/html_node/...
Reading this article I immediately saw a couple of drawbacks. Since then I've thought of a few more. But several of the points made were not lost on me. This article made me think a bit, and I'm still thinking about it. That's worth something right there.

To anyone out there who clicked through to these comments and is thinking it's not worth reading the article, please go ahead and read it. It's short enough. You may or may not use fewer if-statements in the future, but it might give you a better sense of why you choose to do things one way over another.
I remember seeing this when it just started (like two years ago, not sure if it was one of those 12 startups/year). Current one looks fantastic compared to that one, so I guess it's one more example that demonstrates you shouldn't hold off until it's feature-rich eye-catching candy. Your project story is inspiring!
How long can that last?
Oh, Apple only wishes that R&D money down the drain was a joke.
No, you misunderstand me (and the fault could be mine): my point is that since it's pedantic to worry about the terminology, you might as well use the standard terms. Leave it to others to waste their time worrying about what things are called.
I don't agree here at all. The methods you show operate on an Optional, and it's incredibly common to perform those kinds of comparisons so it makes sense that they have convenience methods. This is not at all comparable to something like if_weekday.

This has not "taken over" rust. Result is another type that does this, but this makes sense for the same reasons.
Vifm !!!
That's completely unreadable.

So how exactly is it that by multiplying a regular sum of positive numbers by a decaying exponent do you get a negative number when you take the limit?
sucker news!
That's exactly how it ought to work. I hope this gets noticed despite you being so heavily down-voted (and flagged... wtf?). I'd like to see it get properly refuted if it's not true.
how many people does it take to screw in an everlasting lightbulb?
The article mentions CFLs and LED lamps, which are definitely subject to the same engineering pressures:

This would result in increases of candlepower of 11 and 16 percent respectively.” That boost in illumination, he suggested, “would be acceptable to all flashlight users” despite the fact that the higher current would shorten not just the bulb’s life but also the battery’s.

The cartel’s justification for these changes was that at the higher current levels, the bulbs produced more lumens per watt. Alas, more current means not only more brightness but also higher filament temperature and therefore shorter life.

I have no doubt that LED lamps could be engineered to last essentially indefinitely --- well past the 100+ year record of early incandescents[1] --- but most consumers are lead by the advertising to seek higher brightnesses, which are achieved by running the LEDs at life-shortening higher currents and temperatures.

Newer ICs with small feature-sizes are subject to far more current density and electromigration stress, to the point that CPUs are not expected to last more than a few years, whereas older ICs may remain functional for many decades.

Memory and storage densities are also subject to the same effect, where it seems "capacity and speed is everything" and data retention and endurance have been sacrificed. NAND flash started out at 100K+ cycles per bit and 10+ years retention; now it's more like 1K and 1 year.

[1] https://en.wikipedia.org/wiki/Longest-lasting_light_bulbs
Curious if you've researched the expected accuracy and variance of the cheaper products. 10 points is significant, and it's my understanding that even the brand-name stuff varies by a few points.
There's also virtually nothing in rural areas. The game is certainly biased for certain areas over others, and people outside of those areas are effectively excluded from participating.
What state and county are you in? Agency formation rules are state specific. Asking a county fire agency is probably a good start.