skysight-inc/HackerNews huggingface dataset:
Indeed, but I'd like to add that these recruiters are often penalised if the candidate leaves the business before a set period.

So they have a financial motive with not just placing a candidate, but also them staying there.
Note that the "take the first codepoint" approach doesn't work for all languages. Take Hindi for example. This is a name:

प्रेरणा
'preraṇa'

The convention for initials in Hindi is such that this would be the "initial":

प्रे॰ (< प + ् + र + े + ॰)
'pre'

which is the first four codepoints combined (because they are in some sense considered a single character) plus another codepoint!

If for some reason you needed to respect locale-specific initialism conventions for a lot of different locales, it might be worth introducing an abstraction for determining the initials of a name.
Without the influence of LSD I don't think you would have gotten the Mac. You would have gotten Guis inspired by Xerox park but the whole vision of the computer as a work of art and a device to make art that was tied into Jobs inspirations from his psychedelic experiences.
I wonder how long we will keep hearing the complaint that Swift keeps changing. I never saw that as a problem at all, 99% of the changes have been for the better, and most of the time it's exactly the things I have wanted them to change, or add.

For the first few days after the announcement I couldn't see the point of Swift, why did Apple feel they needed a new language? It's not like there was a dearth of developers in objc. I started reading the Swift book from Apple though, and when I finished it a few days later I was hooked. Since then I haven't voluntarily written a single line of objc.

Of course circumstances may vary but for us migrations between Swift versions, even the biggest ones, have never taken more than 2 hours. Learning the new syntax as a developer I see exclusively as a positive, it's exciting to see how it develops. WWDC is Swift Christmas.

Again, each project and each developer is different but I can't shake the feeling that at least some of the objections raised by obj c diehards sound like pretexts, especially the talk about the language being in flux. It's not like you're forced to adopt the new version immediately, and in any case APIs also change. It's just part of the job. And Swift can't improve if it's not allowed to evolve.
Isn't inflation strongly negative? In the link I posted above, Fred Wilson exhibits behavior typical of deflationary times: people hoard the currency.

That's a strong disadvantage vs nation-state currencies, which have clear inflation targets (generally in the 0-2% range) and the ability to hit them. It may be great for speculation, but it's terrible for a medium of exchange. For that, you want the value to be constant or very slightly decreasing.

And I don't think that's fixable. If the Bitcoin supply is limited but those tokens are used in a world of continuous economic growth, then Bitcoin will always be deflationary.
Art installation intercepts all pager messages
Selecting good features – Part I: univariate selection
It has Indo-European roots https://lrc.la.utexas.edu/lex/master/0821. Although Tamil is Dravidian, probably a loan word.
In one of the linked posts he says that 100% test coverage might not be truly achievable, but it's nonetheless a valid asymptote to aspire to.

I think that exact argument applies to designing ever-safer, ever-better languages. You might never have the perfect tools that ensure 100% program correctness, but it's sure as hell what a tool-maker should aspire to.
Ask any performance expert and they will tell you not to prematurely optimize your program. All of them. Yes, every single one of them. 100% of people with deep performance experience will tell you not to prematurely optimize your code.

I have spent much of my career working on performance-sensitive and/or resource-constrained systems of one kind of another, and the above is simply not true.

Performance is like security or reliability. Yes, sometimes you find local weak spots, and sometimes you can do something locally to improve them. Profilers are great and changes should be based on measurements of real performance; no argument from me there. But in general, these are global concerns. You can't always retrofit "acceptable performance" using a profiler and local changes down the line, any more than you can retrofit "robust security". If it matters for your application, it needs to be considered from day one, and your overall design at least needs to allow for doing the right things even if you choose to not then implement those things in full immediately.

Needlessly busting your cache is a common source of performance problems on many modern platforms, and that is essentially what you're doing by passing inline functions as props when rendering React components whose render algorithm is expensive enough to use shouldComponentUpdate.

Ironically, from the discussion later in the article, the author does seem to understand to some extent, so it's frustrating that they still lead with such a patronising introduction, and that they keep generalising their own experience when not everyone will be working on the kinds of projects where the same assumptions are valid. There are some useful ideas in this article, which I'm sure would be relevant to a lot of React-using developers, but they get a bit lost among the strange and/or dubious assumptions that underpin much of the author's arguments.
Huh? I thought the title was a perfect description of the article. A dude who mostly uses ruby optimizes a piece of Python code. That's it.
Honest question, is anyone building new apps and actually care about older browsers? We’re using svg for everything now and haven’t run into a problem with support.
It can't be a scientific explanation, as far as I can see. That needs experimental testability of concrete predictions. It can be a reasonable philosophical speculation however.
> When was the last time you spent a pleasant evening in a comfortable chair, reading a good program?

Because all the classic, good programs that we use daily are full of ifdefs to account for all the compilers, architectures, etc. and the true, pure intention of the program is completely lost in this disgusting conditional-compilation-mess. Just go read xterm source or something like that. I tried.
PlanetCrap 6.0
You should expand this into an article or blog post!
Not that they’ve religiously followed it outside of their early years but Google has dropped “don’t be evil” over a year ago.
I don't have any statistics on how many iOS apps are just "thin clients" but I wouldn't think it's more than half.
Hotmail apparently! 2001!

Honorable mention to my MySpace account, from 2005. Which I just visited and it took much longer to load than a random more recently created one. I wonder if they archive old accounts?
I've seen a number of YouTube and liveleak videos that were obviously made by recording a security monitor with a phone. Seems to be an acceptable practice for certain genres, and is usually credible.
This is what Kant said. That space and time are pure forms of sensible intuition.
1999 Oldsmobile Alero

It had major engine problems and they were repetitive.
Your comment reminded me of how my friend and I would play that game. It felt so mischievous and exciting. It's nice to hear about it again and I agree, a similar game would be a blast.
It was not presented as a “transitional tech” at the time, it was presented as an equally valid/supported way to build even new apps. Also, for a very long time there were things you could only do in Carbon, and arguably that was still true at the time it was deprecated. Apple just makes bold moves that aren’t always clean breaks.
Excellent.

The video is very good, the presenter explains why the car is terrible, pointing each one of the terrible design decisions.

It looks like some software projects I've worked on:-)
That's not his point. He is claiming he can record a fake video that plays on a screen, and the resulting recording will look like a recording of reality, not of the screen (and the camera will sign it as such).
Isn't this why sometimes entire paradigms can be implemented as libraries in Lisp? Isn't the whole idea of DSLs dependent on this?
Your less controversial example doesn't quite map, though, because climate change is something that can be tested and observed; like you said, you can construct experiments at home to help people understand it.

There's no experiment I can construct that helps people understand that black people are people too. There's no science I can point to which establishes that women should be treated the same as men. There's no journal I can cite that explains why Jews don't deserve to be rounded up and exterminated. Stuff like that is axiomatic; I can't construct a logical argument to show you that people deserve to be treated like people, it's just the case. If you think that some subgroup of humanity is less than human, I'm probably not going to be very effective at changing your mind; any counterexample I show you can be written off with "well, they're some of the ~good ones~, but it's all the others who are the problem". Change really has to come from within on this one.

And I think your extreme example of our president kind of works in my favour, as opposed to yours. Trump said and did (and continues to say and do) a lot of extremely heinous shit. We have him on video discussing how much he loves to assault women, and how they just let him do it. And instead of saying "No, that's not acceptable, full stop. This is wrong and people who do this are wrong", there was a lot of "oh well it's just boy talk, they were just chatting like boys do in the locker room, it wasn't really sexual assault because he said the women let him do it", and it turned into a debate about whether or not sexually assaulting women is wrong and whether or not bragging about sexually assaulting women is wrong. And now Trump is president, despite the fact that he habitually sexually assaulted women and is proud of the fact that he habitually sexually assaulted women. By providing a platform for logical debate of something that is heinous, the heinous action gained legitimacy and ended up being okay.
What is "this?" The paper uses category theory as its lingua franca.
Ask HN: Are there tutorials that guide thru several implementations of parsers?
I am self-teaching, trying to learn the differences between different parsers. But just reading about them, I don't have any clear idea. Are there any tutorials or code examples with comments in any language that explains the techniques?
Yes there is a difference between acceptance and payment use. However they extrapolate that it's declining based on a way too small sample size: 2 retailers stopped accepting BTC so they infer global acceptance is declining... That's just ridiculous.

For all we know the JPMorgan report making this claim could be wrong, as it doesn't even list which 500 retailers it studied, and which are the 2 that dropped Bitcoin. I wouldn't expect quality Bitcoin research coming from JPMorgan anyway, as their CEO is staunchly anti-Bitcoin, so their analysts are probably not enticed or instructed to spend that much time and effort studying it.
> "...Money’s sexy I guess"

The founder really summed his sole motivation right there. This is a mercenary company that could have been created by a hedge fund.

Unlike Amazon, no one would want to work at Flexport except people focused entirely on money, and those aren't the best people.

This company is another (still rare) example of 1999 style VC investing. It will either flip or implode within a couple years. See: Zenefits
It would be really good if the author actually linked to somewhere where you can reproduce the benchmark. Either way, I'm pretty sure the correct response is "use pypy", not that I can check it
> stealing the network away from the Core development group

In theory, the "economic majority" controls the consensus rules, not miners or developers. https://en.bitcoin.it/wiki/Economic_majority

I'm guessing Core will be prepared to reluctantly merge segwit2x's consensus rules and release a new version in the case that segwit2x succeeds. Core wouldn't lose much market share if they act quickly.
One of the universities I was attending had a policy that when you get all answers on a multiple-choice test wrong, you get an A, because the probability of that happening by chance is impossibly low. Seems like 1951 Hoffmann is an example of that attitude ;-)
Agreed. Willingness to break backwards compatibility is good in pursuit of a better language. wish C++ did this!
I'm not so sure that we're missing anything basic. The top rated answer by Scott Aaronson seems spot on to me. The natural numbers are just too powerful. As the resolution of Hilbert's tenth problem shows, we can at best hope to solve special cases of statements involving natural numbers, and the solvable cases are bound to require techniques of increasing complexity.

What would count as a "master theorem" for some field, anyway? I suppose something like Tarski's quantifier elimination of semialgebraic sets over R^n might be an example, though for actual computations the best algorithms have double exponential worst case complexity (i.e. even worse than integer factorization). Or for something even more basic, perhaps the fundamental theorem of linear algebra (along with Gaussian elimination). There's the saying that mathematics is the art of reducing any problem to linear algebra -- I suppose the hard problems in number theory are the ones that don't have a good linear algebra reformulation :-)
My favorite way to end civilization would be a gamma ray burst. It travels at the speed of light, so there's no way to know it's even approaching. And it'd probably irradiate the whole solar system, so a Mars colony wouldn't save us.

Hmm... What are some other tempting apocalyptic scenarios? Asteroids are so 1998.

One thing that's bugged me is being born so close to the invention of nuclear weapons. If we're a random sample in all of human history, then why were we born so close to the birth of nukes? If humans are going to be around for another few million years, it's a minuscule chance that we should be born right now instead of much later.

You might think there have been a hundred billion humans born, so that logic doesn't really work: it's a one-in-a-hundred-billion chance that we were born here anyway. But the population is spread out in a J curve over the course of eons. It's not evenly distributed. https://en.wikipedia.org/wiki/Doomsday_argument

It's fun to waste time thinking about such things.
Meh... that already isn't a barrier. Analogues of heroin (fentanyl, etc) are legitimate Rx drugs today.
Correlation does not imply causation. Did I really have to tell someone on HN this?
Good point. I didn't think of synergy effects.
I'm left handed. Keys are in the right pocket, since most cars have key holes on the right of the steering column.
This sentence doesn't really make sense, insofar as TFA isn't about some conjecture.
Relationship between computation, logic and topology.
People could still experiment with schedule 1 drugs. Sure it's a lot of paperwork, but it can be done, in fact this MAPS study proves it!
I meant to say "also a proof of this".
Agreed. Add to the fact that much like AIM back in the day, Kik is pretty craptastic compared to competing messaging apps. But, it's so fast and reliable that it makes it worth using.
how about "border-radius: 50%"?
> A former employee of theirs told me that at one stage they were replacing ad content with their own adverts

This was afaik the main reason, why YouTube went HTTPS-only very early compared to the rest of the internet. Some ISPs exchanged the video ads of YouTube with their own and lowered the resolution of videos to save bandwidth. YouTube's customers were very dissatisfied because it constantly broke and the video quality was very bad and thus HTTPS came to the rescue.
This is an assignment from Georgia Tech’s OMSCS 6601 class, Intro to AI. This was a super fun assignment, with lots of low hanging optimizations like this :)
This has been "obvious" many times over the last 9 years. What's different this time?
What It’s Like to Drive a Tiny Car Designed for Drunk French Kids
There you go again, sillysaurus! Being born 65 million years ago didn't help you either. Maybe it's just you...
There are still numerous ways to circumvent the paywall [0], or else linking to WSJ would be against the guidelines [1]

[0]: https://github.com/njuljsong/wsjUnblock

[1]: https://news.ycombinator.com/newsfaq.html
Coinbase to support BTC and Segwit2x
There are laws about that. I would guess those laws are the reason that other delivery firms don't offer evening delivery, but I don't know if Amazon might try and get away with it.
حساب الحمل بالاسابيع بسهوله وتوقع الولادة الطبيعية – حياتنا الصحية
The "rubyist" is completely irrelevant to the article. The optimizations might apply as well in any number of languages, because they all are related to minimizing heap allocations and keeping the execution pipeline lean (e.g. by minimizing function calls).

It's fairly easy to think from the title that the article is going to be something about how clever the rubyist is compared to Python programmers or how slow Python is or some such, as an intrinsic property of "rubyists" or Python.
The Myth of Quality Time (2015)
> more easier to understand.

Precisely!
The book Black Swan counters fallacies like this reasoning.

1. Since his example (the fall of the Berlin Wall) is a one time event without any historical data and can only happen once, it's glorified guessing.

2. He ignores that a bell curve is specifically for results that have very predictable ranges. In Black Swan, Taleb calls this "Mediocristan" because the range of height of adult human males holds roughly to a predictable range aka we don't run into men who are 6 inches or 10 feet tall.

3. By taking this once in a lifetime event and applying a bell curve to it - as if the existence Berlin Wall was a gaussian event - he's trying to make guessing look like science.

4. After declaring it "proven", he goes on to compare it to another one time event.. then end of human life.

If he was talking about a regular event with historical data, this may be useful analysis but as is.. oh, he's selling a book. Got it.
>As someone who works at a large company, $10k is in no way "a drop in the bucket". Sales teams might have a budget to wine-and-dine clients, but as a developer I have pretty much zero budget and every expense has to be justified.

My idea was mostly meant for stuff in the category of Nginx, OpenLDAP, Postgres, Mongo, Elm, and co -- stuff that's used as the backbone of projects or services.

So, not just what some random developer in a big company might ask for their personal use. So, not something that some developer would need to justify for their use, but something that has to be accounted for when planning for a new project ("We'll make it in the Foo framework, which costs $10K/year for a company of our size").

If that was adopted, in the end, it would be a budget item like anything else. If they can pay $$$ to IBM and Oracle, not to mention the untold millions made by widget makers, chart libs, and the like, then they can pay a measly 10K to a project they rely on.
iPhone X iOS 11 Snapdragon 835 Octa Core Retina Screen 4G LTE 64GB 256GB
They have to deal with thousands of patent trolls. I'm assuming that they have to do this, otherwise they'd set a precedent, not strictly in the court room, that they have been subdued. IANAL, but I think that any firm of this size would be aggressive when you start throwing such statements.
We are not a random sample in all human history. We are, by definition, the sample of population in human history alive at this moment.

Us being here contemplating it says nothing of the probability of being born now vs some other time. Other than that its probability is now 1 because it has already happened.
>Hmm... What are some other tempting apocalyptic scenarios?

Pretty good list here: https://en.m.wikipedia.org/wiki/Category:Doomsday_scenarios

Cobalt bomb is terrifying. Doesn't require WWIII to snuff us out.

Edit: "gray goo" is also interesting. Self replicating nanobots run amok.
My bogometer started ringing immediately. The article even calls out what the problem is, but offers no resolution or explanation of how it doesn't kill the whole hypothesis. The problem is that the figures you get are profoundly affected by how far you are from the start. How does this not erase all of the presumed information content?
I think it has been in gdb before Swift.
TTD is efficient and works to add as little as possible overhead as it captures code execution in trace files.

...and then in the table below the screenshot...

Large overhead at record time. May collect more data that is needed. Data files can become large.

Based on past experiences with debugging using tracepoints etc., I'm more inclined to believe the latter.

Also, as a side-note, the "more modern visuals" of "WinDbg Preview" look horrible. It's a debugger, not a toy for the barely-computer-literate. Those who want the "friendly experience" will use Visual Studio instead, which amusingly enough continues to have menus instead of the disgusting ribbons as of the latest 2017 version. The screenshot also shows two lines of slightly-misaligned "Command" "Memory" "Source". Yuck.

(For those who don't understand, this what the original WinDbg looks like --- simple and functional: http://sandsprite.com/blogs/images/main_ui.png )
Saving you a click: with 95% confidence, humans are predicted to go extinct between 5,100 and 7.8 million years from now.

The prediction seems neither very robust (normal distribution?), nor very useful.
I agree, but the Tesla spokesperson didn't deny, and instead shot back with:

> For over a decade, the WSJ has relentlessly attacked Tesla with misleading articles that, with few exceptions, push or exceed the boundaries of journalistic integrity. While it is possible that this article could be an exception, that is extremely unlikely.

I want Tesla to succeed, but as far as I see it, the burden of proof is currently on Tesla as they fell incredibly short of their claimed production goals for Q3.
Losing a plane full of people is a tragedy. Losing a few million passwords is not. Actually, my email addresses and passwords have been leaked many times and it's not a big deal. Makes a barely noticeable difference to my spam folder.

These are very different levels of risk. Of course they are approached differently.
7 Days of Free Kubernetes
Not really no. Security wise, they remain one of the most badass actors on the field. I am very sure that my data and passwords are safeguarded. Same can't be said about Yahoo, Bing, or other companies/products.
True, I'm out on a limb here.

But the "news" part of Science is very good, and has insightful coverage of science activities. In comparison with the rest of the magazine, the published research in Science was...meh.
The author dismisses a lot of things as speculation that several years of hard data on my own projects say can be real. It doesn't take much in the way of large tables or lists or SVGs to be in a situation where your costs for rendering and/or reconciliation with the real DOM are significant.

The bottleneck typically isn't the time to build the new function every time you render the React component. The problem is that doing so can remove all of the benefit you would otherwise get from using a pure component (or otherwise implementing shouldComponentUpdate), because each function you pass in as a prop will have a new identity and therefore will not compare equal to the previous one, even if in reality it is calling the same underlying function with the same parameters so nothing material has changed.