skysight-inc/HackerNews huggingface dataset:
I think you're right, if a large portion of a company's stock is owned by passive funds, there should be some arbitrage opportunities since the funds won't buy or sell based on the company's fundamentals.
FWIW, this would be a literal s-expression translation:

(mrow (mi x)
(mo =)
(mfrac (mrow (mo -) (mi b) (mo ±)
(sqrt (mrow (mi b) (msup (mi 2)) (mo -) (mi 4ac))))
(mrow (mi 2a))))

And this would be a saner one, where mrow is implied:

((mi x) (mo =) (mfrac ((mo -) (mi b) (mo ±)
(sqrt (mi b) (msup (mi 2)) (mo -) (mi 4ac)))
(mi 2a)))

I think either of those is clearly and inarguably superior.
As with scythe, you're ignoring the greater point to focus on tactics that it makes irrelevant. C started with stuff that was literally just what would compile on an EDSAC. It wasn't good on about any metric. They couldn't even write UNIX in it. You know, software that people wanted to use. So, seeing good features of easy compilation and raw performance, they decided to invest in that language to improve its deficiencies until it could get the job done. Now, what would UNIX look like if they subsetted and streamlined a language like ALGOL68 or Modula-2 that was actually designed to get real shit done and robustly?

It's programming, science, all of it. You identify the key goals. A good chunk of it was known as Burroughs stayed implementing it in their OS's. Their sales numbers indicated people wanted to use those enough they paid millions for them. ;) Once you have goals, you derive the language, tools, whatever to achieve those goals. Thompson failed to do this unless he only cared about easy compilation and raw speed at the expense of everything else. Meanwhile, Burroughs, Wirth, Hansen, the Ada people, Eiffel later... all sorts of people did come up with decent, balanced solutions. Some, like the Oberons or Component Pascal, were very efficient, easy to compile, easy to read, stopped many problems, and allowed low-level stuff where needed. Came straight from strengths of design they imitated. A form of that would be easy to pull off on a PDP as Hansen showed in an extreme way.

C's problems, which contributed to UNIX Hater's Handbook and many data losses, came straight from the lack of design in its predecessors which soley existed to work on shit hardware. They tweaked that to work on other shit hardware. They wrote an OS in it. Hardware got better but language key problems remained. Whether we use it or not, we don't have to pretend those effects were necessary or good design decisions. Compare ALGOL68 or Oberon to BCPL to see which looks more thought out if you're still doubting.
Wikipedia's Hexagon entry (https://en.wikipedia.org/wiki/Hexagon) explores the mathematical side.
I was one of Scott's early hires and he knows what he's talking about. ProPublica was conceived [1] as a place to do the old-school, indepth investigative journalism that newspapers did before newspaper revenue started tanking. I was hired as a web producer and ProPublica's work would still be going on today with a traditional web presence. But news application development was not necessarily baked into that mission. Now the developers work as journalistic peers with the investigative reporters, as well as developing tech, designing and deploying applications. That wouldn't be the case if Scott hadn't continued to emphasize that there's more to his group than just maintaining the website...such advocacy is needed even in a small, flat-hierarchy, forward-thinking organization.

[1] https://www.propublica.org/about/press-release1
There is Pony (http://www.ponylang.org).
> A simple solution (for the elderly at least) would be to roll up all the debt until death, payable by the estate.

Simple until the next housing crisis.
Not directly. But it promotes a land grab by entitling the owners of that land, and discourages redeveloping existing properties bigger because the owner would then lose the entitlement have his property taxes increased.
Honestly, I'm with you on this. Still stacking up on index but everyone will have to switch at some point.
That threw me, but I think it's for the entire endowment.

I was just shocked at the shoddy reporting of the numbers.
https://gitlab.com/stackshuttle/grow_journal

A webapp to create journals for the plants you're growing. It is using elixir/phoenix.
Always looking for contributors :-)
*per month.
> When I claim it's a feature, but describe the pain it is to use, I get told nearly nobody uses it. When I claim that nobody uses it, I get told that lots of people use it.

Heh it is funny. I might have an idea why. It is hard to use regularly to perform day to day releases. Simply because building correct apups and so on take a lot of time. Most systems are already decomposed into separate nodes and cand handle single node maintenance, so that is what we do at least. Take a node down, upgrade, bring it back up. Care has to to taken to have mixed version in a cluster but that is easier than proper 100% clean hot upgrade.

But having said that, I have used hotpatching by hand probably 5-6 times in the last couple of months. Once on a 12 node live cluster. That was to fix an one-off bug, for that customer before having to wait for a full release, another time was to catch an function_clause error that was crashing gen_server and so on. It was is very valuable having that ability.

> till, at this point, if someone's going to claim that Erlang could go C speed or even close to it in the general case, I'm very firmly in the "show me and I'll believe it" camp.

It doesn't matter if it goes C speed, it has the fault tolerance, expressive language, it is battle tested, it has good runtime inspection and monitoring capability, if someone came one day and said you lose all those but you gain C speed, I wouldn't make that trade.
Zero on average every 3 months is a lot different than zero ever. Reddit is a website most of its users use long term, not some random app you might use once a week or once a month. Their app will be downloaded a lot, and having tens of millions of downloads on unofficial apps is proof of that.
I've been using https://github.com/Olical/react-faux-dom with d3 without issue. The project lists the following caveats:

It's great for...

- Static D3 components or other such libraries (things like Backbone should work too!)
- D3 components with simple state and event interaction, like tooltips on charts
- D3 components such as progress bars that can be animated using react-motion, for example

It's not so great for...

- Physics based D3 components or anything using a lot of DOM mutation and state
- Linked to the previous one, brushing and filtering of selections using the built in stateful D3 tools
- Essentially: Anything with a lot of DOM mutation from timers, events or internal state will be hard to useation from timers, events or internal state will be hard to use

But I've mutated state in an onMouseOver event, redrawn and it's buttery smooth.

node
.on("mouseover", (d) => window.requestAnimationFrame(() => this.setState({selectedElementId: d.id})))
.on("mouseout", (d) => window.requestAnimationFrame(() => this.setState({selectedElementId: 0})))

node.filter((d) => d.id === this.state.selectedElementId)
.select("text")
.style("text-decoration", "underline")
.style("font-weight", 'bold');
Has anyone tried to work out what percentage of the market is covered by rent control?
I'd honestly be happy enough with an open-sourced AB that the community took back on.
http://www.exfiltrated.com/queryport.php?Port=4070

All those IPs are on networks behind doors.
Some of us had to build their own last 10 miles of the Internet.
I can think of a few reasons:

- The field name implies that the primary key field is a string. This entails numerous issues (eg. How do you generate a new unique ID?)
- It is not obvious that the field is the primary key.
- A 'name' property on a reservation doesn't make sense. Is it the name of the person making the reservation? How can this be unique? etc.
I, too, spent some time reading this book, and arrived at the conclusion that it's terribly written.

From a mathematical perspective, the book does not define hardly anything. Take, for example, the important chapter on Deep Feedforward Networks. They hem and haw saying things like "quintessential deep learning models" but never actually explain _what a deep feedforward network is_. There are no definitions: they give what amounts to preamble of a definition, and then move right on to using the notion, but don't actually give the definition itself. In the deep feedforward network example, the closest thing to a definition is, "A feedforward network defines a mapping y=f(x;theta)". That doesn't really say anything though. If you're asked to define "dog", you can say, "A dog has four legs", but how does the reader know that a cat isn't a dog?

I find that for basic machine learning it's much better to just go through machine learning framework tutorials. For advanced learning, I'm not there yet so I can't speak from experience but I'll be shocked if this book fits well in any role except maybe last-resort reference material. If that.
ALGOL68: The language Thompson, Ritchie, and Pike basically cloned when they made Go. Nothing went in there unless everyone agreed on it. Final was every feature they had wanted in a language. Most of which was already in ALGOL68 with key aspects in use by Burroughs since their 1961 designs. Had they just subseted or simplified ALGOL68, they'd have quite the head start and we'd be stuck with a language that's a lot better than C. I imagine the implementation would've been more suitable for OS development, too. ;)
The article is talking more about the declining average load due to passive funds. If the average load goes down, I'm saying that those fees are probably just moving somewhere else rather than upsetting the industry.
If anyone is interested in Carmack's backstory I recommend picking up a copy of "Masters of Doom: How Two Guys Created an Empire and Transformed Pop Culture." It was published in 2004 so don't expect any of the newer stuff he has done but it is quite the read.
Monty Python's John Cleese Almost Explains Our Brains (2013)
>I ran across this study a few months ago that says IQ-like tests, structured interviews (canned questions), and work-sample evaluations were some of the few useful interview tools for selecting good employees [1].

They're great for determining which employees will be productive

They're entirely terrible for figuring out which employees will be decent people to spend 9-5, 5 days a week with.

Realistically you need a bit of both
You've done something wrong then? Or maybe using experimental features? I might play with them a bit, and it can be frustrating to wait, but I've never launched anything on -experimental before.

I was referring to "cheating", with the idea that you might pollute your Actors with... I dunno. Programmatic connection pooling for your database driver? Passing mutable messages around?

Both of those things would be very unusual in Actors written in Scala since pretty much everything is immutable by default. Seeing that sort of thing should at least raise some eyebrows.

As far as non-responsive, I've never seen that. But I do take care to use Futures where appropriate, and pipeTo. Maybe it's good habits, or maybe I'm just very lucky.

One of my first Akka projects is still running, still processing content it's notified of by Postgres through LISTEN/NOTIFY, still posting that content into Cloudant (basically a managed Lucene deployment in this case).

And it's been running since September 2014 without a restart AFAIK. Which would have never happened with a previous non-Actor solution we might have used if for no other reason that a network blip might detach the listener, whereas here the Actor just restarts.

My experience has been overwhelmingly positive. Despite doing the wrong thing occasionally.

If you have Actors that are hung, I guess the first thing to try is figuring out which one(s). After that, you could just schedule the supervisor to routinely PoisonPill them, and forcefully stop them after a grace period.

I'm not sure that OTP is going to help with this sort of issue either. You have an apparently blocking process that makes an Actor non-responsive. The fact that it's single threaded within the Actor and stalls it's mailbox is kind of the point of Actor systems AFAIK.

I guess one thing I feel like helps me is to keep my Actors small and doing one thing. It's hard to do too much damage when you only have a dozen lines of actual message handling. "One thing" is sometimes coordination/aggregation BTW. Which means I might have a GetRequestActor, PutRequestActor, DeleteRequestActor, etc. Which do the one thing. But then I also have a DatabaseActor that basically just coordinates/forwards for all those so you don't actually have to deal with them yourself.

And from there if I decided that no GetRequestActor should take longer than 10 seconds to do it's thing, I can easily schedule the DatabaseActor to forcefully stop any task exceeding it (without the need for an actual watch if you choose). Which you can then log an ERROR for and work out why. And maybe some requests just take longer and that's OK. So maybe you then write a LongRunningRequestPathExtractor and put that pattern before the normal one. And now you can have multiple timeouts for different paths.

Or maybe you just record the epoch for different requests, and if you've had 1,000 updates since the last View request, you know the next one is going to trigger a reindex. So you give it extra time. Or you set it to allow stale results and reschedule the same call to occur again in 1 minute to minimize the disruption of indexing the changes. Just some thoughts.
True but even with these, the percentage of rental units in SF that are rent-controlled is something like 75%
Describe precisely how that works please.
> The op was imprecise.

True. Edited my comment.
Seems to still work in my small codebase, but I get a series of type warnings.

Typings still has 0.14 tagged as the latest - I'm guessing we need an update there too?
I just tried the new release. The data-reactid is indeed gone when rendering on the client side. But on the server side, the html string generate by ReactDOMServer.renderToString still has data-reactid. Is it because client side can validate the server result and decide if it needs to re-render the page?
Speaking as someone with a cognitive science background (and yes, probably too lazy to dig up specific references), I'll say that there exist a lot of poorly designed or poorly implemented tests of "intelligence". Even the concept of intelligence is poorly defined, and lots of different measures are just proxies. Even if the test is good and has some psychometric utility, often giving the test is a giant pain to do well.

Even if the test is good, it's probably calibrated on WEIRD [0] subjects, so is really only good as another kind of gatekeeper - you can probably use old-school IQ tests as an excuse to reduce diversity. People who aren't WEIRD may not do as well on these tests (even though they're just as "intelligent" (parenthetically bracketing the ill-defined term for a moment)), so you have your reason that you only hire white dudes. But that's a cynical extension of logic there.

Most people, when approaching a psychometric test like one of intelligence or personality make the first incorrect assumption that modern cognitive science can actually form a construct like "personality type" or "intelligence" that's stable across all cultures and norms, testable, and repeatable. That's just not really true, and by and large what makes it to public consumption is pseudo-science.

Diverting just a little bit here, but MBTI [1] is another good example of bad use of psychometrics in business. There's about as much science supporting Myers-Briggs tests as there is astrology, yet people still use MBTI for actual decision making. Types aren't shown to be stable and they're not well-clustered (meaning you can be a mix of introvert and extrovert, or show signs of both depending on the day, context, mood). Zodiac Sign and MBTI Type should only be used as pick-up lines in a bar. "Hey, babe, I'm an INTJ, so I'm not going to say anything else."

There are good uses of psychometrics, but they're rare enough that I take any reliance on any kind of psychometric during hiring as kind of a bad sign.

0: http://blogs.scientificamerican.com/primate-diaries/the-weir...
1: https://www.psychologytoday.com/blog/give-and-take/201309/go...
For non-clustered indices, yes.
Care to elaborate? What do you find fascinating about it.
Interesting! Is that a hard-coded penalty or is there some sort of calculated weighted penalty per-domain based on some criteria? If the former, is it just due to mod experience of poor-quality/just link submissions?
5 Skills to Be a Machine Learning Engineer
Some examples:

In project management, tasks might have an assigner_id and assignee_id

In transaction management, transactions might have a sender_id and receiver_id

In sports, matches might have a team1_id and team2_id
30 Best Tools for Test Management, Automation, Performance and Mobile Testing
Here’s How Much Your iPhone Would Cost Under Sanders’ or Trump’s Trade Plans
Somebody suggested having a micro-kernel approach to load modules onDemand in production, e.g. SVG, renderToString will further reduce the initial load time / size.
Actually it sounds like one of my very early jobs where two of the three founders were husband and wife. So nice at interview, both of them. Bought me lunch at the end too.

The daily domestic and the weekly I'm asking you to do this because I'm pissed at my partner and I know it'll piss them off got very wearing.

Probably worst place I ever worked.
> If you are the type who wants to invest X% of every paycheck (i.e. making multiple trades a month), are only investing a small amount of money, or are only investing for the short to medium term, you are likely better off with the the higher fee and lower commission.

Roboadvisors like Wealthfront solve this problem more elegantly and at lower cost.
> I keep saying these same arguments put forth (add more affordable housing!) but the reality is that there are very specific laws that cause the crazy prices here and it ISN'T because of a lack of housing. It's lack of liquidity.

i'm confused, how does liquidity affect the housing market?

if you can admit there is plenty of housing then why are you unwilling to simply say, 'all of you would be tenants move into this available housing'?

i think what you really mean by liquidity, which i'll interpret as an owner's ability to end a lease when and how they want, is that people, you?, want to live in a specific part of sf but all the housing there is already filled and the city has determined that those tenants' livelihood should be allotted some predictability by local law

this is the thing that confuses people who have lived in a neighborhood for 4, 8, or 16 years

the reason you want to move there is because of who is living there

evict all you want and it will just be those that paid for their place who remain and if those people are so flush that they can pay any amount to consume the local culture they want, then the question is, will they be willing to contribute to a local culture or will the region stagnate as some former cultural artifact

the poor will live where ever they can afford, and if that place is boring and seemingly uninhabitable then it is on them to make it fun, and they will, and then they will need to leave because you want to be where the pulse is at even if it is the exact same place you turned your nose up to 10 years earlier

fillmore in the 30s -> north beach in the 50s -> haight in the 70s -> mission in the 90s -> ???

() https://en.wikipedia.org/wiki/Fillmore_District,_San_Francis...

() https://en.wikipedia.org/wiki/North_Beach,_San_Francisco

() https://en.wikipedia.org/wiki/Haight-Ashbury

() https://en.wikipedia.org/wiki/Mission_District,_San_Francisc...
DuckDuckGo implemented something similar a few weeks ago:

http://duckduckhack.com/

This is probably Microsoft's response.
This is covered in the article.
Nice! Can't wait for fewer mutual fund companies compete for my money! As it is, most brokerages waive the transaction fee when buying or selling a fund, unlike an ETF. Can't wait to see how they innovate next!
Just curious, how would you describe your friend?
>Is there really such thing as a passive fund?

To me passive and active are ends of a spectrum which specify how much labor and trading is done with the fund's assets.
assume by default that it is "a crappy boss / toxic environment" and try to find solid evidence to the contrary.

>However, a few months into the job I realized my boss was a complete and utter asshole.

well, that is view from your side. Are you sure that you aren't the one too? It is just a frequent situation that people are defensive in response to your [as perceived by them] "offenses". It is one of the most important skills if you're going to develop your career as corporate drone is to get used to work with different people around you.
Because in every implementation I've seen so far, the server software won't run without certain copyrighted assets extracted from the client being present on the server for it to run in the first place.
Yeah, the article mentions that they only cover pulse tracking, not arrhythmias, but I was under the impression that even the pulse tracking was somewhat iffy due to the nature of how the tracking is performed.

In fact, the article says there's a class action lawsuit because of it, which means using this data in a medical context could have gone very badly potentially.
Questrade in Canada lets you buy ETFs for free, as little as one share at a time. You only pay when you sell ($0.01 a share, minimum $5 a trade).

Anything sold by the big banks in Canada is almost always a ridiculous rip-off.

Even better might be something like Wealthsimple.

(Not affiliated with either company except as a customer)
With aliases that first expression might be:

c.id = p.id

That seems like an easy error to make...
So the thing is, "smart" is a pretty sloppy term. Furthermore, claiming that measuring this "smartness" in a small-sample, unrelated set of tasks (a relaxed, 30 question test), and that this "smartness" on the test would transfer to "ability to write good code well and work in a team" is utter crap.

Doing well on a test is usually an indicator that you do well on that kind of test. Even good psychometrics tend to fail with calibration problems - the vast majority of these tests were written and calibrated using psychology undergraduates at western universities. That's a significant sampling problem. [0]

So I'm personally not opposed to selecting for "smart" employees. But I do think that the belief that a short test actually selects for that kind of smartness in any meaningful way is sloppy thinking.

0: http://blogs.scientificamerican.com/primate-diaries/the-weir...
The Literary Magazine of the Dark Web
Anyone can register content with the ContentID database and choose to remove or put ads on any matching videos. Big players have access to delete any video they want from YouTube.
Didn't the Napster moment happen in the late 1970's when John Bogle started Vanguard?
It will likely strengthen the case for having react manage the DOM while d3 takes care of any fancy math you need, like computing the d attribute for a <path> in a line chart. Previously there were some SVG elements that simply couldn't be expressed in React and so you had to either push that DOM management onto d3 or dangerouslySetInnerHTML
Tell HN: I'm creating an autonomous racing series