MurphyA/hacker-news huggingface dataset:
by fabian2k | 2025-11-01 16:43:53+00:00
They put a whole lot of children onto a plane in the middle of the night to deport them. This was only stopped because laywers got wind of it and a federal judge intervened almost immediately on the weekend.

They are trying to bypass any review by being fast and creating facts that prevent US judges from any effective action as once people are outside US jurisdiction they have very little power.

And immigration judges are not actual judges, they are part of the executive.
by mistr0 | 2025-11-01 16:44:18+00:00
Yeah I can imagine - although probably in any town you could go out and find a nice bit with nice houses and shops, and equally, you could find a bit where shops are closed and houses look a bit run down.

If I'm honest with you, I wonder if you need to think more critically about what you're watching? Grand Designs is designed to evoke envy (mostly) as well as some of the difficulties involved, which keeps people watching. I don't really watch YouTube but people generally seem more predicated towards watching things that evoke feelings of danger, anger, loss, worry, that sort of thing. In both cases you are being shown a version of the truth that results in the programme maker gaining somehow (money, views, whatever).

I'm only saying this off the back of your few comments here though, so apologies if I'm wide of the mark.
by kbd | 2025-11-01 16:44:22+00:00
I wrote my shell prompt in Zig years ago in part because I was interested to use its async/await to run all the git calls in parallel for the git status. My prompt is still fast despite never having parallelized things -- slightly slower now after adding Jujutsu status -- but I'm looking forward to getting to do the thing I originally wanted and have my super fast shell prompt.

To speak to the Zig feature: as a junior I kept bugging the seniors about unit testing and how you were supposed to test things that did IO. An explanation of "functional core imperative shell" would have been helpful, but their answer was: "wrap everything in your own classes, pass them everywhere, and provide mocks for testing". This is effectively what Zig is doing at a language level.

It always seemed wrong to me to have to wrap your language's system libraries so that you could use them the "right way" that is testable. It actually turns out that all languages until Zig have simply done it wrong, and IO should be a parameter you pass to any code that needs it to interact with the outside world.
by beloch | 2025-11-01 16:44:34+00:00
A better policy might be for arXiv to do the following:

1. Require LLM produced papers to be attributed to the relevant LLM and not the person who wrote the prompt.

2. Treat submissions that misrepresent authorship as plagiarism. Remove the article, but leave an entry for it so that there is a clear indication that the author engaged in an act of plagiarism.

Review papers are valuable. Writing one is a great way to gain, or deepen, mastery over a field. It forces you to branch out and fully assimilate papers that you may have only skimmed, and then place them in their proper context. Reading quality review papers is also valuable. They're a great way for people new to a field to get up to speed and they can bring things that were missed to the fore, even for veterans of the field.

While the current generation of AI does a poor job of judging significance and highlighting what is actually important, they could improve in the future. However, there's no need for arXiv to accept hundreds of review papers written by the same model on the same field, and readers certainly don't want to sift through them all.

Clearly marking AI submissions and removing credit from the prompters would adequately future-proof things for when, and if, AI can produce high quality review papers. Clearly marking authors who engage in plagiarism as plagiarists will, hopefully, remove most of the motivation to spam arXiv with AI slop that is misrepresented as the work of humans.

My only concern would be for the cost to arXiv of dealing with the inevitable lawsuits. The policy arXiv has chosen is worse for science, but is less likely to get them sued by butt-hurt plagiarists or the very occasional false positive.
by dale_glass | 2025-11-01 16:44:53+00:00
> I've been patiently waiting for their resurgence. Building embedded/mobile devices is their forte

Wouldn't most of those people have gone elsewhere by now? If you're a mobile device superstar, why would you stick around at Nokia once the mobile device part of it crashed and burned?

A company's just a legal structure, people change over time. And that was more than 10 years ago, and didn't they sell their mobile division to Microsoft?
by MangoToupe | 2025-11-01 16:45:11+00:00
Palm wine addicts have existed since pre history. Or banana beer, or other forms of wine, etc. But distilleries existed virtually everywhere by the 70s.

But even putting that aside, gluttons, drunkards, and gamblers are certainly ancient and well attested, certainly in the western (abrahamic/hellenic) tradition. Perhaps there are some societies without this but it not poverty or want or lack of abundance that provides relief.
by jmward01 | 2025-11-01 16:45:58+00:00
As I have gotten older I have liked 'vigilante justice' movies less and less. Superheros that always prove might makes right, cops that 'buck the system and do what is needed to get the job done', etc etc. It is because those actions always lead to exactly what we seen now, unchecked attacks on people. Corruption using 'we gotta do something and it means a few people will get hurt but it is worth it' as a tool to achieve their agenda. American media has been pushing this message out for so many decades now that we think these are the good guys fighting the hard fight when in reality the opposite is true. Law enforcement and the military should be held at a far higher level of accountability, not a lower one, because of the powers they wield. The country needs to grow up and stop believing, and allowing, this behavior to continue. Be an adult, show up to local city counsel meetings, get actually informed and not headline informed and vote.
by Herring | 2025-11-01 16:46:18+00:00
https://www.ey.com/en_us/insights/strategy/macroeconomics/us...

https://am.jpmorgan.com/us/en/asset-management/adv/insights/...

EY forecasts 1.7% GDP growth, most of which is AI (~1.1% according to jpmorgan). The broader economy is facing headwinds (policy uncertainty, tariffs, etc etc).
by StopDisinfo910 | 2025-11-01 16:46:28+00:00
Considering the number of provers and statistical analysers and given C is the only mainstream language with a formally verified compiler, I would say fairly well thank you.

Honestly, I am not even opposed to Rust. It has cool ideas. I do think it should care a lot more about being portable and properly defined and should have done so a lot earlier and I do deeply disagree with the opinion of some core team members that specification is meaningless.

C obviously always was a questionable choice for a tool like apt but Rust seems even worse to me. Apt has absolutely no need to be written in a low level language. At least you could argue that C was chosen because it’s portable but I don’t see what Rust has going for it.
by roywiggins | 2025-11-01 16:47:16+00:00
> you're white British with an accent from our shores, you don't have a very serious problem. Sure you could get locked up somewhere away from a lawyer for a few days which is terribly inconvenient

This may be statistically true, but it's probably not very good advice. You might equally end up deported, now that they are running everyone through every database looking for things that might make you technically deportable that would never have come up under previous administrations:

https://www.bbc.com/news/articles/c4g78nj7701o

You used to be able to get bailed while stuff got sorted out. That has changed. Now they keep you locked up for months, not days. How long are you prepared to hold out before agreeing to be deported despite being in the right? Racial profiling is certainly happening, but anyone can find themselves in this situation if the wrong database pings when they walk through an airport, and once you have been dropped into immigration detention, relying on your ethnicity to get you out is not a sure thing.
by zerocrates | 2025-11-01 16:47:41+00:00
No, the post is definitely complaining about articles written by LLMs:

"In the past few years, arXiv has been flooded with papers. Generative AI / large language models have added to this flood by making papers – especially papers not introducing new research results – fast and easy to write."

"Fast forward to present day – submissions to arXiv in general have risen dramatically, and we now receive hundreds of review articles every month. The advent of large language models have made this type of content relatively easy to churn out on demand, and the majority of the review articles we receive are little more than annotated bibliographies, with no substantial discussion of open research issues."

Surely a lot of them are also about LLMs: LLMs are the hot computing topic and where all the money and attention is, and they're also used heavily in the field. So that could at least partially account for why this policy is for CS papers only, but the announcement's rationale is about LLMs as producing the papers, not as their subject.
by SyrupThinker | 2025-11-01 16:48:58+00:00
Ignoring the actual proposal or user, just looking at karma is probably a pretty terrible metric. High karma accounts tend to just interact more frequently, for long periods of time. Often with less nuanced takes, that just play into what is likely to be popular within a thread. Having a Userscript that just places the karma and comment count next to a username is pretty eye opening.
by krater23 | 2025-11-01 16:49:06+00:00
I'm from embedded too. We tried to use rust in one of our projects and came to the conclusion that it makes no sense to convert our team from experiences C++ developers to beginner level Rust developers. Additionally to that, it was nearby impossible to control the amount of packages that come in with Cargo. We had for a small tool three versions of the same library as dependency in our binary.

Additionally to that, a part of the team doesn't had fun on writing code with Rust.

We trashed the whole tool, which was a massive loss of time for the project.
by kstrauser | 2025-11-01 16:49:50+00:00
Huh, that’s an interesting point, and I’d have to think on that. There are still plenty of cases where ordering would matter, like subtract(a,b), unless you go whole hog and define that like

fn sub(a:LeftOp, b:RightOp)

but that seems redundant. There are still plenty of other cases where I could your idea being useful. Like I always forget whether (in Python) it’s json.dump(file, data) or dump(data, file). Ultimately, should it matter? I’m passing a file handle and an object, and it’s unambiguous how those two args relate to the task at hand.
by JumpCrisscross | 2025-11-01 16:49:57+00:00
> there has to be somebody who decides what the default is

Sure. This happens with ad blockers, for example. I imagine Elsevier or Wikipedia would wind up creating these lists. And then you’d have the same incentives as you have now for fooling that authority.

> or people just don't care very much

This is my hypothesis. If you’re an expert, you have your web of trust. If you’re not, it isn’t that hard to start from a source of repute.
by woodruffw | 2025-11-01 16:49:57+00:00
I don’t think this is a good argument, given that there are manifestly successful languages that don’t have a formal specification. Python comes to mind.

(Plus, architecture quantity isn’t exactly the thing that matters. Quality is what matters, and Rust’s decision to conservatively stabilize on the subset of LLVM backends they can reliably test on seems very reasonable to me.)
by rapatel0 | 2025-11-01 16:50:03+00:00
There has never been a better time to build. The vast majority of executives likely don't comprehend AI and it's capability. (I'm not talking about silicon valley) I'm talking about everything else.

The highly likely scenario is that: - These people will spend money on "AI" to solve stuff to keep their job - These people will be so slow to respond that they are ripe for disruption/exit.
by avidiax | 2025-11-01 16:50:28+00:00
I'm saying you can keep track of all the riders and drivers, matchmake, start/progress/complete trips, with a single server, for the entire world.

Billing, serving assets like map tiles, etc. not included.

Some key things to understand:

* The scale of Uber is not that high. A big city surely has < 10,000 drivers simultaneously, probably less than 1,000.

* The driver and rider phones participate in the state keeping. They send updates every 4 seconds, but they only have to be online to start a trip. Both mobiles cache a trip log that gets uploaded when network is available.

* Since driver/rider send updates every 4 seconds, and since you don't need to be online to continue or end a trip, you don't even need an active spare for the server. A hot spare can rebuild the world state in 4 seconds. State for a rider and driver is just a few bytes each for id, position and status.

* Since you'll have the rider and driver trip logs from their phones, you don't necessarily have to log the ride server side either. Its also OK to lose a little data on the server. You can use UDP.

Don't forget that in the olden times, all the taxis in a city like New York were dispatched by humans. All the police in the city were dispatched by humans. You can replace a building of dispatchers with a good server and mobile hardware working together.
by cogman10 | 2025-11-01 16:51:20+00:00
IDK what the state of Emac/Zed is in terms of type information (I'm sure it depends on the language in question). For Jetbrains/Eclipse/Netbeans if there's a question about a type you can ctrl+click on the type and immediately pull all information about it.

In java, I rarely pay attention to the `import` section (and I know most devs at my company).

You can look up `using namespace std;` in google and you'll find a lot of articles saying it's a bad practice in C++. Everyone recommends writing the full `std::cout` rather than `cout`.
by uecker | 2025-11-01 16:51:21+00:00
The point of freedom in software is certainly that I can create my own fork. And individual projects a maintainer can certainly do what he wants. But it is still worrying if in community projects such as Debian when decisions that come with a cost to some part of the community are pushed through without full consensus. It would be certainly not the first time. systemd was similar and for similar reasons (commercial interests by some key stakeholders), and I would argue that Debian did suffer a lot from how badly this was handled. I do not think the community ever got as healthy and vibrant as it was before this. So it t would be sad if this continues.
by disgruntledphd2 | 2025-11-01 16:51:40+00:00
> Financial institutions are far from passive bystanders in the legal process that creates those laws, much less the regulatory process that applies them in practice. Binance is frankly probably the lesser evil at this point.

Ok, help me understand here. Like, the laws are passed by governments. The financial institutions complain but comply to some extent. How does this benefit said financial institutions? Or am I missing something here?
by VladVladikoff | 2025-11-01 16:53:38+00:00
My laptop is still a 2012 MBP. Granted I don’t use a laptop as my main computer, I use a hackintosh desktop. I might finally buy a new laptop in 2026, 14 years is not bad. If my new laptop can last that long I see no problem maxing out the specs at time of purchase.
by mpeg | 2025-11-01 16:53:40+00:00
I've literally never had a marketing person tell me whether I should use a <button> or <div>. Let's not pretend things like using the wrong semantic elements is anyone else's fault but lazy or inexperienced developers.

These days it's a moot point anyway, because everyone is using things like tailwind which provide a full reset for things like default buttons, so there really is no excuse.
by ufmace | 2025-11-01 16:53:42+00:00
Considering this issue did also make me think - maybe the real footgun here is the async mutex. I think a better "rule" to avoid this issue might be something like, don't just use the tokio async mutex by default just because it's there and you're in an async function; instead default to a sync mutex that errors when held across awaits and think very hard about what you're really doing before you switch to the async one.
by sethev | 2025-11-01 16:53:50+00:00
Oh, I think you're picturing executing your transaction logic and then sending writes off to a background queue. I agree, that's not a general strategy - it only works for certain cases.

I just meant that if you can structure your application to run write transactions in a single thread (the whole transaction and it's associated logic, not just deferring writing the end result to a separate thread) then you minimize contention at the SQLite level.
by jacobyoder | 2025-11-01 16:54:12+00:00
In 2004 I was at a company that dedicated a team of people to rebuilding a bunch of tables (lots of financial data) in to styled divs because... "tables are depreciated". The fact that they couldn't pronounce or understand the word "deprecated" should have been enough of a clue to ignore this person, but they were the 'lead' on the web team, and... had been there longer than other people. Obviously they must know what they're talking about. Weeks later after having converted dozens of spreadsheets to divs (instead of just using tables) they were 'done', but it was a tremendous waste of time that ignored all the semantics of tables. I was asked to 'help out' on that project to meet the deadline and refused, citing that it was not just stupid, but a big waste of time and against web semantics.

"table" was never deprecated in HTML at all, but was discouraged for general layout (we were aware of this even in the early 2000s). But for representing tabular data - like... data in rows/columns from spreadsheets (with column headers and such)... HTML tables were absolutely the right (only?) way to present this.

I was at that company less than a year...
by anonymousiam | 2025-11-01 16:55:37+00:00
Reverse delegation (RFC 2317) is the way IP-to-FQDN lookups are usually done now. Before this was popular, you could get your ISP to defer to your DNS for reverse records directly, versus them using a set of individual PTR records.

Even though the RFC was written in 1998, it took a while for it to catch on. For years, my DNS servers were using both methods.

Both methods make use of the .in-addr.arpa "domain" syntax.
by kstrauser | 2025-11-01 16:55:52+00:00
All modern editors do that pretty well with language servers now. Specifically, Emacs and Zed do this perfectly with Rust.

I do think it’s down to personal preference. With the fully qualified names, I can look at the screen and follow the flow without having to mouse over the various names in play. For that matter, I could print it out if I wanted to and still have all the information.

I don’t think you’re objectively wrong. It’s more that we have different approaches to managing the complexity when it gets hairy.
by matwood | 2025-11-01 16:56:07+00:00
Once the dust settles around AI, I agree with you. Unless we think the collective company's backlogs are going to stop being infinite, then any extra productivity that can be gained will be gained.

With that said, I think AI is just cover for the current set of layoffs. Companies are still right sizing from the pandemic/ZIRP over-hiring. Additionally, while none will say it at the risk of angering the administration, the economic uncertainty based on how someone is feeling day to day means companies want to derisk.
by rogerbinns | 2025-11-01 16:56:12+00:00
Yes. The interpreter warns by default, and requires steps to disable the warning. My release notes say that the GIL will be enabled when the package is loaded.

Is it madness that other packages claim they support running without the GIL, yet it is possible to cause corruption and crashes just by writing concurrent Python code? That is the case with the standard library. Compiler thread sanitizers don't work with free threaded Python. Diligent code inspection by humans is the only way to update C code so far.

Free threading is at the beginning of the project. It works. You get slow downs in single threaded performance due to extra locking, and speedups in concurrent performance due to threading. But it is possible to cause corruption and crashes via Python code. Don't expose it to untrusted data and code.

But do investigate it and see what works well and what doesn't. See what code patterns are now possible. Help improve the tools and documentation. It had to start somewhere, and the current state is somewhere.
by uecker | 2025-11-01 16:56:19+00:00
While memory safety is important, I do not believe it is now suddenly so important that it needs now needs to be solved quickly at all cost. There are far more pressing issues. I also do not think at all that C/C++ are dead end. In fact, I think it would be far more cost effective to continue to improve safety of C and C++ code via gradual improvement than adding another language into the mix. The reason is that complexity and the burden of long-term maintenance is the main issue we have in free software, and Rust makes this worse rather than better. Case in point, the fact that I have limited security updates because of some Rust video codec in the dependency chain hurts my security far far more than the fact that it might prevent some memory safety issue: https://www.debian.org/releases/trixie/release-notes/issues.... I think this is what people are missing. They over-exaggerate the important of memory safety over rather mundane issues which are actually far more important. I have never known anybody who was directly affected by a security issues caused by memory safety, I know plenty who were affected because their software was not up-to-date.