skysight-inc/HackerNews huggingface dataset:
I'm talking about the newer process they're developing at the gigafactory. But you're right that lithium is so cheap at the moment (getting it from salty brines) that you don't really need to recycle it. The other metals, sure. But push comes to shove, you could pull it from ocean water. Won't ever be economically competitive with brines, but it's also not too expensive if that were the only option.
The official unemployment rate includes only those who are "actively seeking" employment, by specific measures.

It does not include those who have given up looking for work or don't consider the available work sufficiently rewarding. A sufficiently strong recovery brings more of those to find work.

Labor force participation may be a better measure. https://data.bls.gov/pdq/SurveyOutputServlet
Daimler held a significant amount of Tesla stock for this reason, but dropped it when they discovered that there's no magic behind the smoke and mirrors.
Once salaries start rising I'll believe you.
Drilling in the frozen north and releasing an ancient monster is the subject of the first episode of the revamped Mystery Science Theater on Netflix.
Oh man, everyone's talking about MobX in here, and I've never really looked at it. This looks pretty awesome. I don't particularly enjoy using Redux either, so I think I might try this out on my next project.

I'm looking for some replacement libraries from the Redux ecosystem. I've already found https://github.com/pinqy520/mobx-persist, which looks pretty good.

What do you use instead of redux-saga or redux-observable? E.g. for async stuff like ajax calls, or listening for events and emitting new events?

Concrete example: You want to listen to a variety of events in your app, and send analytics. Some of your analytics events require looking up parts of the state and doing some processing. This is really easy to do in redux-saga, but how would you do this with MobX? Or would you use something else for this?

EDIT: Ah, I think I was looking for "autorun": https://mobx.js.org/refguide/autorun.html
I meant steak, sorry for typo.
What has been the most useful application of ETH for you?
You can go back and forth about which coding environment is best for kids but it is really great how many options there are now. I first encountered programming on the trash-80 in the 5th grade. We had a typing program, text games and Logo and saved things to cassette tape. Back then, Logo was a triangular turtle on a monochrome screen. We have come a long way in ~30 years. Still I remember loving it. Logo had a huge impact on my life.

More recently, I started helping kids with their programming projects at my local library's coder dojo using Scratch, JavaScript, Python and other languages. It's a rewarding and fun way to give back to your community. I highly recommend trying it out.
"A-lalla-lalla-rumba-kamanda-lindor-burúmë"

http://folk.uib.no/hnohf/entish.htm
Routinely spent $40 on a taxi from Boston (Logan) Airport to Cambridge (Central Square) as a student. Couldn't really afford it but redeyes often leave one lacking for options. To your point of regulation and pricing, I'd happily accept less "professionalism" for a sensible discount—say $10-15 rides.
More than there will be of the 89, even given a 100x failure rate comparatively.
What do you mean by (?NSAID) after tylenol?
> a true date-of-Easter complication is probably the single most difficult complication in horology

Funny story. I was making the "final" commit before shipping a desktop application, and I wanted to make an Easter egg. But what should it be? It should be Easter-related, I supposed. I made a pastel color theme for the main screen, that should appear only on Easter. This product is used in DoD, and I doubted that anyone would ever be using it on a Sunday.

The product had a design flaw, a kind of time bomb. I was a greenhorn working on it when it first shipped in 1994, and I thought nothing of the fact that its rate table was arranged horizontally, like so:

id 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000
1 4.49 4.59 4.79 4.99 5.16 5.26 5.68 5.78 5.99 6.44
2 ... etc

Despite being a Navy budget forecaster by trade, the Captain who created the program lacked the hubris to worry about needing rates for the next millennium. This set of dates was hardcoded all over the the codebase. The Captain, a poor typist, kept resetting the bomb by adding more years.

Fast forward to 2012. The product has been acquired, and I was brought in to port it for 64-bit machines. And the only task remaining—revision #1400—was to compute the date of Easter.

It took me about 2 minutes to conclude that this wasn't going to happen (although I didn't know it was that hard). So although it lacks the elegance that you'd like in your Easter egg, this one hardcodes the dates of Easter Sunday... through 2020. I mean, it's going to be on the web by then, right?

Yeah, it's still shipping.

http://www.budgetbuilder.com/
And John Carpenter's The Thing.
Because in practice, I'm trying to reason about the consequences of submitting a given transaction. A transaction can invoke many smart contracts in addition to mine. It's not enough for my code to be correct; every piece of code the transaction causes to run has to be correct as well.
I've found that a goal combined with play seems to be effective. People like learning if it is a way to build something they want to build. So maybe try finding something that the child wants to build and then get to design through that?
https://www.npmjs.com/package/tiny-state-manager

https://www.npmjs.com/package/tiny-state-manager

Maybe not for prod, but certainly great for simple uses and a quick start :)
Did you read the article?

> Broader measures of unemployment tell the same story. The so-called U-6 rate, which captures people who are working part-time but want a full-time job, and those who would like a job but have given up looking out of frustration, is also back down to its level before the last recession. It fell to 8.6 percent in April from 8.9 percent, and the last time it was lower was November 2007.
I've read that cold operating rooms are cold for the comfort of the surgeons, but the cold leads to more infections and slower recoveries:
http://www.nytimes.com/1997/04/16/us/surgery-s-chill-can-be-...

Here's a more recent article that cites some papers:
https://www.verywell.com/are-operating-rooms-cold-to-prevent...
I don't understand this, myself. Why isn't this calculation implemented as a mechanical state machine? It's impossible to implement a 5,700,000-year cycle with an individual program wheel, but three or four smaller, simpler ones should be able to do the job.

Hard to see why this is considered a difficult problem at this point, 2000+ years after the Antikythera Mechanism.
U don't have to believe anyone.

But if u believe in math, then even with this U-6 metric, it is back to 2007 level. Meaning this U-6 metric is not really an indicator diverging from the official claim either.
Interesting project. I wonder what is the relation to approaches that allow explicit composition of enumerators, such as [1]? It seems that this approach could provide a nice interface for generators that need to be constructed explicitly. (This would be interesting to explore. By the way, I am the developer of the SciFe enumerator framework.)

[1] https://github.com/kaptoxic/SciFe
I absolutely love Scratch. I think its incredible how it introduces children to concepts and patterns that are very difficult for even intermediate programmers.
Things like actors and message passing, or thinking in ways that are compatible with an event-loop type of environment. Its great!
Because heavy lift aircraft are perfect when you need to get something bulky somewhere else, fast.

When it's multiple somethings and it's not time critical (days or weeks rather than hours), it's economically far more sensible to ship by sea.

Sure, a service centre could really need half a dozen flights of engines, but given how well planned aircraft maintenance is, it would certainly be a turn up for the books to suddenly need such a number so urgently.
What does being employeed matter? Having a liveable salary and average lifestyle for all is more important.
blood sugar is mostly regulated by hormones: glucagon and insulin. Not really by what you just ate. Hence why you can go days without eating and still have a normal blood sugar. Eating causes your pancreatic beta cells to release insulin (in response to elevations in blood glucose). Diabetics have spikes in their blood sugar right after they eat because they have impaired insulin sensitivity and so their tissues (muscles mainly) don't take up the sugar in the blood (a process mediated by insulin receptors).
I still don't understand that phrase. Help?
> I once started going through the Rust library packages and listed uses of "unsafe". Try doing that.

That's ... exactly what I did? Talk about denial. I went through the libraries in my .cargo folder (which filters for libraries that actually get used, not just random libraries out there). I linked you to that audit in the comment.

Yes, libstd contains a lot more unsafe, but that's kind of the raison d'etre of libstd -- to contain OS-abstractions and very common internally-unsafe abstractions. It's better to have one unsafe implementation of Vec (in a library with a lot of eyeballs on it) than to have ten that the ecosystem relies on.

> which then turns up in the JSON decoder at

rustc-serialize is deprecated. It was deprecated before 1.0, and went into maintenance mode. It was still kinda-maintained because of the difficulty of using serde on stable, but now it's basically going to be full maintenance mode.

Also, that line is trivially safe to execute on untrusted input; `char` is utf8. Yes, a comment would be nice, but like I said, maintenance mode.

It is possible to do what that function does in safe Rust today, but it needs an API that probably didn't exist ~two years ago when that library was actually relevant. Fixing.

> The most downloaded Rust crate is "libc". What could possibly go wrong there? Was it really a good idea to import unsafe "strcpy" into Rust?

libc is just bindings (to everything in libc). You still need to use unsafe to call those functions (everything in `extern "C"` is unsafe to call even if not marked explicitly as such). This is not a valid example.

> A very small number of packages need unsafe code for those functions, and those should be tightly controlled.

which is pretty true already? The "partially initialized arrays" problem is generally handled by just using Vec. Yes, you need unsafe to write vec, but then you can just build things out of it.

Backlinks turn up rarely -- if perf isn't involved folks just use Weak safely, but otherwise people use petgraph or something.

> I could give many more examples.

Go ahead then. You literally never have, and none of these examples are valid "unnecessary unsafe" for reasons I gave above. I did substantiate with an audit. I'm genuinely interested in finding places where we have too much unsafe code, because I'd like to avoid depending on those crates and/or fix them.

> Most of these problems are fixable. They're not inherent in Rust. Fixing them is important to Rust's credibility.

Sure. And folks are always looking to improve this. But this doesn't mean that there's some widespread problem of unsafe being used too much in Rust. I'm not denying that this shouldn't be improved, I'm denying your allegations that `"unsafe" turns up way too often`.
That's much easier said than done. If formal methods were practical, we'd be using them already everywhere else.
Is a part of that because women weren't expected to have jobs in the 50s, though?
It will be interesting to see what modding will look like in five years. I imagine total conversion mods will no longer be a thing for starters given how easily accessible development tools are now.

With services like patreon becoming really popular the mod authors who are good I imagine will be able to self sustain to a degree finally.
The 1950s or 1960s is anything but a reasonable comparison point.

The sole reason those decades are plumped up so dramatically, is that the US took over 55% of all global manufacturing temporarily, due to the rest of the planet's dominate economies having been either destroyed or substantially set-back in WW2. It was an almost perfect storm of young men coming home and others coming of age from the post WW2 era baby boom (1960s, early 70s), and the US inheriting manufacturing dominance which was ideal for employing blue-collar men.
Moment.js is about 80x slower than Date()
In parts of Africa, people with albinism are killed or sold by traffickers
Labor force participation doesn't take into account demographic changes so it's almost categorically worse than U3. Look at U6 for something that takes into account discouraged and part time workers.
Wrong benchmark. I'm talking about k-nucleotide, which tests hashmaps.

http://benchmarksgame.alioth.debian.org/u64q/knucleotide.htm...

(And I was only really talking of the comparison of rust v rust, not rust v c, i.e. that ordermap is faster than the built in hashmap despite not using unsafe)
What I never get is who is making money off these?

Surely Google doesn't want to risk damage to it's billing dollar brand.

So it's fake websites selling fake ads with click robots to make money from Google? Is this really a hard to solve problem?
> I really love seeing articles like this come out about Rust.

Yeah, me as well. It's a perfect marriage of academic know how and pragmatism. Very exciting year for Rust.
That makes sense....
Depends on how personally is personally.

I've seen a lot of places like McDonalds replace most of their cashiers with self-order stands over the last few years.

I've seen parking app and terminals replace parking fee collectors over the last decade.

Road repair teams have shrunk over the last couple of decades - it's much less crowd of people with tools and more of a few big combines and a couple of dudes.

Just the ones that come to mind.
Labor force participation has many other problems - retirees being a huge one. There are disputes on who to include as actively looking for work and how to measure the underemployment, but labor force participation is not the answer.
And "At the Mountains of Madness" by H. P. Lovecraft, more or less. Although at the other pole.
Each person is pushed into a tube from the top whilst the current resident is pushed out the bottom. Each tube is made of reinforced kevlar and whatever else you can imagine. Each person is naked and is allowed no carryons of any kind. This of course will also increase profits as you can fit more tubes than seats.
Pretty much a dupe of https://news.ycombinator.com/item?id=14277005.
the guy said he would like to be able to afford steak to take home more often, and I quote 'but nope, I guess its beans again this week too"

sorry I wrote 'stake' twice. it may be keyboard on my phone messing with me
I don't think it's worth making changes like that to satisfy random misconceptions unless they are widespread.

There are good reasons for having an unsafe-code flag on a crate. This is not one of those.

This has been discussed in the past and the main concern IIRC is that this may make people afraid to use crates that contain unsafe code even if it is well audited. There's a finer balance you want to strike here.
It is an unfortunate name. I don't know why, given how inclusive the Rust community usually is and how eager they were to remove master/slave terminology, that they would choose to announce this effort under the banner of Nazi war tactics.
Same w/ German. Halb Neun (Half Nine) is 8:30. Half to nine.
I'd be interested in how many stay-at-home dads are in that drop.
This ignores the deterrence factor
Humans are not very good at telling time and since their observations are subjective we can dismiss such experiments as anecdotal.
> It may help you to ponder that in the 1980s, a lot of people were extremely confident human civilization was doomed, doomed, doomed by certainly no later than 2000, and even setting the date that late was terribly optimistic.

I imagine a lot of people thought things were going to be fine too as the Roman Empire collapsed. Or at the start of the Dark Ages. Or when the Black Plague began. Or when the 1929 market crash that kicked off the Great Depression. Or on the eve of both of the World Wars.

The point being: yes, most of the time, humanity muddles its way through its crises successfully. Until one day, it doesn't...
I believe they figured out that there is some truth to the idea that cold=sick at least for influenza. It doesn't live long while airborne but in a cold environment it can survive a bit longer, meaning in a warm room if someone sneezes you are less likely to be exposed than in a cold one.
Srsly: https://fred.stlouisfed.org/series/LNS12300002

Men employment rate is down from 80% to 65%, but women's employment rate is up from 30% to 55% from the 50's to now. In total the average employment rate for everyone has increased over 50 years from 55% to 60% in the US.

And there's no reason to think that we need a larger labor force than we had in the 50's - the opposite in fact.
hahaha. thanks.
Probably to convince manager types to adopt it? NoSQL is a hot marketing word among people who don't actually write code. Just go to any conference about "big data" and listen ;)

It's like the word "XML" 10 years ago. Just say some BS about how you're adopting a new XML-based infrastructure for motivating a novel, globally-connected society with Web 2.0 standards compliance, and the managers will let you do what you really want to do.
This looks like a simple & potentially enlightening question, but, its more complicated than it appears & examples may only be more confusing:)

Companies (tech & other) are sued literally all the time under RICO (which is now over 40 years old), though mostly as civil rather than criminal offenses. Success rates vary. Often there are better ways than RICO. And, also, most cases never make it to court.

Basically, prosecutors choose the charges they seek to prosecute based on their judgement of the likelihood of conviction; RICO can effectively multiply the number of charges...which some judges are less keen on. There are many factors at play with RICO, but they won't clarify anything, so I'll leave it there.

It is certainly not clear that the DoJ will even prosecute Uber under RICO. Its a possibility, but perhaps not the most likely approach, for a variety of reasons. That said, its far from impossible. And, some USAs use RICO more than others (eg Preet Bharara).

Long story short: criminal investigations & charges are the issue, more than whether they are charged under RICO. Being criminal investigated is rare in most businesses (less so on Wall St? Idk, speculating) and being prosecuted, even rarer.

Hope this helps.
Does it though? I understand the value that Electron brings, but at the same time, that doesn't make it immune to criticism. 100MB+ for every instance of a hello world application is stupid. It's because people thought it was stupid that the linked article and the software for it was written, and why it was posted on HN, and why it was upvoted.

You might not like that people have criticisms of Electron, but that doesn't mean there's not room for improvement, and certainly just jumping at this guys name rather than his argument makes your comment less valuable than his.
I'm looking here:

http://www.macrotrends.net/1316/us-national-unemployment-rate

I find it almost impossibly odd that "1 year after the decade" is sufficient to imply a recession. By that chart, 2021 is going to blow.
Clippy has some checks for naming convention beyond what rustc and rustfmt does. Not nearly as much as https://github.com/brson/rust-api-guidelines, but the wrong_self_convention check helped me make sense of the as/to/into conventions.

https://github.com/Manishearth/rust-clippy
So if we are saying this isn't that great of news, what should I make of some European countries?
Juncker – English is losing importance
Not all microwave dinners are beer-battered steak fries with gravy and nacho cheese. There are some that have reasonably healthy ingredients, like lean meat and actual vegetables. If you want, you can go all the way and get some that have whole grains, kale, quinoa, etc. in them.
It sounds like you're running a hobby Linux distribution. I have nothing against that, but please don't make it seem like somehow it is superior just because it is different. I used to make Linux distributions that could fit on a floppy disk, but I wouldn't brag about how fantastically small it is and how that obviously runs much better.

If you are compiling source code by hand, you are circumventing the entire distribution. Do not expect it to work. Just because it may work a lot of the time for you does not mean you should expect it to. If updating a shared library broke something, it's because you didn't know what you were doing. This does not mean shared libraries are bad. In fact, a great feature of shared libraries is the ability to update thousands of applications by simply changing one object file. LD_PRELOAD and many other features are incredibly handy, and don't work with statically compiled apps.

Yes, I have run into dependency incompatibility bugs. It happens when expected behavior in library code changes. If an application was not written expecting that behavior, then when it interacts with another application, it may have a conflict. The common places it will crop up are IPC, protocol, and file format changes, but also locking, support for optional functions, infrequently used features, etc. It can also happen from updating software's configuration in a way that is incompatible with some older version of some software that was using it, even though some other software supports the newer functionality. If you were around during the Linux desktop wars this was common. It happens less often with distributed applications since they mostly use APIs now, but some APIs suck balls and don't have versioning, and people will change the functionality of some part of the API that old code was depending on somewhere.

Copy an application from 5 years ago into a new system, and copy all the shared libraries into the new system too, and it should run, just like a static binary would run. And it will then immediately die, because all the other dependencies that don't have anything to do with linking weren't there, like kernel feature or modules changes, missing or changed non-library files, protocol changes, missing/incompatible daemons, abandoned deps, security paradigm shifts, etc etc.

Honestly, tracking and updating multiple copies of software with different dependencies is not difficult. We were doing that a decade ago at scale (tens of thousands of servers, thousands of individual software packages). People just don't like dealing with reality. So instead of dealing with the fact that they are doing complex things, they pick up their mess and throw it into a spare room. Look, the living room is clean now! Let's hope nobody looks in the other room.
Probably more interesting is that the USPSTF recently added a recomendation for aspirin use to prevent colorectal cancer in certain populations[1]. There is increasing levels of evidence about this, though it is by no means certain.[2]

[1] https://www.uspreventiveservicestaskforce.org/Page/Document/...
[2] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3354696/
How many American atheists are there really?
This sounds more like the "department of imagined threats" justifying its existence, not actual security.

Even if there is ANY possible risk, what was their analysis? The odds of this are probably lower than being struck by lightning.

The only new things I want to hear out of the TSA each week are: which rules have now been REMOVED, and how many fewer minutes security lines are taking on average.
We'll have to agree to disagree.