skysight-inc/HackerNews huggingface dataset:
I really like cancellation in Rust, and I don't mind that it's so forceful. Maybe it's because I've worked with Node.js which is all the way at the other end of the spectrum with no way of aborting promises externally. In Node if you want to abort an async operation, you need to thread a DIY signal/flag/callback throughout your entire program, or you'll be left with orphaned tasks still running. Compared to that, Rust's futures that just immediately stop when you abort them are a luxury.

I've written quite a bit of async Rust code, and I haven't hit the problem described in the blog post. I think there are a couple of reasons:

• Rust already has programming patterns (like Drop guards) that avoid leaving the program in an inconsistent state in case of panics, and this solves the problem for aborted futures too. If your tasks owns a TCP stream, then it will always close the stream when it's aborted.

• Aborting and error handling are usually tied together, e.g. `timeout(copy()).await?` aborts a future, but turns that into an error. Especially for network-related tasks it's natural to treat timeouts as yet another case of an I/O error. Each end needs to handle suddenly closed connections anyway, regardless whether they're closed by Rust or a network error along the way.

• Rust uses layered abstractions for async code, e.g. you have request/response servers or streams for protocols. This way you can't leave the network protocol in an inconsistent state, even if your request handling code is aborted. If you were writing to a multiplexed HTTP/2 stream, then the underlying protocol handler will send an end-of-stream packet for you when your higher-level response stream is dropped.
Indeed I am! HN readers are a fun group. I am receiving beeps almost every second, so I updated my previous shell script to keep a record of the connections netcat receives. Also, converted the beeping loop to a background job, so that the outer netcat loop does not have to wait for the inner beeping loop to complete before handling the next connection. Notice the '&' before the last 'done' in the improved alerting service below:

while true; do (echo ok | nc -q 1 -vlp 8000 2>&1; echo; date -u) | tee -a beeper.log; for i in 1 2 3 4; do printf '\a'; sleep 1; done & done

Here is a log of the timestamps of the connections received so far: https://gist.github.com/susam/159c7d92659b3185eb0b0d683998a3...
I have a feeling that part of the appeal of the touchscreen for Tesla was early on, they were desperate to ship things that had problems which hadn't quite been resolved yet. The automatic downloads enabled them to sell the car with "don't worry, that will be fixed soon and will download automatically".

I guess it is clever in some regards but like others, the touchscreen on my Skoda (thankfully mainly for media) is impossible to use without taking your eyes off the road, which is truly dangerous if you need it for basics.
It's likely that someone's girlfriend is in the same bubble as themself.
I think that DCOM can be used for communication between threads, when used in-proc with the appartment model, if memory serves me well. However in this case they are sending windows messages between the communicating threads, i think that this mechanism isn't very lightweight, as opposed to how it was advertised back then.
Point taken, and my judgement is not personally at you with the political correctness comment. It was a lament on the general recent (couple of years) development when we can see sprouting of and gaining undeserved media attention due to the socio-political climate in the west. This article is just point-in-case. There is overwhelming evidence (direct and indirect) even in the way our teeth and jaws evolved, collectibles and artefacts point to the fact that meat diet played overwhelming role in defining us as humans (in the wide context of things).
Honestly both the Amiga and ST were excellent computers. Judging by the A1000 I'd even say the ST was the better machine, considering the price.

The reason so many people who had an Amiga are (still) salty over the ST is that lots of games were ported straight from the ST without taking any advantage of the extra power of the Amiga besides audio. While the publishers are to blame here, the ST is the easy target.

Had the ST not existed, those games would have likely targeted the Amiga hardware first and foremost, and been far better as a result (proper scrolling, higher framerates, more and better colors, etc.). But again, the ST is not to blame for that.

Similar thing happened to MSX and Amstrad CPC owners with ZX Spectrum ports. These days all these machines have healthy homebrew scenes that show how nice the hardware really is. I still can't believe Dread and Metro Siege are real Amiga games. And Dread has an ST port, and that's a good thing.
In what field is this fraud occurring? Are we talking about a hard science?
Yes, you edited your reply to be a lot less polite after you saw my reply to your reply, and I don’t think I did anything to provoke that. I might’ve responded differently if I had realized you were in attack mode.

Some points I’d like to clarify:

1. Multiple contradictory edits in the answer is weird by Stack Exchange standards regardless of the merits of the discussion, that’s the main thing I observed.

2. Whether Euclid uses contradiction or not is not really open to interpretation: the word “absurd” appears right in the proof. If people want to split hairs about whether that contradiction is in the lemma or the main proof, I guess fine.

3. There are of course multiple subschools of constructivism that accept and don’t accept different things. Not all of them ignore computational complexity. For example, some ultrafinitists reject the unique prime factorization theorem on the basis that you can’t really execute the factorization algorithm even for relatively modest numbers. To be clear, that’s not exactly my view, but I would for example agree that something like “just find the prime factors” sweeps a bit of relevant subtlety under the rug: you can only do that conceptually, not actually.
To be fair, flashy UIs sell well so it is a strange place to be when you need to decide between "engineering good" and "flashy and saleable"
It should be; men have twice the risk of death from covid. I'm guessing Shadi needed to add "male" because it turned out that male + Hispanic > obese + diabetic + asthma + hypertension > Hispanic.
Also before powersteering manufacturers had to do a compromise between ease of use and available grip. Parking a car with wide tires such as a 70's/80's supercar was a real workout. Hence many cars of that era without powersteering had narrowish tires and thus very poor available grip and emergency braking efficiency.

Powersteering has allowed cars to have much more available grip and it is not a inherently a bad thing although it comes with its downsides too. Mainly fuel efficiency and overconfidence issue.
30% is the standard cut for platforms though, going as far back as the Minitel. And yeah, any platform is evil by definition, but Big evil takes more than that according to the OP.
I mean, I use microsoft tools even for compile on Linux nowdays.

It's hard to forget. :D
That is the argument you are making, and I struggle to see in what world being published in Nature is "being suppressed".

They make the claim "vaccines that pose 50% higher excess risk of myocarditis compared to an infection", and this is a misleading claim.

The risk to an individual of taking the vaccine is more sensibly measured against what happens to somebody who isn't vaccinated, not what happens to somebody who isn't vaccinated and also didn't die.

This is like comparing injuries in people who survive jumping out of a plane with and without a parachute. How important is it if people without a parachute break their arms less often?
> And why in the hell does a yolk need to have the horn on a button rather than the center of the yolk as anyone would expect? Maybe there's some technical reason i'm unaware of

No you're right, it's change for the sake of change. It is now a status symbol to show off how well you drive a vehicle whose management is more challenging than other cars.
Thoughts on Client-Side Platforms
In general for inversion, we have object A (argument) and object I (identity) and a function F of two arguments, so we have equations: `F(A, X) == I, F(A, I) == I, F(X, I) == I, A != I, A != X`, where A, I, and X are objects in the same category, i.e. they must be circles `(x² + y² == r²)`.

If F is defined as `ra•rx`, then `ri == 1`, and inverse will be `rx = 1/ra`.

If F is defined as `ra + rx`, then `ri == 0`, and inverse will be `rx = 0 - ra`, where negative radius means hole.

If F is defined as `ra²•rx²`, then `ri == 1²`, and inverse will be `rx = sqrt(1/ra²)`.

If F is defined as `ra² + rx²`, then `ri == 0²`, and inverse will be `rx = sqrt(0 - ra²)`.

And so on.
Cuba has historically funded healthcare and medical research very well. It has a lot of the infrastructure and organisation in place already compared to other poor countries.

Arguably this is what those other countries should have been doing all along. However that level of coordination usually requires a degree of public activity that tends to reduce external private funding from countries like the US. They're in a tricky situation.
>probably more reliance on the app update systems of third parties.

Exactly right. Big platforms with guaranteed support is one thing, but here's the situation for smart TVs right now:

It's 2022. You build an app for SuperScreen's latest range of smart TV. You update it every so often, and SuperScreen are happy to certify those updates and help you push them.

It's 2023. You port your app to SuperScreen's latest range of smart TVs. You keep updating your 2022 app, but SuperScreen are slightly less helpful now, as most of their attention is focused on the 2023 set (and upcoming 2024 range).

It's 2024. You port your app to SuperScreen's latest range of smart TVs. But when you want to update your 2022 app, SuperScreen say "hmm, we don't really have a lot of time now to certify apps for these older devices, please try to make as few updates as possible". It's a little tough but you have to do it, as the alternative is that 2022 TVs don't get any of your new features.

It's 2025. You port your app to SuperScreen's latest range of smart TVs. But now SuperScreen refuse to certify updates to your 2022 app saying "these are legacy devices and we can't justify the time or effort to certify apps on this platform any longer... unless you were to pay us a LOT of money".

You might get approval for one last update, paying SuperScreen the money, and then you effectively mothball your 2022 app. It becomes a "legacy" app for you as well, stuck in maintenance mode, not getting any updates or new features. And this is on a TV that is only four years old. So the best way forward is to make your native layer as small and light as possible, and shift all of the heavy lifting into the runtime client layer. If most of your client UI is a downloadable JS / WASM runtime, then you can keep supporting it even if the platform owners don't want to play ball any more.
I haven't used Caddy for this use case, but as a simple proxy and file server it's just great. IMO it's largely what Traefik promises but fails to keep. An actual production Caddy configuration with HTTPS set up, web sockets and everything fits on a single line (or 3 if you want multiple hosts).

I can see myself checking this out (but for v2, of course). It looks to be just as nice in this area as in the others.

More software should strive to be this user friendly.
Why not ? It's not like Amazon is only an online library these days...
I'd argue the users benefit from having something that integrates tightly with the OS rather than an application that targets the lowest common denominator of all platforms. Qt applications always feel a bit shitty to me, I only use them if there is no alternative.
The Spider of Doom (2006)
Ebola set the way forward for faster approvals : https://www.nature.com/articles/s41541-020-0204-7 it also ( luckily) uncovered many flaws in the process that were improved upon.

The faster approvals were because of prioritisation of the government's during a pandemic and nearly flawless execution of Pfizer.

But doing something faster doesn't mean it's new. In many cases it means you made your existing processes more efficient. Not changed them.

You are also changing your point. You said Biontech did almost nothing and compared it to a iphone app, lol. They could have chosen someone else and there aren't many that failed approvals. ( Except if you count Russia). But as mentioned, Pfizer was the best choice.

The largest difference in making it faster was an in-place term that allowed simultaneous clinical trials, which was unique and funded by the government due to extra costs and risks for pharma. This was not due to Pfizer and shouldn't be attributed to them as you are trying too.

Without that regulation it would have taken multiple years like before.

The government's also quickened feedback from months to weeks, which was an additional efficiency improvement.

If you're "in the know", you sure are forgetting the most important "details" for cutting the duration till approval vs. the past.

In the context of this article, it's important to note that the first authorized vaccine was not funded by the program.
Some ko rules only address a subset of repeating positions, and still allow for infinitely long games (sometimes ruling those as a no-result requiring the game to be played over).

The so-called superko rule simply states that no previous position can be repeated, which seems preferable.
Robin isn't going to like where this is going
I wish these kind of cars with touch screen could be optionnally equipped with controllers on which user could assign and customize whatever function they want. Something similar to midi controllers for DAWs full of knobs, buttons and sliders.

Search 'Akai midimix' to get an idea if what I am thinking at.
You're looking for your first junior software engineer job, now what?
Also described in Brad Stone's book series "The Everything Store" and "Amazon Unbound"
> Lockdowns had no impact on mortality.

This is literally impossible, because viruses cannot teleport through walls.

Unless there is confusion between the government calling for lockdowns, and people actually doing lockdowns?
Thanks for the comment. It is indeed something I've been considering. In fact, lots of the optimization done here is to move the logic away from the game objects , which should enable the flow you've described.

I ended up not doing it in this iteration because:

- cocos2d's custom shader support is kind of poor, especially documentation is pretty much zero

- the dot is not "purely" visual. For example you can trace and highlight a resource's movement. This is not a blocker per se, but requires more work
Presumably they were prioritizing treatment for those 65 or older over treatment for younger people, who will almost all get better without treatment, rather than leaving those over 65 to die. Even on the far right I don't think mass killing of retirees is a popular policy. In that context, being categorized as "equivalent to being 65 years and older" would be an advantage, not a disadvantage.

I don't think affirmative action is a "far-left" policy in general, but rather a policy that enjoys broad popular support, at least when it comes to things like employment and education rather than immediate lifesaving treatment.
> ... is going to have major consequences in everyday life.

is going to ? Already has.

Used car prices start climbing Jul '20.

https://www.cargurus.com/Cars/price-trends/
There are two bits of context you need to understand this.

First: Early nuclear missiles weren't very accurate - you don't have to be very accurate when your target is the size of Moscow. A missile silo is a much smaller target!

So AIUI missile silos were hardened to survive a nuclear bomb landing 500m away - but they wouldn't survive a direct hit.

Second: There was a theory, at one point in the cold war, that one side could launch a surprise attack that struck and disabled the other side's nuclear weapons. Or at least, disabled a large enough fraction that the counterattack was survivable.

This was seen as winning. Or as close to winning as you can get, in a nuclear war. And it was seen as relatively more ethical than targeting cities.

The jargon for this is "counterforce" or "disarming" strike [1] and it was part of the rationale for having a ridiculous number of bombs - if you have enough bombs to destroy the world 10 times over, you can destroy the world even if 90% of your bombs have been destroyed in a surprise attack.

Later in the cold war other technologies were developed - high precision guidance, submarine launched missiles, and missiles with multiple warheads. Between them they made a disarming strike seem unlikely to work. But on the other hand there are still an awful lot of missiles around and they gotta be targeted somewhere. If you'd already sent a dozen at the pentagon and a dozen at the white house, why not send some of the remainder at a few nuclear silos?

Of course, you might well say this all seems pretty unlikely. A nuclear war? In this day and age? But people who think that probably aren't in the market for a disused nuclear bunker, except as a historical curiosity.

[1] https://en.wikipedia.org/wiki/Counterforce
Feels like too many people think “published paper = truth”, when really the paper is just the start of a journey towards truth, on which hurdles such as replication, independent scrutiny, and common-sense/real-world testing must be overcome before we can start treating them as reliable. And I think most scientists do actually get this, and what we suffer from is a media environment that jumps on the first sniff of a result and holds it up as definitive proof of something.
Japan's Kowa says ivermectin has 'antiviral effect' on Covid-19
It is completely absurd. "Lockdowns" is shorthand for "people not coming into contact with other people in a way that spreads the virus". Because the virus cannot teleport through walls, lockdowns necessarily prevent transmission.
Thanks, this article confirms indeed that Dr. Malone is one the 50 or so people in the world, who has the highest legitimacy speaking of that topic.
I just invest in ETFs & Stocks, and a bit of playing in Etoro, and I have money in a roboadvisor, so I can't help you in that. Again, in Spain, the best place for asking for financial help, aside from professional, is the Rankia.com forum.
You can for example declare than on draw black wins and give white some small material advantage.
Not only that, but there is more going on than just auditing. If Apple spent the time necessary to constantly do deep security dives, and spent the money on top talent to do it, it still wouldn't get done because it is constantly a moving target unless they froze all new development. Otherwise they have done a complete walk through of Mac OS 12.1, but 12.3 is released and they have n't even started on a full walk through of 12.2. These are time intensive tasks, meanwhile customers and shareholders are still wanting the latest, greatest, and shiniest.

Then at the end of the day, customers are still installing 3rd party applications, so does apple have to walk all of their code too?
> In this situation, large capital expenses make sense on the buyer side (to ensure future supply and widen their visibility horizon)

Does it?

Are these actually large capital expenses ("cash" [or credits on a bank balance sheet] is actually being locked up and transferred to the suppliers) or are these purchase orders where fractions of the cash are actually transferred at the point these long term deals are being made and some ones else is actually on the hook (i.e a creditor) securing that?

Because if its something like the latter (which I'm pretty sure it is), suppliers still run the risk of future demand cratering as well as the buyers (esp the ones that are fronting the cash and still will have that innovatory on hand until they can actually unload it on to consumers in finished products), and if Jeffery Snider who as been warning about something like this for months now and more recently in "When GDP’s Almost All Inventory" [0], I'm pretty sure those buyers are gonna get hosed with the suppliers…

[0] https://alhambrapartners.com/2022/01/27/heightened-conflict-...
There could be other reasons that it's downvoted, even if it's not taken "seriously". The fact that it's a low effort comment that has barely anything to do with the OP, that it's a rehashing of the same old "unpopular opinion" that's not really unpopular here, the fact that it takes a nice little post of a small utility and shifts the tone to something negative just because they have an axe to grind - all of these are other possible options people might downvote this oh-so-ironic comment.
It's a joke, they're just referencing modern trends in web development and a dose of /r/programmerhumor
I suspect the real problem was it was hurting other parts of the business. They needed to abandon it to free themselves to accept the reality of the dominance of the iPhone.
The child might refuse to install it though.
I think we’re on the same page. The point I was trying to make is that reciprocal/multiplicative inverse in every day use seems like it’s a property of a number and not of a function only because most people just assume that the function we’re inverting is multiplication. The comment I was replying to missed that.
Blueprint for Revolution
I think the expression "see how the sausage is made" is widely misused, here included.

While you might not have enjoyed your stint the sausage factory, sausages have a long, successful history. Handling meat safely is hard, and it has been done with varying levels of success over the years, but historically sausages weren't much worse than any of the other meats despite the nature of their creation, and with modern food standards they are pretty much safe when handled properly (of course proper handling depends on the type of sausage).

If you didn't like what you saw and, as a result, decided not to eat any more sausages, this seems more like a gut response on your end than any particularly deep insight into sausage production. People are generally aware that some of the steps in the process aren't nice to look at, but they judge the product based on the end result.
Stress is a physiological reaction to certain stimulus. You can stab people with blood monitors and conclude that yes, it is a high-stress environment.
Heightened Conflict of Interest (Rates): When GDP’s Almost All Inventory
Seems doable (difficult but doable) and a valuable idea if you have the permit from the family. Death changes everything in no time so we would need to use really fresh samples and filter what is expected to be in the body (lots of inner flora that would contaminate everything) from what is new, shouldn't be here and is interesting.
Hasn’t happened to me yet, and also you have to remember that the occasional road trip hassle is offset by about 30+ gas station trips you don’t make every year, because you usually just charge at home
Name a few such stories, besides Erlang related.
Why would that be? Don't you think "they" have better uses for their spare nukes?
And intelligence agencies updating the list of target objects?
Ryan invented WUPFH because Kelly couldn't reach him. [1]

[1] https://theoffice.fandom.com/wiki/WUPHF.com_(Website)