skysight-inc/HackerNews huggingface dataset:
The writeup mentioned that (await future)?; is undesirable because it disrupts the logical flow.

Could await be implemented as a prefix, with an additional macro?

awaits!(foo()) that expands to (await foo())
It is likely that the association of red-meat consumption with colon cancer is explained either by an inability of epidemiology to detect such a small risk or by combinations of other factors..

Whoah.
Does anyone know of a way to obtain an official listing of participants in nuclear tests? My father had described in detail being taken out to one of the Nevada tests sometime in the '50s when he was in USMC. He passed away from cancer in the 1980's. I reckon with some cross checking of muster rolls and tests I should be able to piece it together.
The real cancer is SV companies growing to an enormous scale without ever figuring out how to get people to pay for it. Once the price ceiling is $0, there is no other way to monetize except by destroying the experience with increasingly intrusive advertising.
almost all iOS devices and the majority of Android devices DPI is > 100%.

Almost all Macbooks DPI is > 100%.

Majority of the new mid-high end windows laptop DPI > 100%.

I don't think that matters developing web apps. Unless you are confusing with Ctrl/CMD + Plus font size increase.
To be even more clear, a steam explosion cannot by any stretch of the imagination "level" a city fully two hours away. And the phrase "equivalent of a 5 megaton explosion" has no possible interpretation that squares with reality. The idea of a megaton-sized steam explosion is ludicrous, so I assume he means to imply some connection to radioactive fallout - but the amount of fallout isn't really correlated with the strength of the explosion. In fact, early fission bombs were relatively dirty while later thermonuclear bombs were relatively clean. The largest nuclear explosion ever produced was actually remarkably clean due to its unique design. So what is Moxie even talking about? It borders on incoherent, and I think you're being far too charitable.

By the way, the three men who faced "almost certain death" were certainly heroic but weren't in nearly as much danger as he plays up. All three men survived and lived for decades afterward.
How is the effect different? It's a cost that the private company should be paying, but is not.

EDIT - if your comment is pointing out that these things are techincaly different words/phrases, then ok. However, to me, that doesn't make for good discussion: talking about the effects and results, and not fighting about term meanings in the trenches, leads to points of productive conversation.
The structure of the stress-induced photosystem I–IsiA antenna supercomplex
No, the vulnerability is within the API for `docker cp`, specifically.
I assume you are referring to this bit.
> The researchers discovered that you can find out a lot from open source data, including Facebook profiles and people-search websites

It had me wondering too.
I just checked a modern copy I have lying around and couldn't find that particular phrasing. However there are lots of other gems such as "a malfunction of the extraction system that causes cargo to move can be extremely hazardous."

Oh really. You don't say.
I think (but I cannot find a reference to now) one of the proposed syntaxes was that awaits were immediate and implicit in async functions, and that if you didn't want that, you could opt-out and get futures normally. Loosely,

async fn foo() {
let result = blocking_req(); // awaiting immediately here.
async {
let future = blocking_req(); // not awaited.
// can do more complex stuff w/ the future
}
}

IDK what happened to it, and it is a bit more complex IMO than what the Rust folks went with. However, I don't think it helps your gather case.

For gather, I think the problem w/ your proposed

return alpha + beta + gamma

is when does that happen? If I do

let some = alpha + beta;
// < ... code ... >
let more = some + gamma;

what happens / when are things evaluated?

At any rate, with the syntax as it is, I think your gather example is essentially¹:

alpha.join3(beta, gamma).await

or

Future::join3(alpha, beta, gamma).await

(Perhaps minus the `.await`, depending on when you need/want the result.)

There's no operator overloading, which I'm fine w/, as there is a need to choose between, e.g., select or join.

¹but I'm new w/ the async stuff, so if I'm wrong I'm assuming that Cunningham's Law will kick in and someone will correct me.
There's a few books around for this, first is Jeremy Kun's book https://pimbook.org/ and is probably exactly what you're looking for: math from a programmer's perspective. There's also Discrete Math w/Functional programming https://cs.wheaton.edu/~tvandrun/dmfp/ in which most chapters translate theorems into algorithms or turn sets into types. Sussman also has two books translating Lagrange equations and differential eq into Scheme but both assume an undergrad physics background. Brown has a course in linear algebra using Python http://cs.brown.edu/courses/cs053/current/lectures.htm but you can do it with any math language library that builds matrices or write your own naive implementation as you go.

Of course the best way to do this would be to try and model the notation yourself (if possible) into function specs or algorithms, as you go through various math books. Then you'd really understand the notation even if you failed to implement it. You could try Pyret to do this https://papl.cs.brown.edu/2018/func-as-data.html#%28part._.A...
The World’s Most Wondrous Public Transportation Options
If the subsidiary doesn't have enough autonomy, then their status as a local subsidiary should be revoked immediately. If the subsidiary is complicit in criminal activity, then they are now investigating a crime, potentially an international conspiracy, and there's already mechanisms to handle that.
It helps your discipline to do things you don’t like, even if in some sense you are forced to. You are not strictly forced to do them of course because there is no law against slacking off in school, you just need to attend. And high school generally is not compulsory.

I don’t know where you are from, Korea perhaps? But when I was 16 I had oceans of time for mischief, parties and endless amounts of skateboarding and just slacking.

I’m not saying that people can’t change their lives, or that they have to be slaves. I am saying that school teaches people to sit down and concentrate and do something that’s maybe not very interesting and probably a bit difficult but has a reward waiting down the line in the form of good grades and graduation. Deferred gratification is the most important life skill of all.

And people can definitely change their lives, in most countries there is no outside force stopping you from doing almost anything, starting a company, begging, travelling or whatever. But most people are neither very interested nor capable of doing anything out of the ordinary. Most people just want to swim with the current. And that’s a very good thing because we couldn’t have society and civilisation if everyone was an iconoclast.
Revisiting the cold case of cold fusion
That ruins the chaining aspect.
He left the airport in 2006, lives in Paris now.
Extremely poor design:

* Not DRY. What if I want to use a cache for production but disable caching in development? And I have 10s or even 100s of functions that rely on the cache? Because the decorators contain implementation/client-specific parameters, I now have to add another entire layer of abstraction over this.

* Implementation is tied to the decorator, e.g. `ring.memcache` -- seriously? Why does it matter?

* What about setting application defaults, such as an encoding scheme, a key prefix/namespace, a default timeout?

I'm sorry but this is over-engineered garbage and good luck to anyone who uses it.
FYI that project was killed last year[1]. Also, like a lot of research projects, there was a lot of auxiliary research that could end up quite useful, even if the initial idea didn’t work out. For example, figuring out how to put an antenna into a contact, how to safely store power, etc.

[1] https://en.m.wikipedia.org/wiki/Google_Contact_Lens
Yes the advances are coming from degree seeking students. That's kind of the point of a PhD program. Its to write an original work.

PhD students often receive a stipend. So they do get paid to do their work.
How about apps and adoption from developers? Those are much more important than an OS alone. As someone mentioned, we have bunch of OS aready, Tizen, Window Mobile?
Professors not knowing how to teach is common for research universities in the US. Their main job is research, and teaching is just something they do on the side.
I love Nix and NixOS personally... but it's been a tough sell at work, unfortunately.

Even with simple shell scripts... it's so easy to invoke programs with GNU extensions and later find they fail on a co-workers macos machine. And I often have a shell.nix sitting right there that defines the complete dependency closure; very frustrating to not be able to use it.
I as well think there could be promise in someday exploring that space, but for the moment my enthusiasm for hypothetical postfix macros (which have yet to ever be formally proposed) is somewhat dampened by the realization that `foo.bar.qux.qaz.await!()` would need to expand to `await { foo.bar.qux.qaz }`, which makes me consider how uncomfortable such macros would be to parse (the saving grace of "normal" macro calls being the fact that both the reader and the compiler know exactly where the span of a macro begins and ends by looking merely at the balanced delimeters).

IMO, if the goal were ultimate language consistency then that would involve both adding an `await` keyword (with mandatory braces, like `if` and the others) and a postfix macro for the cases where it looks nicer. However, when considered by itself, there's no denying that `foo.await?.bar` appears nicer than `foo.await!()?.bar`, especially if there is no guarantee that postfix macros will ever become a thing.

(Though in honesty I think all these proposals are just trending towards justifying an F#-style pipeline operator.)
Same thing with biology. A bs in bio is the most awarded degree in the US, no thanks to all the people gunning for pre med. You can get a job of course, but you have an uphill battle to get promoted much farther than entry level unless you start straddling multiple fields with your job description (business-y roles are a good option for a BS holder). An MS gets you up a title from the get go, but even then, for research jobs you need a PhD unless you want to hit a ceiling and make the same salary from 30 years old until you finally retire. Companies see a PhD as necessary proof of work for good r&d jobs. At least a PhD is free though!
But that starting point has to be initially checked somehow. Say we are user "bob" we open "/foo/bar/xyzzy" (for later use with openat), and, say, "bar" is writable to "mallory", then that isn't a path we can trust in the first place.

O_PATH is a Linux Kernel 4.x thing; can't find it in POSIX. Won't compile on non-Linux POSIX operating systems or older kernels. It seems to be an optimization; if we omit it, we just get a "fatter" file descriptor that takes more cycles to set up.
> A standard is set in stone as a fixed target for implementers.

Is that a descriptive or normative statement?
‘Cold case’ of cold fusion reopened by Google-funded scientists
Yep, american "scientists"...I knew it.
I think this is a much better idea, because it decomposes the problem into easier things for robots. People are talking about stems, but hold up! You can just make a second robot that picks up raspberries from a bucket and removes the stems. This sounds much easier to me.
> It should be obvious that the difference between the user friendliness of a program that shows you a real time window of the text you are editing with immediate feedback and a command line interface based editor designed for slow teletypes is much greater than the difference between two slightly different sets of commands that will be the majority of one's VCS use will be.

I think that anyone who is familiar with CVS & Git and with ed & vi/emacs will agree that there is a similar leap forward in capability. The move from CVS to SVN is a bit like the move from vi to emacs, but the move from CVS to Git really is like the move from ed to vi, vim or emacs.

I suspect that this is probably another example of the Blub effect, this time applied to VCS: the CVS user looking up at Git thinks, ‘Why would I ever need that? Besides, if I ever did I’m sure that I could roll something that was good enough,’ while the Git user looking down on CVS thinks ‘There but for the grace of God go I.’
To me, mocking of the caches for testing is super important and missing.

I searched the article, the linked "Why Ring?", and this page of responses for "mock", but no results.

Maybe it's just me!
Would totally depend on the missile and where it is coming from. Anything behind ... acceleration wouldn't matter as few missiles would have been fast enough to close the gap. Missiles to the side would be outrun. Missiles from the front are another story. A missile rising up from a point in front of the aircraft is a deadly threat. It doesn't even have to match velocity to make a kill. In short: acceleration for missiles below and to the sides. Stuff in front, time to turn. Stuff behind, forget about it.
I want to go out on a limb and say two things: (i) It probably is broken. (ii) That table doesn't show when the data was listed as public. The reference on the top speed is "Taylor 1988, p. [51]."
Although this is true, it is terrible from a developer UX perspective.

Yes, you can "dynamically"-decorate your functions at run-time using whatever global conditionals.

Yes, you can re-decorate the ring decorators.

But you shouldn't have to.

This design is guilty of the cardinal sin of being un-pythonic.
You seem to have cherry picked sources that have a lower estimate for all these figures, i.e., "propaganda numbers".

I think the best source for these numbers is the Wikipedia article "Deaths due to the Chernobyl disaster" [1]. From the article, Russia claims "estimates ranging from 4,000" while scientific and environmental organizations claim "no fewer than 93,000". It's clear that Russia wants to downplay the enormous human and environmental toll this has had and will continue to have.

[1] https://en.wikipedia.org/wiki/Deaths_due_to_the_Chernobyl_di...
He's right. China banned Facebook and no one is accusing Russia of hacking their elections. Clearly banning Facebook is the path forward for democracy and civil liberties. clearly.
As soon as I saw that whole section on database-related flakiness my mind went from "flaky unit tests" to "tests called unit tests that are actually integration tests". I worked on a team where we labored under that misconception for a long, long time. By the time we finally realized that many of the tests in our suite were integration tests and not unit tests it was too late to change (due to budget and timeline pressure).

I really like the different approaches to dealing with these flaky tests, that is a good list.
One HBO show and boom: https://trends.google.com/trends/explore?geo=US&q=chernobyl
I'm not willing to use Windows on my home machines, and I'm not them.
Continuous force and displacement measurement below the standard quantum limit
`fut.await()` looks too magical. There's no hint in that expression that it's anything other than a method call. You could argue the same about `fut.await`, except in this case `await` is a keyword and thus the expression `x.await` is known to be an await expression without knowing anything about `x`, whereas `fut.await()` requires knowing the type of `fut` to understand that the method call `.await()` resolves to the lang item. Also, since it's a lang item, you could write your own nostd library that picks a different name for the same lang item and cause even more confusion.
> That said, nuclear will never, ever be able to achieve either the real or the apparent risk levels of a wind farm or a bunch of rooftop solar panels.

I'm going to go ahead and point out that more people die falling off their roofs installing solar per kWh than have died per kWh from decades of nuclear operation [1]. Denigrating that data as mansplaining seems pretty anti-scientific. Both death/kWh rates are nearly zero compared to fossil fuels.

Apparent risks, now that's a real problem. Can be solved with PR and education.

Check my link in the previous post. You'll see that the industry is writing down in good detail exactly how it plans to reduce costs by increasing procedural efficiency without reducing safety.

To just say that appropriate safety has to be expensive, and any attempt to fix it is unsafe, is pretty bold, especially in the face of what the climate scientists are predicting with continued carbon emissions.

[1] https://www.forbes.com/sites/jamesconca/2012/06/10/energys-d...

[2] https://ourworldindata.org/what-is-the-safest-form-of-energy
Don't forget the Internet Archive!

The first version is from Nov. 14:
https://web.archive.org/web/20111114185849/http://matt.might...
The article index from Nov. 8 does not include the article:
https://web.archive.org/web/20111108003034/http://matt.might...

So we can say with confidence that this should have a [2011] tag and was published sometime Nov 8 - Nov 14 in 2011.
Had anyone tried to build a package using these instructions?

Did it work without issues?
Here's the tl;dr

app.use(cors());

defaults to Access-Control-Allow-Origin: *

If you know how CORS works, you already know that even if the resource is on localhost, it's open to any web page, including not on localhost. You won't find anything enlightening here.

If you don't know how CORS works but you're using the Express middleware for it anyway, read the documentation: https://expressjs.com/en/resources/middleware/cors.html#conf...
RadioShack was really ahead of their time, what with trying to collect your phone number and address every time you come in to buy a pack of AA batteries.

Now with smartphones it's all automatic and much harder to say "no" to.
Slime Thinks Fast and Slow
If they want to avoid a US OS, they probably want to avoid a US service too.
Should every API be modeled after how react works?
I really really don't mean to be dismissive here, but... you know the WHATWG largely emerged as an backlash against the W3C's efforts to create an extensible standard for allowing authors to create custom elements (what's more, they would be namespaced with actual schema, a la react prop-types, or—later—Typescript interfaces), with extensible forms (xforms). This is a process started in the late 90s! Two decades later, and there's people on the internet claiming the WHATWG are doing something novel reinventing this concept now.

WeakMap is ECMA. CSP was W3C and implemented by Firefox 4 years before HTML5 was released as a spec.

There's good stuff in the HTML5 (there would want to be in a spec. that size!), but it's remarkable how many of the cited examples are nothing to do with it.
> Instagram was ad-free for quite some time. Now every third or fourth post is a big, unmissable ad. Same thing in stories.

Stopped using Instagram because even the "organic" posts are ads or product placement of some sort. It seems like every time someone hits 10k subs or more, their content becomes >50% ads.
In Ireland, I remember the petrol being sold on the street in front of newsstands. It makes clear the reason for having the gas cap on the left side in Japanese and British cars, because people would just parallel park and fill up. I imagine those locations are rare now both for flow-of-traffic and environmental reasons.

In the US gas stations used to be very full service. For the price of a tank (and tip) you would get your radiator and tires topped off, windshield cleaned, etc. There were probably a few old groceries that had a couple pumps but the full service stations quickly became popular. That ended with the oil crisis and stagflation, and self service became the norm, except in a few holdout states like New Jersey, where full service was the law.

The sad result you mention (which is good for consumers, perhaps bad for the environment) is that commodity pricing and loss-leader mentality has made gas worth selling at a small loss to get people to buy high-margin items in the store. QT has cheap gas and expensive sodas.
> The check and the operation would need to prevent anything else from operating on it during that time.

I don't think you understand. If we verify that the absolutized path has sane permissions from top to bottom, then nothing else can operate on it; nothing else that is not either the superuser, or our own user ID. I.e. no untrusted security context.

(If you think that the requirement is literally "nothing else", such as a different thread in the same application in exactly the same security context, then that's a whole different set of goalposts in another soccer field.)
Hmm props to getting this out, but my way is has always been "bash is good enough" ja its not perfect a d feature rich but gets you 80% there and most linux based coders knows enough bash. I hate learning a new "language" just to deploy code or servers. Guess im just too old :)
In theory, yes. In practice, many people will flinch and sell, maybe even near the bottom.

edit: (But also, you should probably not own a ton of stocks near your retirement date)
Yes they have a huge mono repository and tooling to update projects in it to specific versions. You don't get a choice really. You can go home one night with your project on say Java 7 and then wake up and find someone has migrated it to Java 8 because they've decided it's Java 8 now.
> cost of pretty much everything would go up significantly

This just includes the short term costs.
It has to be some form of linux.

For all the reasons you said, it would take so long to get something usable, let alone security....
Trump administration’s attack on climate science goes full-Orwell
TLD matters to a certain extent. What is your main woe is that the name itself is already taken, so particular TLD (.com or any other) doesn't matter that much. Which TLD to pick is entirely different concern. It largely depends on your target market. Unless your target market is niche specific, tech savvy or limited to a certain geography, .com is a given.
"We have enough wealth"

The current system has wealth. If we changed to that system, all definitions would be less of what they are now, so you'd have to bake in the idea that more people are now building cheap housing in random places, and that grocery stores are given food non-stop to feed those people, and that doctors will want to live near them.

It doesn't account for the droves of people that may stop working because we don't _think_ like the people that work for Chipotle that no longer want to do so. We're all fucking programmers (well a lot of us are).
They're specifically looking for the string "Edg", not "E", not "Ed", not "Edge", they're specifically detecting Microsoft Edge.

Try it yourself:

Go to https://www.youtube.com/new

with

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3800.0 Safari/537.36 E/76.0.167.1

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3800.0 Safari/537.36 Ed/76.0.167.1

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3800.0 Safari/537.36 Edg/76.0.167.1

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3800.0 Safari/537.36 Edge/76.0.167.1

There should be no doubt this is malicious. They're specifically targeting Microsoft Edge. Varying the string away from the real Edge string (Edg/76.0.167.1) gives you the proper experience. They're badlisting Microsoft Edge (Edgium/Chromium based Edge), not goodlisting Chrome.