skysight-inc/HackerNews huggingface dataset:
React won the spa crowd.

Lags behind in server side frameworks adoption over Vue.

React won the enterprise crowd pushing angularjs out.

React hasn't won over the JQuery crowd

If you do primary js it probably has. If you only do some js and other things it probably hasn't yet.
Brilliant! https://news.ycombinator.com/item?id=35103
Unfortunately the relationship between clock readouts and actual health state is tenuous at best, and is really more of a postulate than an established fact.

It is true that Horvath and others have shown that clock deltas (between predicted and chronological age) correlate with all-cause mortality. There has been surprisingly little work on clock deltas and specific disease risk.

But these are correlational or observational studies. What is not known is whether, or how often, an intervention that changes the clock will also change lifespan or healthspan. There are far too many grants and papers that just assume this is true. Usually the argument is something like this: intervention X improves health, intervention X lowers clock age, therefore the clock is a good biomarker of aging.

The classical Horvath clock has something like 350 loci all spread out in the genome, often in regions that have no obvious functional significance.

Imagine the extreme case (which has been the subject of more than one grant proposal): take one of the clock loci 100 kbp from the nearest gene, forcibly alter its methylation state specifically. Will this change clock age? By definition, yes. Will it alter health at all? Very likely not. People seem unaware of the almost certain fact that these loci are not causal in aging, they are readouts of upstream biological states.

Also, there are numerous inconvenient facts, such as the fact that the if you compare groups of the same age, one group with and one without various neurological diseases such as Alzheimer's, the group with neurological disease appear to be younger by the clock.

I would beware of this area, there is so much hype around it and claims have far outstripped evidence by this point.
0 degrees fahrenheit =
-17.778 degrees celsius
Judging by your politics the other party will do the same citing Russian interference, you will always be slaves to your two party system abs continue fighting with each other.
Not NYC. Long Island. Tropical Storm went through on Tuesday.

PSEG spammed us with all these boasts about how they were prepared.

They weren't.
Gogo is trying to sell its commercial in-flight internet business
Saying an argument is false because it's a meme isn't a rational way to argue against a thought. You argue against things with facts and evidence. It's more disrespectful of the opposition if that's the strongest remark the opposition can make.

I suppose the great-grandparent is more an 'appeal to emotion' fallacy rather than ad hominem.
The quiet revolution: China's millennial backlash
Ah makes sense... thanks for the clarification!
C:\Documents and Settings\Lammy\
Correct. Adiabatic cooling due to depressurization causes temporary condensation. Though arguably it's more of a "back" than a "front", since it's in the wake of the pressurization front.
“Bon Voyage” and other outtakes
What is the point of this comment?

You've effectively spend a few paragraphs adding nothing of value to the conversation.

You've effectively restated the grandparent's points, but tried to do so in an adversarial manner.
I get your point but I went down a CNW rabbit hole and I’ve got to tell you, there isn’t a whole lot of original reporting being done. There are no sources and in many cases (6ix9ine is a great example), the content seems to be a rewrite of his Wikipedia page. In other cases, entire sentences are reprinted verbatim from Wikipedia. The net worth calculation is basically reported earnings less relevant taxes. For major celebrities, they seem to rely on publications like Forbes and Business Insider coverage.
It won't simulate the block storage data loss, which is a key part of testing a database, filesystem or similar for robustness to those events.

Even killing a VM instantaneously on a host only simulates the loss of the guest OS's cache. The host OS still has its cache.

And even killing the host OS only simulates loss of the host OS's cache. The drives still have their caches powered, so might behave differently on power loss than host OS crash.

And killing a drive while the host keeps running is different again.

(And in terms of high-level software-observable data effects, abruptly killing power to a drive is not the same as slowly lowering the voltage or limiting the current to the drive, or seeing corrupt data on the I/O bus while the host system loses power (which is never instant), or... you can go quite deep with this.)

In the networked storage environment at AWS, who knows what events are possible to observe on EBS in the event of a system-level failure such as power loss in a data centre.

For example, EBS is a distributed system with replication, so if it has an implementation error that only affects certain untested, complex failure modes, it might lose recent writes in flight (as expected), but then some time later they might come back, or some of them might come back if it's sharded. Both are bad if software using it has already started state recovery after an outage. Distributed systems often have surprising incorrect recovery patterns, because it's a complex and subtle problem; that's why the Jepsen tests keep finding bugs in databases people have been using for years.

The observable events can differ depending on whether it's VM hosts, switches, block storage units, drives failing and in what ways.

For Linux guests we have abstracted away most differences we care about under fsync() or various combinations of O_DIRECT and virtual HDD cache disabling, or relying on known features of filesystems, but there's no easy way to be certain those abstractions actually provide the expected semantics on different kinds of system failure. Stress testing higher layers in the virtualization stack would go some way to verifying that they do in practice, not just in theory.
The F14 actually had a neat processor, with an architecture which remained classified for a long time (arguably far too long at the end, but it was plainly justified at the beginning)

It was very old so, yes, I'm sure it had plenty of limitation though.
A little googling about the article's author:

"Dr. Tilak K. Doshi is a Senior Research Fellow at the King Abdullah Petroleum Studies and Research Center in Riyadh, Saudi Arabia. Prior to taking this position, Dr. Doshi was Principal and Head of the Energy Economics Department in the Energy Studies Institute of the National University of Singapore. Dr. Doshi is an industry expert with over 15 years of international work experience in leading oil and gas companies."

...

"Prior to joining DMCC, he worked as Specialist for Saudi Aramco in Dhahran, Saudi Arabia in the crude oil sales and marketing and corporate planning departments. "

http://education.mei.edu/profile/tilak-k-doshi

So, about precisely the profile a person who has an interest in promoting the oil the gas industry and talking down its competition.

EDIT: Choice quotes here https://asiatimes.com/2017/10/dinner-parties-climate-change-...

"Belief in global warming has itself become a quasi-religion, and one is faced with the obvious choice between enlightened affirmation or “anti-science” denial."
>...That’s intentionally deceptive.

Part of the Hacker News guidelines is to assume good faith.

As the IPCC says:

>..There is no scientific argument for selecting 100 years compared with other choices (Fuglestvedt et al., 2003; Shine, 2009). The choice of time horizon is a value judgement since it depends on the relative weight assigned to effects at different times.

I chose 100 years since you seemed to imply that since methane was "front loaded" then "...there are significant benefits from eventually moving to something else, but little long term advantage due to methane from doing so sooner."

Trying to ignore the problems of methane in the atmosphere is not helpful. As the Think Progress article says

>...The IPCC reports that, over a 20-year time frame, methane has a global warming potential of 86 compared to CO2, up from its previous estimate of 72. Given that we are approaching real, irreversible tipping points in the climate system, climate studies should, at the very least, include analyses that use this 20-year time horizon.

>...If we are to avoid catastrophic warming, our natural gas consumption has to peak sometime in the next 10 to 15 years, according to studies by both the Center for American Progress and the Union of Concerned Scientists.
I take a screenshot of the QR codes and save the images directly into my password manager and a private git repo.

> If you are not storing them in a secure manner, then using 2FA is not really an additional layer of security

My worry is not someone hacking into password manager but rather someone doing a driveby hacking using old/leaked passwords. Therefore I optimise for convenience.
Why was it a problem with the Pi and not a laptop?
Targeted Web Traffic
Things to Know About Shakuntala Devi
> Meltdown was independently discovered and reported by three teams:

Jann Horn (Google Project Zero),
Werner Haas, Thomas Prescher (Cyberus Technology),
Daniel Gruss, Moritz Lipp, Stefan Mangard, Michael Schwarz (Graz University of Technology)

Spectre was independently discovered and reported by two people:

Jann Horn (Google Project Zero) and
Paul Kocher in collaboration with, in alphabetical order, Daniel Genkin (University of Pennsylvania and University of Maryland), Mike Hamburg (Rambus), Moritz Lipp (Graz University of Technology), and Yuval Yarom (University of Adelaide and Data61)

https://meltdownattack.com/#faq-systems-meltdown
Do people in your life like you?
On the other hand it's absolutely pathetic that C still doesn't have actual arrays. To head off comments, no syntactic sugar on top of pointers doesn't count at all. So don't even try to make that argument.
I'm starting to wondering how accurate this article is...

"High explosives produce shock waves; low explosives, like ammonium nitrate, produce pressure waves, which have a bit of slope to their shape, a period of time over which the pressure increases more gradually."

But a shock wave is an area of high pressure, so it's a "pressure wave" too.

And at least according to this Los Alamos article [1], "low explosives" versus "high explosives" is basically the difference between deflagration (rapid burning, e.g. black powder) versus detonation (chemical conversion happens faster than the speed of sound through the material, e.g. TNT).

By that definition, ammonium nitrate, is a high explosive. That's why they use it as the main blasting agent in mining operations.

[1]https://www.lanl.gov/museum/news/newsletter/2017/2017-04/hig...
Semi-related: "Arrival" was a terrific movie adaptation of "Story of Your Life", an even better short story by Ted Chiang, featuring attempts at communication with advanced alien intelligence. Highest recommendation for both.
Current employment law really isn't well suited for cases where someone can be an "employee" of 4 or 5 companies at a time, and stop and start on a whim as they see fit. I mean, just look at unemployment insurance. When the nature of the job is essentially a bid out to people willing to do the work, what does it mean for someone to be unemployed in the first place if there is just less work to go around? Flexibility DOES have a lot to do with it: I'm fine with the company not guaranteeing me a set number of hours per week if I can just choose to not work a particular week if that's what I want.

I agree with some other posters, I think a new categorization for "gig" workers is necessary, as I think a lot of your other points (e.g. paying workers comp) make sense.
Thanks!

Quick summary:

Immer is an incredibly useful immutable update library, created by Michel Weststrate (author of MobX).

It exports a single function `produce(originalState, updateCallback)`. The callback receives a `draftState` value that _looks_ like your original state, but has been wrapped in an ES6 Proxy. You can then "mutate" the draft all you want. Internally, Immer tracks all the mutations, and the final result is a safely immutably-updated value.

It drastically simplifies immutable update logic - no more nested spread operators!

See https://immerjs.github.io/immer/docs/introduction and https://redux.js.org/recipes/structuring-reducers/immutable-... .

Redux Toolkit comes with Immer built into our `createReducer` and `createSlice` APIs automatically.
The risks were/are in the filings.

https://d18rn0p25nwr6d.cloudfront.net/CIK-0001543151/f0dcd9a...

Page 34 (by PDF count).
I tried that two months ago and the bank didn't support it, unless I was holder of both accounts.
Morrison Shelters
I'm not sure your point here. The Amendments are generally included when someone refers to the Constitution. Several of the Amendments are directly related to protecting the right to vote.
All web links go through some form of interception.

Deep linking allows web links registered with apps can be monitored or intercepted by the apps.

(wondering why amazon links open up in the amazon app?)

Links pasted into messages will be intercepted and a link preview is loaded.

You can kind of prevent this is by putting the link in angle brackets like <https://example.com>
Astrophysicists observe long-theorized quantum phenomena
@BeatLeJuce You don't have to go very far online to find the answers to you question. James Corbett has amassed a formidable array of facts and history, for example.
This isn't even remotely what the post is about. It's about how the C standard is resistant even to things like warnings for provably bad code in the name of backwards compatibility ("more warnings for (maybe) working code = bad"). Did you even read the post?
Uber has not ever been more efficient than the services it replaced. Better in many ways, definitely for riders and arguably for some drivers, but not efficient. Uber has simply been shoveling tens of billions of dollars in funny money into the maw of their attempt to corner a market, which has never worked.

This write-up from today sums up some of the story so far. https://www.nakedcapitalism.com/2020/08/hubert-horan-can-ube...
All these worlds are yours except Ceres. Use them together. Use them in peace.
The question isn't whether they're historically related, but whether they are sufficiently similar as to be comparative -- the american hotdog and the german sausage may have shared elements, and presumably shared roots, and I wouldn't doubt that the hotdog is a modified sausage -- but they are so distinctly different in taste, texture, quality, usecase and goals, that it doesn't really make sense to say that the german sausage is a better hotdog, or vice versa. Even if the hotdog was still called a sausage. (and sticking a full sausage on a hotdog bun? A criminal act if I ever saw one)

If it doesn't look like a duck, and it doesn't quack like a duck, then it ain't a duck. Even if you called it a duck the last 500 years, it still ain't a duck -- at least, it's not a duck like my duck's a duck.
I have been through various wiki migrations and so on (and on, and painfully on). And yes, there's a lot of rot, and unfleshed skeletons, and potemkin villages of Sharepoint subsites, and so forth. And there's no structure or consistency because everything is self-service.

The term is outdated but the need is not: to tame this kind of thing, you need a webmaster, a person who has been granted the authority to create structure, to move things, to say "This belongs somewhere else" or "If you don't update this I am going to take it away." This is a person who has a responsibility to run a link checker and to see when the last time a page was accessed.

It's a real need, but we just forgot about it during the fragmentation of all things web-related.
>A Gravitational Redshift Measurement of the White Dwarf Mass-Radius Relation

https://arxiv.org/abs/2007.14517
Faster is normally not all that important: it's much better to save fuel and send more stuff than to get there a few months earlier. Fuel costs vary roughly with delta-V, the total amount you have to accelerate or decelerate your spaceship. Because of the tyranny of the rocket equation, they aren't linearly proportionate to delta-V, but in general, if it takes more delta-V it's going to be harder and more expensive to send a spaceship there.

Here's a map of the solar system by delta-V [0]. Good news is it's roughly equally difficult to get to Ceres as to get to Mars! It's further away, but it's smaller which means less decelerating when you get there.

For your actual question...you can get faster routes with more fuel. We're pretty close to the limits of how big a rocket we know how to build and still get it to Mars (or Ceres) with a 2-ton payload (enough for a lander, a rover and a little fuel) using the most fuel-efficient route. If you want to get there faster, which might be important for manned missions, you need a smaller payload or a bigger rocket. Or the most likely solution - you launch lots of rockets and join up the payloads into a bigger spaceship in Earth orbit. If Elon's goal was to make a one-way trip to Ceres as fast as possible, he'd be doing mostly the same as he is now - focusing on being able to build lots of rockets and launch them cheaply.

[0] https://imgur.com/WGOy3qT
This trick generally works, but is not guaranteed to work by DOS API. COM binary gets 4k paragraph allocation and nothing more, the fact that this allocation essentially always is at the bottom edge of free conventional memory is not even an implementation detail, it is consequence of everybody trying to be frugal with their memory allocations. ie. if there was TSR that allocates and then frees 64k region, you will get exactly this region and this trick will break and you will overwrite who knows what.
drunk by a human or drunk at all?
I'd suspect that not all water has been drunk at all, but lets cover the human part.

Lets say the average human drinks 3 liters per day and lives 80 years (3 * 365 * 80 ) = 87,600 liters per human.

there have been about 100 billion humans so 100 b * 87600 =8,760,000,000,000,000 liters have been drunk.

there are about this many liters in Earths 5 oceans (source google search):
1,400,000,000,000,000,000,000

Assuming no one has ever drank the same amount of water before,
8,760,000,000,000,000 <
1,400,000,000,000,000,000,000

It sounds fairly certain that not all water has been drunk by a human, even if my math is way off
So what? That's how semantic versioning works, it wouldn't be a major point release without the breaking changes.
> I've had multiple APC UPS literally catch on fire. It's always the tower models with the real time voltage regulators that catch on fire.

I wonder how that is even possible in the first place.
> if an EV is driven 50,000 miles over its lifetime

Small nit-pick, but this made my eyes pop out of my skull. My first car had over 200k miles on it when I _started_ driving it another 75k. It seems ridiculous to use 50k in these calculations.

> Where the electricity comes from isn't a function of the car; that is just stupid.

I don't think it's fair to dismiss this part of the argument. In the US, the vast majority of our electricity is generated with fossil fuels. It's great that the car maker wishes this wasn't the case, but the reality is absolutely relevant to the discussion IMHO.
That is not at all how that works. How do you reconcile this altruism with Britain's continued trade with and reliance on goods from the Americas and their continued use of slave labour? How is it that so many Westerners keep making these strangely naïve and surface-level readings of history and politics?

You might find this interesting: https://origins.osu.edu/review/after-abolition-britain-and-s...
Why is that weird? If the rules vary by jurisdiction, I expect compliance to follow suit.

I suspect that you're implying some sort of objective universal metaphysical state of "being an employee" or "being a contractor", but that's pretty clearly false.
I thought Wikimedia has a version history. Couldn't you just write a "blank" version of every article that hasn't been accessed in over a set time period.

And if someone gets there and wants the old version back, they can.
I'm pretty sure some of the "ohmygod you're suppressing voters!" articles are about states with free IDs. (Or extremely cheap - for instance in Michigan an ID is $10)
> Waiving the fees is sufficient to make the ID ubiquitous immediately,

No, it's not. Many people have difficulty finding the documents that will get them an ID. There are plenty of people working illegal jobs who are trying to figure out how to get a birth certificate, social security card or prove residence. This was even more common when more people were born at home.

I had a hard time getting ID when I was a teenager, and I needed it for migrant agricultural labor (to work on a legal crew doing corn detasseling.) Luckily, I got arrested a week before we were scheduled to leave, and I was able to con the DMV into issuing an ID based on my jail papers (although the clerk at the jail wrote down whatever I told them.)

The reason requiring ID is a problem is because there's no widespread voter fraud, and declaring that you're someone else is very difficult without that person agreeing not to go vote. It's a requirement whose administration cost dwarfs by orders of magnitude any benefit. The intention is to exclude people who have ID problems, not the people who don't believe it's possible that anyone could possibly have ID problems.

Also, just let felons vote. Put voting booths in prisons. If your population is so prisoner-heavy that they make a significant difference in the outcome, your society is broken.
> You've effectively spend a few paragraphs adding nothing of value to the conversation.

You might want to check what you consider "adversarial" when it comes to a discussion forum.

The issue is that the comment I responded to seems to be under the false notion that workers (or employers, for that matter) get to "choose" how they want to be classified, and that's what this debate is about. My point is that, when it comes to employment law, a worker or employer's preference about how they are classified does not factor in at all about how the law classifies the job.
A combination of routing the power elsewhere in the grid when possible and banks of gigantic (shipping container sized) dummy loads. As other people have noted, you don't need to dissipate the full amount of power all at once, you test the generators individually.

http://resistive-loadbank.sell.everychina.com/p-109417602-35... is the first example I pulled up, and there are bigger ones.
Google has pushed the patch for this back to October. I wonder what will happen to downstream vendors (Samsung, CopperheadOS)?
The term "dependent contractor" is sometimes used for this idea of a third category. Whether it actually provides workers with the benefits and protections that employees with similar working arrangements are entitled to remains to be seen.
But for Uber being allowed to seize the market with their ultra low prices, which are only possible because they class their labor as contractors, there would be companies more like Uber than like taxis but that treat their employees like employees.

The problem with taxis was the medallion system and other crazy regulations.

There is a middle ground. No medallions or other protectionist measures, but you have to treat your employees like employees.
It is not. In Texas, you cannot purchase alcohol with a school ID.
I use `org-journal` to have timestamped daily notes. If I think it's going to take more than a couple of minutes, I start a new .org and add bullet points to it (currently just dumping these in some canonical, indexed location, haven't felt the need for something fancier like org-roam yet)
Diagnosis: TDS
Maybe help me understand how having a phone means you're present in a conversation? There have been class action lawsuits filed by uber and lyft drivers.