MurphyA/hacker-news huggingface dataset:
by kibwen | 2025-11-01 13:14:57+00:00
> Deadline would only be the minimum duration after which the language, when evaluating the future / task, would return the empty set/result.

This appears to be misunderstanding how futures work in Rust. The language doesn't evaluate futures or tasks. A future is just a struct with a poll method, sort of like how a closure in Rust is just a struct with a call method. The await keyword just inserts yield points into the state machine that the language generates for you. If you want to actually run a future, you need an executor. The executor could implement timeouts, but it's not something that the language could possibly have any way to enforce or require.
by TrackerFF | 2025-11-01 13:15:29+00:00
Because who's going to stop them?

What happens right now is this: ICE can run loose and do whatever they want. If some judge finds their activities illegal, they can block ICE from doing the illegal things.

But...who's going to stop them? Not the DOJ. Stephen Miller has said that ICE have "federal immunity". The keen observer will of course know that there's no such thing as "federal immunity", so a charitable way to interpret that statement is that no-one federal will go after them.

So what about states, and local police? Sure, they could start arresting them, but then again, Miller et. al have warned the states about not interfering, threatening with going after LEO's etc. with federal charges if they do so.

The long story made short is that they can (and will) keep doing illegal shit until someone stops them, and that's not going to happen as long as Trump is POTUS. DOJ and ICE leaderships has explicitly said that their workers should just ignore the law and courts.
by orwin | 2025-11-01 13:15:36+00:00
> Ukranian(?)

Basically Ukraine had a lot of small "security" (mercenary) groups post 2014. In the beginning of the Russia-Ukraine war, those group were basically told "please go oppose Wagner in Africa", and some found themselves in Soudan (and other in Armenia). I'm not sure if now they're paid by local forces. I don't have any information post-war though, my friend left the comapny and came back in France since the war.
by intended | 2025-11-01 13:17:05+00:00
Eh?

Theres too many moving parts in your very short paragraph, to actual engage with without any substantial engagement being minced into woodchips, I fear.

Theres many things that have happened since the 40s, just to name ONE thing that has resulted in this - we have much better psychological technology than we did ever before. Skinnerian conditioning, reward schedules, their results - we never had that.

MS Excel alone would mean we better ways for the statistically inclined to zero in on more attractive addictions, just through better data analysis.

Just consider how common place and obvious A/B testing is. How do you think humanity will fare on average, against industrial strength siren songs?
by zX41ZdbW | 2025-11-01 13:19:31+00:00
I was using it just half a year ago, after either reading MDN or reading what AI suggested. Which means, this API is not obscure and not forgotten. Using `rows` and `cells` is very convenient for keyboard navigation across table cells.

https://github.com/ClickHouse/ClickHouse/blob/master/program...
by chasil | 2025-11-01 13:20:10+00:00
Google has many, many government contracts.

I believe that they would face enormous scrutiny in multiple contexts if they adopted Graphene as the next version of Android.

Google also wants Play and GMS to have complete control of the device for their own selfish reasons. I do not see them willingly sandboxing their own control.

So I can think of a few reasons.
by darkwater | 2025-11-01 13:20:22+00:00
> I would agree ZIRP fuels those things (to unhealthy levels), but not that it's always the root cause.

It you were to set a house on fire with just a lighter in your hands, you would not succeed. If you have a lighter and a tank of gasoline, you might probably succeed. ZIRP was the fuel, the lightener and your will are the "root causes". But with no fuel, no fire.
by Marshferm | 2025-11-01 13:21:17+00:00
The problem is the dichotomy between specifics (robotics, tumors) and the arbitrary (sentences, imagery, code). No one seems to be taking into account an animal that verifies events using the arbitrary requires vocal and gestural analog sing-a-longs to stay semi rational.

Not even the companies directly responsible for the sing-a-longs have surmised the analog commentary track is required to keep us animals glued to our signals. It’s all a C-suite shitshow.
by repstosb | 2025-11-01 13:21:50+00:00
Modern CPUs do out-of-order execution, which means they need to identify and resolve register sharing dependencies between instructions. This turns the notional linear model of random-access registers into a DAG in practice, where different instructions that might be in flight at once actually read from or write to different "versions" of a named register. Additionally, pretty much every modern CPU uses a register renaming scheme, where the register file at microarchitecture level is larger than that described in the software-level architecture reference, i.e. one instruction's "r7" has no relationship at all to another's r7".

Caches aren't quite as mix-and-match, but they can still internally manage different temporal versions of a cache line, as well as (hopefully) mask the fact that a write to DRAM from one core isn't an atomic operation instantly visible to all other cores.

Practice is always more complicated than theory.
by timeon | 2025-11-01 13:21:58+00:00
> Scala? Kotlin? Swift? Zig? None of those languages have built such poor reputations for their communities.

> I didn't see C++ users jumping into Rust threads posting attacks, but there are many examples of Rust users jumping into C++ or C threads, posting attacks.

I already seen this with Zig. And even without language communities. Look at this whole thread. Look in to the mirror. Regularly when Rust is mentioned on HN. Anti-Rust cult comes to complain that there is Rust.

Even if someone just posts "I have made this with Rust" - then this cult comes and complains "why do you need to mention Rust?!". Like look at your self. Who hurt you?
by aurintex | 2025-11-01 13:23:42+00:00
Then, we are in Matrix ;) But I think this is already one step ahead of my idea ;)

But I think I know, what you mean - the human aspect should not be lost in the process. Do you see a chance for the future, what can unite the two aspects, i.e., supportive AI without losing the human touch? How could this be ensured?
by MSFT_Edging | 2025-11-01 13:24:22+00:00
> no one is forced to do it

This logic always bugs me because no one truly lives in a vacuum. People are flawed and generally need help from a community. A small community can't really fight back a well endowed company like gambling companies. The whole(stated) reason android is losing unsigned side loading is because grandmas in SEA are sideloading gambling apps.

It's obvious to me that gambling is generally a vulnerability in the human psyche. For many, it short circuits something in their brain and forms genuine addiction.

It's actually insane to me to use this vulnerability as a tax base to fund roads and schools, because regardless of the funds, your incentives will still be perverse and those incentives will dictate that more people need to be losing their money to out-of-state firms because a small portion of it might fund roads and schools.

The incentives basically state: "A percentage of our population must become sick and addicted to risk and reward in order for society to function". Is this not basically the concept of Omelas?
by Esophagus4 | 2025-11-01 13:24:43+00:00
Keep in mind “great engineer” will be a subjective term that means different things to everyone.

To Meta, it might mean cream of the crop, $1m+ engineer. To early Google, it might mean Stanford grad with deep CS knowledge. To a no-name startup, it might mean someone who accepts the job who takes initiative and knows how to crank out ugly code quickly on AWS and makes good prioritization decisions.
by auxym | 2025-11-01 13:24:53+00:00
FWIW, I agree that Araq is an abrasive character and probably not a great community leader for an open source project.

But I disagree with your take on the moderation team. I don't know if you have specific names to call out, but PMunch, miran and the rest of the team have been nothing but welcoming, in my experience.
by cogman10 | 2025-11-01 13:26:11+00:00
Especially in ways that worked cross browser.

Young folk don't understand just how wildly different IE5 was to the Netscape or the Mozilla browser. Or just how bad Javascript was when it started to be used on the internet.

I've lived through and seen the evolution. For all the shit the JS community takes for constantly revving frameworks, it's 1000x easier to make a website that looks the same regardless of browser due to a lot of these frameworks and browsers themselves evolving.
by intended | 2025-11-01 13:26:14+00:00
If everything is coercive - Yes.

Your definition of coercive is too permissive, so it ends up being more of an ideological stance, but its a saturday, so its a fun argument to work through.

If something is coercive, its inherently aiming to generate an unfair transaction. That means we need to spend a ton of effort on forums where such unfair transacations can be reversed, and punitive measures applied.

Otherwise we are always going to fail as a society, simply because coercive technqiues will be the default. Any new business, discovery, or product which provides a net benefit without defending itself from predatory practices will be torpedoed. resulting in a moribund economy and culture.

Having gone through what you have, I suspect you quietly prefer people learning from your example, over discovering the same lessons by following in your foot steps.
by skerit | 2025-11-01 13:26:16+00:00
Interesting, but the JavaScript examples hurt:

let table = [ ['one','two','three'], ['four','five','six'] ]; let b = document.body; let t = document.createElement('table'); b.appendChild(t); table.forEach((row,ri) => { let r = t.insertRow(ri); row.forEach((l,i) => { let c = r.insertCell(i); c.innerText = l; }) });

Use full words for variable names!
by iainmerrick | 2025-11-01 13:27:03+00:00
You’re right, of course, but this reminds me of when Chrome didn’t obscure your passwords when looking at its autofill settings. The developers argued that it would just be security by obscurity -- if somebody has access to your computer when it’s unlocked, they can do anything they want, so obscuring your passwords does nothing.

The counter-argument is, even if it’s not perfectly secure, that extra bit of friction before you can see the passwords is useful, and may just save your bacon if a casual thief has access to your computer for a few seconds.

The Chrome team eventually saw sense and added some client-side password protection.

As long as you don’t only have client-side protections, of course (and maybe your clueless auditors were making that mistake).
by elmerfud | 2025-11-01 13:27:52+00:00
You clearly didn't seem to read anything that I wrote, especially the point about where the constitutional power to make money and set the value comes from. Nor does it seem you understand anything about the Constitution itself. Because you cannot talk about respecting the power of small government and local governments while simultaneously ignoring the document that says any powers that aren't specifically listed here are granted back to the States.

So let me say this again, and maybe you can go look it up yourself, the Constitution gives the power to make money and set the value to Congress. Congress gave that power over to the president. There was a time early in the history where states and localities thought that they had the power to make money and it was a big confusing mess. Which is why the power was directly written in to the Constitution that the money is a federally governed thing.

So any state or locality that is trying to pass some law or ordinance overriding the making or setting the value of money is automatically wrong. You have representation the power is within Congress every two years you get to reelect around 60 to 70% of Congress. So stop complaining on hacker News and start paying attention to the congressional elections.
by Bender | 2025-11-01 13:28:18+00:00
My self hosted mail server is averse to anything with a low bar to entry. When a registrar rents thousands of domains to a group for nearly free they get added to a file that will just REJECT them with a URL or snarky message. There are a handful of TLD's that my DNS will NXDOMAIN as well. I have done this for decades and have zero regrets while acknowledging it is hard for people to get a decent short name on .com net org. IRL and internet scammers are why we can't have nice things.
by Mystery-Machine | 2025-11-01 13:28:53+00:00
The variable naming convention used here could be improved for clarity. I prefer appending `El` to variables that hold DOM elements, as it makes identifiers like `tableEl` clearer and helps avoid ambiguity between variables such as `table` and `row`. Also, the variable named `table` does _not_ actually represent a table element; it would be more accurate to name it `data` or `tableData` to better reflect its purpose.
by kibwen | 2025-11-01 13:29:14+00:00
While the Mozilla layoffs were a stressful time with a lot of uncertainty involved, in the end it hasn't appeared to have had a deleterious effect on Rust development. Today the activity in the Rust repo is as high as it's ever been (https://github.com/rust-lang/rust/graphs/contributors) and the governance of the project is more organized and healthy than it's ever been (https://blog.rust-lang.org/2025/10/15/announcing-the-new-rus...). The language certainly isn't rudderless, it's just branched out beyond the RFC system (https://blog.rust-lang.org/2025/10/28/project-goals-2025h2/). RFCs are still used for major things as a form of documentation, validation, and community alignment, but doing design up-front in RFCs has turned out to be an extremely difficult process. Instead, it's evolving toward a system where major things get implemented first as experiments, whose design later guides the eventual RFC.
by piker | 2025-11-01 13:29:35+00:00
U.S. DOT provides a ton of road funding to the states as well. If memory serves, it’s often over half their budget.

[Edit: fun fact: threatening to withhold this funding is how the U.S. DOT managed to essentially federalize drinking age of 21. (https://en.wikipedia.org/wiki/South_Dakota_v._Dole)]
by imtringued | 2025-11-01 13:29:36+00:00
>In real world, the futurelock could occur even with very short locks, it just wouldn't be so deterministic.

You have to explain the problem properly then. The problem here has nothing to do with duration whatsoever so don't bring that up. The problem here is that if you acquire a lock, you're inside a critical section. Critical sections have a programming paradigm that is equivalent to writing unsafe Rust. You're not allowed to panic inside unsafe Rust or inside critical sections. It's simply not allowed.

You're also not allowed to interrupt the critical section by something that does not have a hard guarantee that it will finish. This rules out await inside the critical section. You're not allowed to do await. It's simply not allowed. The only thing you're allowed to do is execute an instruction that guarantees that N-1 instructions are left to be executed, where N is a finite number. Alternatively you do the logical equivalent. You have a process that has a known finite bound on how long it will take to execute and you are waiting for that external process.

After that process has finished, you release the lock. Then you return to the scheduler and execute the next future. The next future cannot be blocked because the lock has already been released. It's simply impossible.

You now have to explain how the impossible happened. After all, by using the lock you've declared that you took all possible precautions to avoid interrupting the critical section. If you did not, then you deserve any bugs coming your way. That's just how locks are.
by lores | 2025-11-01 13:29:44+00:00
Countries housing the most refugees:

Iran 3.5 million

Türkiye 2.9 million

Colombia 2.8 million

Germany 2.7 million

Uganda 1.8 million

Pakistan 1.6 million

Chad 1.3 million

Poland 1 million

Ethiopia 1 million

Bangladesh 1 million

Source: UNCHR, https://www.unhcr.org/refugee-statistics
by isodev | 2025-11-01 13:29:51+00:00
> Under the hood, we clone the repo into a VM, spin up gpt-5-codex for every diff, and ask it to output a JSON data structure that we parse into a colored heatmap.

Wait, you're consuming the energy a small town needs for a week just so you don't have to write a couple of lines to parse your content into a heat map of whatever strings you're looking for? This is crazy, and given our climate shituation, should be illegal.
by tux3 | 2025-11-01 13:29:59+00:00
I think the kernel and microcontroller use-case has been overstated.

A few bare metal projects use stackless coroutines (technically resumable functions) for concurrency, but it has turned out to be a much smaller use-case than anticipated. In practice C and C++ coroutines are really not worth the pain that they are to use, and Rust async has mostly taken off with heavy-duty executors like Tokio that very much don't target tiny #[no-std] 16-bit microcontrollers.

The Kernel actually doesn't use resumable functions for background work, it uses kernel threads. In the wider embedded world threads are also vastly more common than people might think, and the really low-end uniprocessor systems are usually happy to block. Since these tiny systems are not juggling dozens of requests per second that are blocking on I/O, they don't gain that much from coroutines anyways.

We mostly see bigger Rust projects use async when they have to handle concurrent requests that block on IO (network, FS, etc), and we mostly observe that the ecosystem is converging on tokio.

Threads are not free, but most embedded projects today that process requests in parallel — including the kernel — are already using them. Eager futures are more expensive than lazy futures, and less expensive than threads. They strike an interesting middle ground.

Lazy futures are extremely cheap at runtime. But we're paying a huge complexity cost in exchange that benefits a very small user-base than hasn't really fully materialized as we hoped it would.
by ipaddr | 2025-11-01 13:30:03+00:00
So do private in person conversations. Going the route of North Korea putting two way speakers in each house would help make those conversations available to the government. Think of all of the child exploitation you could stop by removing any sense of privacy. Of course they would figure a way around this and everyday citizens would have to deal with the lack of privacy but at least they thought of the children so we should keep voting them in.
by hexbin010 | 2025-11-01 13:30:10+00:00
> “ICE officials have told us that an apparent biometric match by Mobile Fortify is a ‘definitive’ determination of a person’s status and that an ICE officer may ignore evidence of American citizenship—including a birth certificate—if the app says the person is an alien,”

This is "computer says no (not a citizen)". Which is horrifying

They've just created an app to justify what they were already doing right? And the argument will be "well it's a super complex app run by a very clever company so it can't be wrong"?
by aurintex | 2025-11-01 13:30:22+00:00
That makes me wonder --> how do you currently deal with your smartphone, which often has wakeword detection enabled (like “Hey Google”)? Or when you're visiting friends who have an Alexa device at home. Would that already be a problem for you?

I’m genuinely curious where you draw the line. Because in practice, many of us are already surrounded by passive listening systems, even if we don’t actively use them ourselves.
by Too | 2025-11-01 13:30:52+00:00
14 is a indeed very long. Let’s instead assume 12, it’s 2013 and you got a top specced T440 with 4th gen i7. That’s actually not bad and the build quality is like a tank as all Thinkpads. Nothing I would use as daily driver myself but having used many other thinkpads of that generation I can see why others are still getting by with it today.

Since we are talking about OS support. 4th gen Intel isn’t supported by Windows 11, so you’d have to upgrade to Linux.
by bookofjoe | 2025-11-01 13:30:53+00:00
>Name of Turkey

The name for the country Turkey is derived (via Old French Turquie) from the Medieval Latin Turchia, Turquia, from Medieval Greek Τουρκία, itself being Τούρκος (borrowed into Latin as Turcus, 'A Turk, Turkish'). It is first recorded in Middle English (as Turkye, Torke, later Turkie, Turky), attested in Chaucer, c. 1369. The Ottoman Empire was commonly referred to as Turkey or the Turkish Empire among its contemporaries. The word ultimately originates from the autonym Türk, first recorded in the Bugut inscription (as in its plural form türküt) and the Hüis Tolgoi Inscription (as türǖg) of the 6th century, and later, in the Orkhon inscriptions and the Tariat inscriptions (as both türük and türk) (𐱅𐰇𐰼𐰜) of the 8th century.

In 2022, the Turkish government requested the United Nations and other international organizations to use Türkiye officially in English, to which they agreed.[1][2] Turkey has remained the common and conventional name in the English language.

Source:https://en.wikipedia.org/wiki/Name_of_Turkey
by elif | 2025-11-01 13:31:05+00:00
This is insane level of data to store for every person's likeness.

Fake masks are so advanced now, I'm sure the IC has 3d printers that could just arbitrarily map any face to any user. And this insane spoofing capability would give not just the government, but contractors, corrupt police departments, or hackers or rich people that aquire the data.

And that's just the physical realm because to me that's the scariest one, but giving these power manipulators access to likeness for deep fake video is probably sufficient to cause all kind of havock.
by firefax | 2025-11-01 13:31:07+00:00
Thanks for this pointer and explanation, I appreciate it.

Also my "dev enviornment" is vi -- I come from infosec (so basically a glorified sysadmin) so I'm mostly making little bash and python scripts, so I'm learning a lot of new things about software engineering as I explore this space :-)

Edit: Hey which of the models on that page were you referring to? I'm grabbing one now that's apparently double digit GB? Or were you saying they're not CPU/ram intensive but still a bit big?
by zozbot234 | 2025-11-01 13:31:50+00:00
Note that this is only true of the Java/C# volatile keyword. The volatile keyword in C/C++ is solely about direct access in hardware to memory-mapped locations, for such purposes as controlling external devices; it is entirely unrelated to the C11 memory model for concurrency, does not provide the same guarantees, and should never be used for that purpose.
by estimator7292 | 2025-11-01 13:31:50+00:00
Population demographics is not zero-sum. Very soon the fraction of people who are too old to work will be larger than the fraction who can. We'll lose a shit ton of able, working bodies all across the board. This will tank the econony and quality of life for everyone.

This is the exact problem Japan is facing. You should go read up on how well that's "self-correcting" (it isn't)
by XorNot | 2025-11-01 13:32:22+00:00
You Americans are really going to have to get over trying to blame corporations for all your problems, or expecting them to fix all your problems.

This is a problem from your government, by your government, that you voted for - one way or another. Pretending this problem is originating from anywhere else except the political choices you're making as a nation is denying reality.