skysight-inc/HackerNews huggingface dataset:
I commented before reading the article, just going by memory of reading about this before. Perhaps I was wrong about it not making sense in the language, but more that it isn't necessary when using ReactReason because the concept is built into that binding.
I think you’re misunderstanding. According to the report, it’s not just the Volvo emergency braking system that was disabled. Uber’s self-driving system had its own emergency braking feature that was also disabled.
Glad to see this here! Modern Day Babylon are great for those looking for instrumental work in the same sphere as the above. Disperse as well - Jakub Zytecki is a fantastic guitarist and features on a lot of David Maxim Micic's work.
This comment made my brain hurt. I think you have something interesting here, that’s why I read it four times and still didn’t understand.

Please re-write this for clarity.
Why America Is the World’s First Poor Rich Country
The pointer events contribution comes from PSPDFKit, a company that sells PDF SDKs for mobile, desktop and web. It's used in https://pspdfkit.com/web/
To me, the real takeaway is this:

> unlike, say, immigration law, there is weak enforcement of employment law.

For me in the US, this is the crux of the current wave of anti-immigrant sentiment. The problem isn't "immigrants stealing our jobs." It's shitty jobs that don't cover basic costs and have inhumane working conditions. But the people in power have done a great job of misdirecting people's attention to immigrants. Boy are they going to be disappointed when all the immigrants are gone and they still can't make a living.
> didn't want their emergency braking accidentally firing during normal driving causing rear endings.

In no case would sudden braking be the cause of a rear-end collision. It's always the fault of the driver behind.
IME using ClojureScript, you don't really need something like Redux/re-frame all that often either.

Once you've handled local state and remote data dependencies, you have like 10% of your app state left. That can easily be solved with a global atom (a la re-frame) or something like the new React context API.

Our understanding of how to handle state, remote data fetching, etc. has grown a lot over the last few years. Both the React & ClojureScript ecosystem went all-in on global state stores like Redux because, at the time, we thought we needed it. It felt like, if we needed a global state store for one thing, that it made more sense to just put everything in there for cohesiveness. It also was hard to determine up-front what was needed globally (mostly data IME) and what was only needed locally.

It turns out that local state and something like apollo/relay/"suspense" for remote data solve the 80-90% case, and now we're getting better tools like React context to handle the last 10%. I don't think that Redux/re-frame is going away, but the number of apps that I would implement with them has gone way down over the years.
Would love to see a timelapse of those thermal maps! I wonder if there are enough images of them over time to create a smooth-ish animation?
Also for your issue with deeply nested options, have a look at this

https://medium.com/w3reality/working-with-option-using-maybe...
Digital Forensic Report of TIDAL Streaming Manipulation [pdf]
bittorrent as a protocol isn't even any more secure over Tor, so you're just taking up bandwidth on the network by using it. Direct downloads and streaming may be less of a concern, but it's probably too slow right now to really do streaming effectively.
> "PostgreSQL 11 introduces SQL stored procedures that allow users to use embedded transactions (i.e. BEGIN, COMMIT/ROLLBACK) within a procedure."

Did PostgreSQL not have stored procs before?
Or TiVo, or the internet. I'm not sure how this is different from how you watch sports on cable unless you come across it randomly. Either way you need to find a schedule somewhere?
Again, not at all charitable. Your assumptions are baseless, seemingly motivated by little more than your mistrust that in the competence of people that have been actively working on this problem, many for years.
This is best done using the first sentence of a paragraph. Make a statement first and support it with the rest of the paragraph. At least that's a style judges use on verdicts. That way I can skim a long text easily enough.

The opposite is having a conclusion at the end. That's used for opinions. A severe disagreement (not to say error) can be found faster if building an argument from the ground up.

If your conclusion is somewhere in the middle and scattered all over the place, you might want to highlight that indeed. I prefer stream of conscioussness for quick notes, but bringing it into a proper format can help to refine the argument.
Show HN: Lass scaffolds a modern package boilerplate for Node.js
It does not follow that if we can trust a Government to price carbon emissions then we should be able to trust them to not print money. We are basically guaranteed that they will, despite being able to effective disincentive things like smoking with an excise tax.

It is trivial for Governments to implement a carbon tax which would improve environmental conditions for all energy intensive production.

With regards to giving power to people, this is not done through wealth redistribution (although you get a little bit of that). The mechanism is tgrough the constraint that the currency can not be debased. A rising tide lifts all boats, especially when there are not holes in them.
That's not the only hardware you're running though: those two cameras are connected to a sophisticated object-classification system with around 540 million years [0] of R&D behind it.

[0] https://en.wikipedia.org/wiki/Evolution_of_the_eye
>We've been converting a large JS react app to Reason

Is the process like say converting to using Flow where you can just add it in where you want and the application still runs fine, or by convert do you mean write a whole new application and when it's complete then launch?
There’s a kind of Moore’s law in batteries, but the multiplier looks more like inflation than 2x.

Any tech that falls outside of the growth curve seems to run into issues with production or cost that delay it until it fits under the curve. Something cheaper and easier gets picked first.

The first modern EVs had lead acid batteries. More sophisticated than your starter battery, sure, but lead acid all the same. Which is why Tesla was a big deal. We talked about LiPo for something like fifteen years before it showed up in consumer electronics, and then they started catching on fire.

All of this stuff is painfully slow. The big story in EVs is how crazy efficient the motors can get. A company I used to follow (whose name is escaping me now) had a motor that was 95% efficient in its sweet spot. They had scaled up the design to 100 HP.
Clickbait wording.
Getting paid by a US university.  Or not.
Some time ago I gave a talk at a US university. I said up front that I was happy to do it, and that I would provide an invoice from a limited company registered in England and Wales. I was assured that this would be fine.

Indeed, now I've completed the W8-BEN-E form and sent that in, along with my invoice, but now I'm being told I have to provide a "foreign tax id".

To the best of my knowledge I don't have a "foreign tax id".

So this post has several purposes. Firstly:

* Do I need a "foreign tax id", or are they just stalling?

* How should I get a "foreign tax id"?

* Should I just give up now?

I've done work in the past for US companies and it's not been a problem. This is the first time a block like this has been thrown up, and I'm wondering whether it's real, constructed, the result of changes in the law, or what.

So this might be a place for people to chime in with their best and worst experiences of dealing with US companies and organisations, and maybe along the way I'll get my answers.

Thanks.
The illumos project undertook a massive effort to eradicate any and all dependencies on Perl (which had also been made part of the core operating system decades prior, by themselves no less). While they're still at it, they have managed to rip out most of it and replace it with binary executables in C or shell.

Yes, writing a build engine in AWK would be perfectly doable, but the right tool for that job is Make.
12.15 on p 167 of http://cdn.batstrading.com/resources/regulation/rule_book/BA...
I dont think you've followed through on that model of yours.

If you buy 50 dollars of taco materials, then taco materials seller makes likes than 50 dollars ,because the state will charge a tax on him. If he didnt sell 50 dollars worth of raw materials, he would have 50 dollars of raw materials to consume, instead of less than 50 dollars.

On the other side, making the taco, you have the same issue: if you sell 100 dollars of tacos, and someone pays you 100 dollars for them, you then pay taxes.

You earn less than 100 dollars, and someone else lost 100 dollars. Repeat the proces ad-infinitum and your holdings go to 0.
I understand that emergency maneuver system was disabled so the car did not brake between t minus 1.3 and t. But why didn't it brake from t minus 6 to t minus 1.3? Looks like it detected that the car's and object's paths were converging, so why didn't it brake during that interval?
Why can’t we bury flywheels to protect from any explosions?
I'd like to throw out that one of the pilots of that flight was pulling up during a stall warning.

I don't think it's really similar to this accident, since it'd kind of be like the driver realizing they have to break, but gassing it instead.

Also interesting is that in a Boeing, this likely would have never happened. In an Airbus control inputs are averaged together, so the captain had no idea his copilot was pulling back during a stall warning. In a Boeing, the control gear provides feedback (physically moves) to the pilots, so they would have been able to realize they were giving opposite inputs.

Source: https://www.popularmechanics.com/flight/a3115/what-really-ha...

Excerpt below:
02:13:40 (Robert) Remonte... remonte... remonte... remonte...

Climb... climb... climb... climb...

02:13:40 (Bonin) Mais je suis à fond à cabrer depuis tout à l'heure!

But I've had the stick back the whole time!

At last, Bonin tells the others the crucial fact whose import he has so grievously failed to understand himself.

02:13:42 (Captain) Non, non, non... Ne remonte pas... non, non.

No, no, no... Don't climb... no, no.
The article doesn't explain much, but it sounds to me like the device mistakenly interpreted a voice command to record and send a message.
I dont think you've followed through on that model of yours.

If you buy 50 dollars of taco materials, then taco materials seller makes likes than 50 dollars ,because the state will charge a tax on him. If he didnt sell 50 dollars worth of raw materials, he would have 50 dollars of raw materials to consume, instead of less than 50 dollars.

On the other side, making the taco, you have the same issue: if you sell 100 dollars of tacos, and someone pays you 100 dollars for them, you then pay taxes.

You earn less than 100 dollars, and someone else lost 100 dollars. Repeat the proces ad-infinitum and your holdings go to 0. (assuming for simplification, any rate of positive taxation on income).
It's interesting that bitcoin (and crypto maximalists in general) repeatedly harp on and attack QE as if it was the end of democracy itself.

QE is just another tool for monetary policy designed to combat deflation and increase available capital supply as a stimulus measure. Because QE belongs to the school of thought that the economy is driven by consumer spending as opposed to consumer savings.

Could you please elaborate on what you mean by:
> steal money from the public with QE
?
the Suspense PR was merged in for this version (https://github.com/facebook/react/commits/master?after=fa7fa...) so you can absolutely start trying it out in 16.4. with the requisite warnings that it is still unstable. I keep a repo of all publicly discussed stuff on async react here: https://github.com/sw-yx/fresh-async-react for people's research convenience.
I did a study on Kroger, Costco, Walmart, Sams, Aldi, and Kroger was a scam.

Constant "10/10$" or "ALWAYS LOW PRICE $2.49" on items that are cheaper at Costco, Walmart, and Aldi.

As a note, Walmart won or was on par with Aldi. Aldi had a very limited selection despite having decent prices. Costco isnt worth shopping at for food item with few exceptions(canned food, which isnt very optimal in general).

Anyway, my point is, I dont really trust Kroger. They overcharge for items and claim its cheap. They even have an 'organic' section of the store, which makes me think is all marketing.

If anyone wants the link to the study, lmk, I avoid posting my link unless its relevant and wanted.
This reminds me that all those points would apply to dartlang
Masks, face altering, stickers, etc. I like this research about "Adversarial Patches" - stickers that confuse image recognition systems. I imagine one may wear a display with ever changing images that are salient and confuse such systems.

> Research Article: https://arxiv.org/pdf/1712.09665.pdf

> Video for patches: https://www.youtube.com/watch?v=i1sp4X57TL4
EIP-999 isn't backed by Vitalik but it was backed by major figures in Ethereum, including at least one co-founder. And yes it's dead.
Recap of Write the Docs Portland Conference 2018
Shouldn’t the decrease in available labor as a result of decreased immigration lead to wage increases? Particularly for jobs that aren’t going to be shipped overseas (construction, manual labor..).

EDIT: I know the topic of immigration can evoke strong emotions. I’m just pointing out that a decrease in labor pool ought to increase wages. Isn’t this just law of supply/demand?
> USDT is only 0.5%-0.8% of the market.

This is false. Market cap is a meaningless statistic when applied to cryptocurrencies. If I create a billion 'FOOCoins' and sell one to a friend for $1, FOOCoin now has a 1 billion market cap, but only a single dollar has changed hands. He sells it back to me for $2, now FOOCoin has a cap of $2 billion! With only $3 having changed hands.

This is clearly an exaggerated scenario, but it does show that the market price multiplied by the number of coins is not meaningful.

> Do you really think that a 300-500 billion dollar market is being propped up by less than pennies on the dollar?

I don't think it's a 300-500 billion dollar market.

In fact the article you linked to goes on to explain this very phenomenon! That in fact it's possible that only around $6 billion in inflow has gone into cryptocurrencies, ever. This puts tether at around 1/3 of the entire inflow. Is that still trivial?
Mistake? Turning off emergency braking because it happened too often then continuing to drive on public streets isn't a mistake. That calls for a custodial sentence.
The third point is incorrect. It will be implemented on Mindgeek sites and any other sites that wish to use it instead of the competing age verification products.
"at least we’re only partially wreckless" has been Tesla's standard operating procedure for a while now. I'm guessing you think Tesla shouldn't exist either.
You could even use ReasonML without React, and build complex web apps, by going an even more Elm-like route with:

https://github.com/OvermindDL1/bucklescript-tea

Here some demo code (in ReasonML, not OCaml):

https://github.com/feluxe/bs-tea-starter-kit/blob/master/src...
Hmm, you're right. I didn't mean to suggest that basic income should be based entirely on cost-of-living, though. My thinking was something more like:

NewUI = OldUI * (CostOfLiving[NewJobMarketLocation] / CostOfLiving[PrevEmploymentLocation])

Thus, if you got paid the going rate for a factory-worker in Michigan, and you moved to SF, then you'd now be getting the UI that a factory-worker in SF would be receiving if they had been getting paid the going rate for factory-workers in SF. So you could afford to "switch" to the SF jobs market, or any other jobs market, and compete for jobs with the unemployed factory-workers currently living in the SF area: you'd be able to afford to live roughly where they live, feed the family you moved with to the same standard they were used to back home while you're job-hunting, show up in clothes of the same quality they show up in, maintain your car as well as they do to get to interviews at roughly the same time they do, etc.

But that assumes that there are factory workers in SF. There aren't—running a factory in SF is an unprofitable proposition. Whether or not you could come to the area and job-hunt, supply of your job (or any job at your pay-grade) might just not be there to meet your demand.

And that's not even accounting for the second-order effects: decreasing friction of movement between jobs markets would cause everyone else who ever wanted to live in SF to also come there to job-hunt. So, even if there were some factory-worker openings right at the beginning of this policy, they'd quickly be filled, and the markets in cities like SF would come to resemble Hollywood: a place where you have to put up with unreasonable amounts of shit to get anywhere, because there's so much more talent who has come from all over to vye for attention, than there are productions needing talent, that the productions take absolutely no care in how they treat their talent.

In other words, at equilibrium, you'd just be back to where you started as far as "number of people employed" goes, at most levels†; and you'd also not see any change in the population density, demand for gentrification, or any other such thing in these cities, because Unemployment only lasts a fixed amount of time—you can't afford to stay if you don't succeed in finding a job. The one thing that would change is that companies the nation over would be seeing far more "talent liquidity", and thus thinking of employees as even more fungible/replaceable than they do now. (But, the flip-side of that statement: an individual new hire at an SF company would now have much more even probability of having originated anywhere in the country.)

---

† Maybe you'd get more startups, from several people coming to SF (or other expensive cities) and deciding to spend their UI as initial runway to form a company together. But that'd be the exception, not the rule, I think. (Might still have nice knock-on effects for employment if those companies need to grow by hiring later on, though.)
Should we not count dependencies that are comprised of nonsense dependencies as nonsense themselves?

In my opinion, fork it and fix it or stop using it. Also, warn others if you have the capacity.
I would recommend you make this clearer in the readme, as I wasn't left with the impression reading the documentation that the tool was for limited scenarios and scope.
As Tesla’s share price falls, it becomes an inviting takeover target
Until another browser implements proper tail calls as per the spec, I'll still have great respect for Safari, quirks and all. It's the only browser where you can write fully functional, continuation passing style code without fear of blowing the stack.

And all the fear mongering over "it makes debugging haaard" is just frustrating. Debugging is hard, there's just no way around it.

The Develop menu in Safari is also without equal in my experience. Quick access to almost a dozen settings each of which requires either command line arguments or buried toggles and restarts in Chrome (or myriad extensions).

I do wonder why the console doesn't use a monospace font. That's not the only problem with Safari, but it's one of the most off-putting, glaring issues. Makes you feel like the browser isn't intended for serious work. Which I guess some people would say is true.
Turning poor people against immigrants is a time-tested strategy to keep the heat off of employers. The old, "I think he's going to steal your cookie," joke.[1]

1. https://metro.co.uk/2016/08/21/a-banker-a-worker-and-an-immi...
My concern is that this almost sounds like something not customer facing was accidentally made customer facing imho.
'We develop new AI processors on the open RISC-V architecture'
The article makes it sound like the engineers didn't know what was going on, so it could be an actual bug, unless support was just trying to placate her.
One thing I also really like about Awk is that you can keep 99% of the language in your head. With Awk it is seldom necessary to even reference the man page. I don't have to interrupt myself with looking up the syntax or the order of the parameters to a function.
Yes it did. The "embedded transactions" is the new feature.
I think the new part is "allow users to use embedded transactions (i.e. BEGIN, COMMIT/ROLLBACK) within a procedure."
It does, and has since Civ 4 at least.
Get ready for $12 lettuce.
I think they mean surveillance cameras run at an angle that makes automated facial recognition impossible.
A good podcast on the risks of semi-automation: https://99percentinvisible.org/episode/children-of-the-magen...
I think most people here can relate to being an engineer who is held to other people's unrealistic expectations. Problems happen when there is not a critical mass of individuals to push back on those requirements. It's possible that this project is Uber's last ditch effort at existing, in which case there would be enormous pressure on everyone to make self-driving work at any cost. It was a design decision to disable the car's stock automatic braking feature, for example. It's not that they're stupid, it's that they're putting their morals on the shelf in order to get this to work.

At some point you need to have a regulatory body in place that sets standard for safety, otherwise people are going to die.
Seriously? No one suggested it was an imposition of any financial culture - just that mitigation of risk is costly.

However, I can't imagine what sort of ignorance leads one to believe, as it appears, there's no unfairness in distribution of profits or risks in comestible (or pretty much any) supply chain.
If you're into fast cardinality estimation (HyperLogLog) and item counting (Count-min sketch, Bloom filters, hash tables), check out Bounter:

https://github.com/RaRe-Technologies/bounter/

(Pythonic interface on top of highly optimized algorithms, faster than dict but using limited memory, MIT license)
Facebook rewrote Messenger in Reason. Before they had hundreds of bugreports in a year. Afterwards? Less then ten.
Coming soon: Your voice in a UN database
He said that he can "guarantee" Uber engineers gave it careful consideration (or at least more than people in this thread), but in truth he can do nothing of the sort. There are a plethora of examples where engineers and "engineers" didn't give a problem careful consideration and it got people killed. There is no rational basis for guaranteeing this is not one of them.

There is no "guarantee" that uber "engineers"/engineers put more thought into this than "their system is inconvienent, tear it out" or "we don't need their system because ours will be better, tear it out." Nobody can guarantee Uber engineers were not stupendously negligent until the investigation is complete. Anybody who thinks they can guarantee that has an irrational basis for thinking they can provide such a guarantee.
>but still there is no code, no network, no nothing

EOS mainnet launch is June 2nd, 9 days away. There's lots of code: https://github.com/EOSIO/eos

Check this cool demo out: https://eosauthority.com/space/
> The 2nd theme that's mentioned in passing is the Six4Three bikini API dispute as a forensic discovery into how the Cambridge Analytica abuse was deliberately engineered into the platform in 2011 and was approved by Facebook senior management. I think this is the more interesting angle that the Guardian writers should have focused more text on.

Is that intentional aspect of the lawsuit or just a side-effect? It would be interesting if a privacy advocate gained control of a defunct entity with standing to sue Facebook over data-related dispute like this, and used discovery to dig into Facebook's privacy practices.