skysight-inc/HackerNews huggingface dataset:
I think the author is confusing two things here:

1. User-space threads / Green threads

2. Structured concurrency

The former one is an advantage of async/await, but is not unique to it (see Go or Java Loom for examples that involves no function coloring problem). And the latter one can be implemented with both OS threads and green threads (see Structured concurrency JEPS for Java [1]).

[1] https://openjdk.org/jeps/462
Async/Await as a syntax thing wasn't, but Async/Await as "don't just blindly use Threads for scaling to a myriad of incoming HTTP requests" was.

I remember the Apache webserver story and that one has little to nothing to do with Webbrowsers or JavaScript ;)
Very cool! It pretty much covered the entire earth. I wonder about the connectivity and speed difference between the north poles and those in the middle. I was using it on a cruise, it is very stable.
Despite ESBuild often being used as a default in new Rails apps, I was surprise to find very little experiments about rollup.
> he'll have to replace all of his storage devices out of pocket, which won't be cheap

22 TB of storage - ~500 $

the data stored on the fried disks - may be priceless

Yeah, the old adage to always make backups applies here, but I guess many people (me included) back up stuff by keeping duplicate copies on different drives, because it's very rare for two drives to fail at the same time. Except if your PSU decides to fry them, of course...
Firstly, Rust does not have async Drop and it's unlikely to be added in the foreseeable future. Secondly, cancellation signals is a more general technique than async Drop, i.e. you can implement the latter on top of the former, but not the other way around. For example, with async Drop you can not ignore cancellation event (unless you copy code of your whole task into Drop impl). Some may say that it's a good thing, but it's just an obvious example of cancellation signals being more powerful than hypothetical async Drop.

As for implementation difficulties, I don't think so. For async Drop you need to mess with some fundamental parts of the Rust language (since Futures are "just types"), while fiber-based concurrency, in a certain sense, is transparent for compiler and implementation complexity is moved to executors.

If you are asking about how it would look in user code, then, yes, they would be somewhat similar. With cancellation signals you would call something like `let res = task_handle.cancell_join();`, while with async Drop you would use `drop(task_future)`. Note that the former also allows to get result from a cancelled task, another example of greater flexibility.
> 22 TB of storage - ~500 $

Side note, but damn, imagine telling someone in the 90s that storage would get this cheap. We've come a long way.
Strangely, a search for how many satellites are in orbit right now, returns those numbers:

- 9,494 active satellites

USA 2926
China 493
United Kingdom 450

So the 5k plus from Starlink are in this count yet?
Cut out the stuff you don’t value, the amount of stuff you can do when you don’t own a TV and never visit news or social media sites[1] is astounding.

The downside is your reply to any questions like “have you seen <popular show>?” will perpetually be blank stare, shrug

[1] 1 exception - a ruthlessly curated rss feed reader, and this site - although i’m experimenting with using this site via a “best of” aggregation feed. For all popular stories here there are a 2nd wave of thoughtful posters who arrive to a thread a day or 2 late. I’m thinking they are also filtering similarly but i have never asked.
I have heard about them in embedded systems where there are no OS threads, because there is no OS, but there is Async tasks and a scheduler
There are a few MSIE web icons in there too that would not have been in Windows 3.1.
Oh. I wish they had a "forecast vs. actual" for the past 24 hours.
Seeing these in 48 * 48 feels uncanny. 32 pixels was the norm back then.
Is food truly considered a low-value product today? In my country, it's one of the most marked-up items, second only to printer ink. For instance, farmers receive $2-3 per ton of potatoes, yet these are retailed for $3-10 per kg, over triple what they were just 3 years ago. Despite the general tripling of food costs (just for basics, processed things have increased even more heavily), the earnings of farmers and others in the supply chain, except for supermarket executives and shareholders, remain unchanged. This price inflation, driven by greed, results in significant profits for those who can bypass the system. For example, if one could acquire a ton of potatoes and sell them at farmers markets for $2/kg, undercutting supermarkets, they could make a substantial profit quickly. However, buying directly from farmers is not an option as they are typically bound by strict contracts with major grocery store chains, this leaves theft which has the added enticement of yielding even higher margins than doing things properly.

Now, a truckload of luxury goods like avocado as given as an example of cargo stolen in the article? I imagine you'd be set for a year of a single heist with less risk than robbing banks and less exploitation than 'honest' work.
I've never been on internet relay chat.
If you're the only one reading the code, then sure write it however you like it.

But using long chains of expressions is the same as one-liners or point-free style in Haskell. It saves some typing and also you can skim the code more easily, but only if you're extremely familiar with what's going on there.

I wonder how much you can benefit from this, if you return to the codebase after a 6-month break though. Maybe some people do manage to really memorise these details, but for some of us the effect is more like "wtf is this code doing?"
No my dear,

this hack

type Operation int

const (
Escalated Operation = iota
Archived
Deleted
Completed
)

has nothing to do with

typedef enum {Escalated, Archived, Deleted, Completed} Operation;

Only someone that can't get type systems would ever assert they are the same.

Literally "Go enums suck", https://news.ycombinator.com/item?id=39564737
Memory is an interesting thing. I once claimed to somebody I was seeing that I had done/said something humorous, fully believing that it was my own experience. It was only when he mentioned hearing that joke from a famous standup comedian that it really hit me - I think what really happened was that I watched a clip a long time ago, and thought hey that's the kind of thing I'd have done - and then proceeded to record the memory as mine, even going as far as attaching it to a specific shop from the same chain in the story.
How does it compare to pocket?
scoop is a significantly better tool and can actually manage the things it installs.
This is an incredibly milquetoast question, I'm shocked it's on the front page. No crazy insight into anything related to computing.
I like the ...___... operator when your code is sinking.
Each charged particle in the standard model has a corresponding anti-particle that is (as far as we know) identical to it in all ways except the sign of the charge. The electron has the anti-electron, also called the positron. Each kind of quark has a corresponding anti-quark, and these can form an anti-Proton. There are muons and anti-muons, tau and anti-tau, the plus and minus W bosons are each other's anti-particle.

There is nothing mysterious about anti-particles, they have all been observed directly, and they simply have the opposite electrical charge. The one thing we don't understand is why there seems to be so little antimatter in the universe, despite antimatter behaving identically to matter as long as the two don't meet. This could just be a fluke of the matter distribution in the early universe, but it could also indicate that there is a difference we don't know about.
"They are likely the two most difficult parts of any design for parametric polymorphism. In retrospect, we were biased too much by experience with C++ without concepts and Java generics. We would have been well-served to spend more time with CLU and C++ concepts earlier.

-- https://go.googlesource.com/proposal/+/master/design/go2draf...

CLU was invented in 1976, C++ concepts were proposed in 2005!
That's part (not the only) of the signal thing being evaluated: can you efficiently familiarize yourself with a codebase. I'd encourage you to try it. It's not that big a codebase: 140 files, 80k lines of code. Given that similar commands (incr/decr) exist, finding a way to get multiplication to work shouldn't be out of most qualified candidates' skillsets for a software engineer job (language skills aside).
In Windows 95, even if you authored an icon containing more than 16 colors, it would still be displayed as a 16-color icon. (With a strange exception that there were 4 additional colors that could appear in icons, including another gray, a greenish gray, sky blue, and a nearly white color)

Then finally Windows 98 updates the shell to actually support full-color icons, and this was a big deal. I think Microsoft Plus for Windows 95 also added this feature as well.
What's wrong with mkfs.<tab-tab>[select-middle-click] /dev/sdc1?
Seems pretty open and shut to me. That power supply either has a connected equipment warranty or it does not.

Dollars to doughnuts that it doesn't (https://www.evga.com/warranty/power-supplies/), and likely has language confirming the opposite for liability reasons (it does). Commonplace for consumer gear.

Sure the good, and human thing to do would be to cut the guy a check, that's inarguably true. It's probably even a good business decision to, given that bad press is likely more expensive than a couple grand worth of drives. Legally though, they're probably in the clear.
‘Tree’ has always been my go-to. How about you?
It's funny how that shade of teal green went super out of fashion for many years but it's now a "hot" color again on Android material design apps.
By imaginative do you mean the whole dark forest game theory and such? That's all taken straight from the original SETI scientific discussions back in the 60's and 70's. It's been explored by various scientists in that context, as well as a whole slew of sci-fi authors in the intervening years. The version of the theory presented in 3BP doesn't hold water, but there have been various strengthened alternatives presented over the years. The Killing Star comes to mind, but I think also the wolves of the Revelation Space series are a good match too. Sci-fi also abounds with many other innovative answers to the Fermi paradox that make more sense than the dark forest hypothesis.

Other than that I really don't know what you might take as 'innovative.' Antinatalists wanting to wipe out humanity? Done to death since Limits to Growth, The Population Bomb, and Silent Spring were released in the 1970's, albeit usually with environmentalists occupying that role. Frankly I'm tired to death of that trope. PTSD from the cultural revolution? Well other than the slew of books and memoirs on that very topic, there's also all of holocaust literature.

It certainly has a very imaginative misunderstanding of the three body problem which gives the book it's title. Not only does the author completely misunderstand what it means for there to be no closed-form solution to the three body problem (it does NOT mean orbits would be chaotic), but interestingly we've actually discovered an exoplanet where the trisolan planet is in the book. And guess what? It's in a perfectly stable orbit within the habitable zone. So the whole plot gimmick that gives the book its title turns out to be a misunderstanding of undergraduate mathematics and physics by the author.
An entire universe is quite different to a considerably more limited orbital space
> It seems clear at this point that Covid (the latest variants in the wild, at any rate) does not cause "often debilitating effects"

Depending on the study, you have up to 45% of people experiencing covid symptoms (aka Long Covid) almost four months past infection, and around 10% that experience symptoms 18 months past infection [1].

The amount of people so massively impacted by Long Covid that they can't work any more or have to significantly reduce their labor hours is so large that it's been theorized to be a significant contributor to current labor shortages [2]. So yes, it does classify as "often" IMHO.

> and so any mitigation must have its costs, which are very high for any easily-transmissible respiratory illness, weighed against its benefits, which are pretty low.

Just the 2023/24 covid+rsv+influenza wave is suspected to have cost the German economy alone 36 billion euros in lost income and sick day payments [3].

We need pathogen mitigation concepts, the sooner the better.

[1] https://www.nature.com/articles/s41467-023-43661-w

[2] https://www.brookings.edu/articles/is-long-covid-worsening-t...

[3] https://www.deutschlandfunk.de/ifw-grippewelle-koennte-die-d...
Companies that plan on doing something like this: please make sure you are paying your candidates market wage for the interview.

For Leetcode style questions, there is some amount of interaction from the interviewer, so the cost to the company is that employee's 1 hour wage. If as a company, you feel like this is an efficient and superior way of interviewing, consider giving that amount to the candidate.
What’s the best way to find a location in the center of totality and also ideal weather conditions.

As for location, I’m finding the NASA map hard to use: https://science.nasa.gov/solar-system/skywatching/eclipses/n...

For the weather, I realize that clouds may pop up. And, I’m not sure how much I can rely of local / regional weather to tell me where, within a 4-5 hour radius, I should drive for best conditions.

Lining these two up (as well as handling traffic), will be difficult I imagine. For what it’s worth, I’ll be in Austin.

—

From another comment: https://www.cleardarksky.com/ec/2024-04-08_eclipse_map.html
Is the data really gone, from the perspective of Physics?
Not when it is a matter of national security.
Does that runtime run the tasks across multiple cores?
OK, I'll jeer: I'm a big fan of [McCarthy60], but everything-is-a-list implicitly introduces order, and the 21st century ought to explicitly accommodate the unordered as well. (there ought not be any is-more-basic-than relation between ordered and unordered)
Great, want to go debug a bunch of container processes running on a cloud Kubernetes cluster, with all security policies turned on?
Before I tried to make my own, I had been convinced that an icon is just a resized large image. For me up to this moment, it's amazing, how hard is to create an icon or pixel art. How every pixel counts, how the creator needs to manage the shades, gradients, and sometimes two pixels will show for example the white and the pupil of the eye.
This really needs some screenshots and/or video of what it is.
I would argue abundance based on CO2 being a fairly common gas and "easily" processed. Silicon in silicate minerals is common, but it's much harder to crack out of them.
Thanks for your charitable response to a reader who quite obviously misunderstood what you were writing about. You might want to update your article to make that clear, as "preprint review" isn't a term I had ever encountered before, and a simple reading of your article doesn't obviously indicate that you were talking about post-publication review. (Note that outside of academia, upload to arXiv is publication, so yes your "preprint review" would be a post-publication review.)
the same with fashion all around
If you have some random set-top box or camera that doesn't support exFAT, fair enough, but the situations are becoming few and far between. Windows, Mac, Linux all have native support for it.

No (practical) volume size or file size limits is a huge win for exFAT over FAT32.
My possibly unpopular opinion is that async/await is a mistake as a first class programming construct. That functionality should 100% be in libraries for two reasons: 1) that way it won't infect the actual language in any way and 2) it will be more difficult to use so people will only reach for it if they really need it.

Sync code and threads is the way to go for 99% of the cases where concurrency is needed. Rust handles most of the footguns of that combination anyway.
> the iPhone SDK is Apple's intellectual property and they can charge whatever they want.

Unless they sell iPhones in a jurisdiction that enforces the phone owners right to own their device, which may severely limit Apple's ability to charge for that. Let's see. I have a hunch the fee will be waived sooner or later in the EU.
This question is asked over an interview (I’ve personally faced this question) and the company isn’t deriving any more value out of asking this question as opposed to a Leetcode-style question, so I disagree.
Some of those icons are from 2000/Me, such as the round recycle bin with blue arrows, or the computer and network icons with cyan screens.
i turned it off halfway through the first episode when it became clear that they had rewritten it to be british/american
This is 100% correct. Emad tried to lure me into the trap that Eleuther eventually fell into, and I lucked out by blowing him off after getting weird vibes from him. This was back when he was unknown, but was running around offering a bunch of researchers massive GPU cluster time for seemingly altruistic reasons but were in fact creepy reasons. In reality he wanted his name on their work.

I have the DMs to prove this, and have not ever said something like this about someone. I wouldn’t make this accusation lightly, for whatever it’s worth. In the HN discussion of that article, I had left a comment, which Emad DMed me on Twitter about, saying no no, he never lied to investors, and tried to convince me that what I was saying wasn’t true. I was wondering why he cared so much. In retrospect it’s probably because it was correct.

I’ve never worked with him, to be clear, and the few colleagues who have worked at Stability have had generally positive things to say. But there was one that was screwed over by them hard (he was doing contract work, and never got paid for it), and I can think of at least four other alarming data points that all point to the same thing.

It’s unsettling not knowing whether to speak up about this. On one hand it doesn’t really matter that much. On the other hand, it’s the fundamental difference between a CEO that tends to IPO vs one that tends to fail. I hate seeing people fail, and I genuinely thought that my feelings about Emad were mistaken since empirically they were doing fine. Turns out, nope, not fine, and the original impression was right. Weird experience.
I'm wondering it this is even technically possible because of bandwidth? There is many more mobile cell towers worldwide - all they are big, connected to power grid, connected internet with fiberoptic, much closer to users but such one tower can still struggle to handle traffic during peak times when many users are connected.
> I thought random walks tended to stay close to the initial state...

Can you remember from where you got that impression?
could be the terrible working conditions you're often subjected to in wet labs. I am / was in chemistry, but have put a lot of effort into transitioning into a more programming / data heavy role to avoid the bullshit, lack of safety standards, and poor pay that comes with doing work in wet labs.

The problem is the same everywhere at the moment, no one wants to pay for good work anymore, but areas like research and wet labs which are dangerous and thankless jobs in the first place, this has the added problem of employers having been coasting on peoples passion and dedication these last few decades already, so this extra burden is simply too much for most. The dam has burst and people are simple leaving, and it would be too little to simple 'go back to how it was'. Even paying more than what was being paid at this stage would be too little, once you've started re-spec'ing, why would you stop?
I suspect the country borders problem will never get resolved. Even now, starlink is only available in US-allied countries.
There still is a lot of non-coding dna in there.
> WSL is nice, but it takes up a lot of RAM on my system. I prefer to use MSYS2.

That's why you trash WSL2 and just stick with WSL1. I'm surprised they didn't mention it at all.

Keep MSYS2 around for where WSL1 doesn't suffice, but that should be fairly infrequent.
Maybe it's just because I do that a lot, but imo potential candidates that are HN readers already know how to do this, if there are no gotchas. I find leetcoee considerably harder.
Bluecurve was amazing. For me, nothing in the Linux world has equaled it since. It was so nice and polished with thoughtful colors and design. It was quite similar in colors to Mac OS 8 & 9 (the platinum gray, the purple-ish blue).
Async/await with one thread is simple and well-understood. That's the Javascript model. Threads let you get all those CPUs working on the problem, and Rust helps you manage the locking. Plus, you can have threads at different priorities, which may be necessary if you're compute-bound.

Multi-threaded async/await gets ugly. If you have serious compute-bound sections, the model tends to break down, because you're effectively blocking a thread that you share with others.

Compute-bound multi-threaded does not work as well in Rust as it should. Problems include:

- Futex congestion collapse. This tends to be a problem with some storage allocators. Many threads are hitting the same locks. In particular, growing a buffer can get very expensive in allocators where the recopying takes place with the entire storage allocator locked.
I've mentioned before that Wine's library allocator, in a .DLL that's emulating a Microsoft library, is badly prone to this problem. Performance drops by two orders of magnitude with all the CPU time going into spinlocks. Microsoft's own implementation does not have this problem.

- Starvation of unfair mutexes. Both the standard Mutex and crossbeam-channel channels are unfair. If you have multiple threads locking a resource, doing something, unlocking the resource, and repeating that cycle, one thread will win repeatedly and the others will get locked out.[1]
If you need fair mutexes, there's "parking-lot". But you don't get the poisoning safety on thread panic that the standard mutexes give you.

If you're not I/O bound, this gets much more complicated.

[1] https://users.rust-lang.org/t/mutex-starvation/89080
Isn’t the point that you have a way to get to a point far away faster than you can get to a point in between? The worm hole thing ist because you can only exit at discrete points so it pulls a single point far away, and it’s sorrounding, closer to the starting point. That’s probably hard to map to a 2D map because there would be some overlap between the different „islands“ starting from subway stations
I’ve always thought async await is just a less clunky implementation of green threads. Not as a feature parity replacement, but trying to fill the same niche.
https://github.com/gildas-lormeau/SingleFile
While other industry players have certainly seen significant advancements, AI stands out as being on an accelerating trajectory fueled by a potent combination of big data, computing power, and algorithmic breakthroughs.
It's interesting to see an almost marketing-like campaign to save face for async/await. It is very clear from my experience that it was not only a technical mistake, it also cost the community dearly. Instead of focusing on language features that are actually useful, the Rust effort has been sidetracked by this mess. I'm still very hopeful for the language though, and it is the best thing we've got at the moment. I'm just worried that this whole fight will drag on forever.
P.S the AsyncWrite/AsyncRead example looks reasonable, but in fact you can do the same thing with threads/fds as long as you restrict yourself to *nix.