MurphyA/hacker-news huggingface dataset:
by tom_ | 2025-12-13 21:13:28+00:00
The 286 looks like it ought to be usefully quicker in general? Motorola did a good job on the programming model, but you can tell that the 68000 is from the 1970s. Nearly all the 68000 instructions take like 8+ cycles, and addressing modes can cost extra. On the 286, on the other hand, pretty much everything is like 2-4 cycles, or maybe 5-7 if there's a memory operand. (The manual seems to imply that every addressing mode has the same cost, which feels a bit surprising to me, but maybe it's true.) 286 ordinary call/ret round trip time is also shorter, as are conditional branches and stack push/pop.
by rokoss21 | 2025-12-13 21:13:38+00:00
False dichotomy. Medical records and writing style reveal different categories of information. Medical data: extremely sensitive, can enable discrimination/blackmail. Writing quirks: revealing but not dangerous in isolation.

The real question: who has access and what can they do with it? Using a local open-source model to polish your writing is fundamentally different from sending everything to a corporate server. Context matters more than the tool.
by twodave | 2025-12-13 21:13:42+00:00
I’ve been doing a rewrite of some file import type stuff, using a new common data model for storage, and I’ve taken to basically pasting in the old code, commented out and telling it to fill the new object using the commented out content as a guide. This probably got me 80% of the way? Not perfect, but I don’t think anything really is.
by LeFantome | 2025-12-13 21:13:48+00:00
What drives me personally nuts about the CentOS saga is all the “community” hand-waving about creating a bit for bit clone of a distro.

There can be no “community just shipping builds of RHEL code as, by definition, you cannot change anything. That means you cannot contribute. In my view, an Open Source “community” cannot just be people that use things for free. It is supposed to be about collaborating to build things.

At least now we have Alma Linux which strives to be ABI compatible with RHEL but builds it themselves from CentOS Stream. They actually build something. They can actually contribute (and they do). They can innovate. For example, they have continued the x86-64v2 builds even though RHEL has abandoned them. On Alma, you can at least claim to be building a community.

I do not use any of these distros by the way, in case you think I am shilling something.
by why-o-why | 2025-12-13 21:13:50+00:00
I tried to use ProtonVPN when I switched over to ProtonMail a year ago. But so much of the web does not work when you're on a VPN. For example even HackerNews has VPN restrictions. More and more sites know where VPN endpoints originate. How will VPNs prevent this in the future without them just become easy to block?
by alsetmusic | 2025-12-13 21:14:01+00:00
It's a bit dark, but I'm doing much better now, so happy ending. No need to wish me well or anything, I'm the happiest I've ever been (thankfully).

After reaching an age where bi-polar disorder goes full swing, I was unable to manage manic episodes; they'd spring up and I'd be awake for days and then crash horribly. I lost all hope that I'd be able to hold down a typical job ever again. I became a 24h/7d alcoholic with the goal of never being conscious and trying to sleep through life until it ended.

I was at the local shop where I bought my booze buying a bunch of beer and vodka around 7-8am. A guy near me at the counter made a comment about what a great party must be coming. I looked at him, probably dead-eyed, and said, "I'm an alcoholic."

He put his hand on my shoulder. He didn't say anything. It was just a moment of compassion. It was deeply kind. What was communicated was simply that someone cared and, to this day, I wish I had a way to thank him for that profound gesture.
by melvinroest | 2025-12-13 21:14:03+00:00
> it never seemed really practical.

IMO this is partially true but that's mostly because not enough people are working on it. If Pharo would have as much people working on it as Python, it'd be practical really quickly.

> Maybe what I was missing the most was static/explicit typing

I actually have a talk where you can hack typing in. To be fair, it will be checked during execution, so it's not a compile time thing. It's somewhere around here (I did like 3 mini talks in one mini talks, it was pure chaos, haha [1]). It's about 5 min., the whole talk.

Personally, I'm a fan of type hints, but ultimately engineering culture and standardization is more important. Or at least, in a professional context, in a personal code context I like dynamic typing and when it gets too big, I refactor it to explicit typing.

[1] https://www.youtube.com/watch?v=FeFrt-kdvms&t=2270s
by intelec1 | 2025-12-13 21:14:13+00:00
BMW EVs Can Now Use Tesla Superchargers — This Is Really About APIs, Not Cars

BMW EVs in the US now have access to Tesla’s Supercharger network. On the surface, this looks like a consumer convenience win. Underneath, it’s a textbook case of platform convergence.

Tesla’s Superchargers used to be a vertically integrated stack:

proprietary connector

closed authentication

Tesla-only billing

Tesla-controlled routing logic

BMW’s inclusion means Tesla had to open multiple layers at once — not just the plug.

What actually changed

Hardware

NACS ports on newer BMW models

certified NACS adapters for existing ones

Software / backend

Superchargers can now authenticate non-Tesla vehicles

billing is tied to BMW accounts, not Tesla apps

charging parameters are negotiated dynamically with BMW BMS

This is very similar to how payments or identity systems evolve: once you standardize the interface, vendors stop mattering as much as the protocol.

Why this matters

Charging networks are becoming utilities Like cellular towers or payment rails, fast charging only scales when it’s shared.

Closed ecosystems don’t age well Fragmented standards increase friction, reduce utilization, and push users elsewhere.

Data is the real asset Interoperable networks generate better load forecasting, pricing models, and infrastructure planning.

UX follows backend standards Once Superchargers appear in BMW route planning, range anxiety drops without adding new UI complexity.

Bigger picture

This feels like the EV industry replaying old tech history:

USB-C replacing proprietary ports

OAuth replacing custom auth

IP beating closed networking stacks

Standards win slowly, then all at once.

The interesting question isn’t why BMW joined Tesla’s network, but how long any automaker can justify running a closed charging system at all.
by madaxe_again | 2025-12-13 21:14:22+00:00
I’ve always gone for a document that expands fractally - that is to say, the title is clear, the opening paragraph gives an overview that a stakeholder would want, the following paragraphs give top level detail for a quick skim/end users, and then you delve into the detail of each feature/fix/etc.

The first sentence should inform of any breaking changes or major (e.g. security) fixes. For instance:

We are pleased to announce the release of version 2.2.1, which includes several fixes for major issues, includes one change which will require action on your part, 36 bug fixes, 12 enhancements, and the new combine harvester feature.

And then you drill into the top level. Also, categorise, it helps people find stuff.
by AndrewKemendo | 2025-12-13 21:14:35+00:00
And most computers were entirely shit in the 1950s

yet here we are today

You must’ve missed the point: people invested in desktop computers when they were shitty vacuum tubes that blow up.

That still hasn’t happened for any other user experience or interface.

> it's good and versatile enough for what most people need to do with a computer

Exactly correct! Like I said it’s a limitation of the human society, the capabilities and expectations of regular people are so low and diffuse that there is not enough collective intelligence to manage a complex interface that would measurably improve your abilities.

Said another way, it’s the same as if a baby could never “graduate” from Duplo blocks to Lego because lego blocks are too complicated
by miki123211 | 2025-12-13 21:14:57+00:00
I understand your point, and I agree with it in most contexts! However, for the specific use case where one assumes that the client and server are running the exact same code (and the client auto-refreshes if this isn't the case), and where serialization is only used for synchronizing between the two, decoupling the state from it's representation on the wire doesn't really make sense.
by HumanOstrich | 2025-12-13 21:15:08+00:00
Yea that's a common theme of excuses for both Rust and Nix. Wrong though, because most anyone who can use a computer at all can learn the basics of Vim.

Seeing that flake.nix badge of complexity lets me know a project will be a nightmare to set up and will break every other week. It's usually right next to the Cargo.toml badge with 400 dependencies underneath.
by LargoLasskhyfv | 2025-12-13 21:15:12+00:00
The Ruhrgebiet may be a melting/mixing pot, but it comes without an Ümläüt :-)

https://dict.leo.org/german-english/r%C3%BChren vs. the name of the river it's mostly built around https://de.wikipedia.org/wiki/Ruhr (SCNR)
by kmeisthax | 2025-12-13 21:15:39+00:00
I have to wonder if we need, say, a special "secret data" type (or modifier) that has the semantics of both crypto/subtle and runtime/secret. That is to say, comparison operators are always constant-time, functions holding the data zero it out immediately, GC immediately zeroes and deallocs secret heap allocations, etc.

I mean, if you're worried about ensuring data gets zeroed out, you probably also don't want to leak it via side channels, either.
by solatic | 2025-12-13 21:15:41+00:00
I'm exaggerating somewhat. But I'm familiar with Docker's multi-stage builds and how to attempt to optimize cache layers. The first problem that you run into, with ephemeral runners, is where the Docker cache is supposed to be downloaded from, and it's often not faster at all compared to re-downloading artifacts (network calls are network calls, and files are files after all). This is fundamentally different from per-language caching systems where libraries are known to be a dumb mirror of upstream, often hash-addressed for modern packaging, and thus are safe to share between builds, which means that it is safe to keep them on the CI runner and not be forced to download the cache for a build before starting it.

> without having to figure out a per-language caching systems

But most companies, even large ones, tend to standardize on no more than a handful of languages. Typescript, Python, Go, Java... I don't need something that'll handle caching for PHP or Erlang or Nix (not that you can really work easily with Nix inside a container...) or OCaml or Haskell... Yeah I do think there's a lot of room for companies to say, this is the standardized supported stack, and we put in some time to optimize the shit out of it because the DX dividends are incredible.
by kevindamm | 2025-12-13 21:16:13+00:00
I think that LLMs will be complemented best with a declarative language, as inserting new conditions/effects in them can be done without modifying much (if any!) of the existing code. Especially if the declarative language is a logic and/or constraint-based language.

We're still in early days with LLMs! I don't think we're anywhere near the global optimum yet.
by ebcode | 2025-12-13 21:17:15+00:00
> A 10% improvement every month gets to be a 10x improvement in (math...)

1.1^24=9.85, so yeah, if you could reliably get a 10% speed-up each month, you’d get to 10x in roughly 2 years. (But I’d expect the speed-up per month to be non-linear.)
by haunter | 2025-12-13 21:17:16+00:00
Next one to look out for: 2026 Hungary. Fidesz is basically a russian backdoor in the EU and they will do everything to stay in power.

https://telex.hu/english/2025/12/11/most-hungarians-fear-rus...

They are also doing everything to bypass the no-political-ads-on-facebook ban https://telex.hu/english/2025/10/29/despite-the-ban-fidesz-c...
by forgotpwd16 | 2025-12-13 21:18:14+00:00
Since although details given, it isn't explicitly stated, ELVM is an infrastructure with an 8cc front-end, a simple IR, and multiple target back-ends which, alongside others, include QFTASM, that article is about, brainfuck, and lambda / binary lambda calculus. Essentially you can write code in C and have it compiled to bunch of weird targets.

Mentioning the last one (same model, different encoding basically) because that guy (@woodrush*) also made a Lisp to λ-calculus expressions compiler which then used to make a Lisp interpreter expressed in λ-calculus (which can evaluate aforementioned compiler and also has an a λ-calculus interpreter implementation available**) and a VM for a Lisp/ELVM-like assembly. The λ ELVM backend was made possible integrating this VM in ELVM. And, of course using his own contributed backend, had an 8cc-based C compiler expressed in λ-calculus.

*If want a drink game to get drunk asap, "take a shot for every λ" in @woodrush Lambda projects is a strong option.

**For extra inception points, can use it to run 2012 Tromp's λ self-interpreter.
by dlubarov | 2025-12-13 21:18:16+00:00
Suppose we believe all captions in your links, so for example we'll assume that guy in shorts and flip flops was some sort of “spy balloon manager.”

It wouldn’t matter, because once you perform terrorist attacks, you’re still a terrorist even if you also attack valid targets sometimes. Same as Hamas, which is still a terrorist org despite attacking some IDF bases.

Even Amnesty has acknowledged Hezbollah’s routine use of unguided rockets, which can’t possibly target military assets but are just lobbed in the general direction of population centers. That makes them terrorists, regardless of what else they do.

https://www.amnesty.org/en/latest/news/2024/12/israel-hezbol...
by rssoconnor | 2025-12-13 21:19:23+00:00
Do not try this at home, but I replaced the lead acid battery in my UPS with a LFP battery. From what I read online, the charging curves for lead acid batteries and LFP batteries are very similar. The LFP batteries have a slightly higher charging voltage, so I expect my LFP battery to only charge upto about 80% capacity or so due to the charging voltage being slightly too low. I'm hoping the battery will last 10 years instead of 2 or 3 years.

Do not try this at home, as changing battery chemistry is quite ill advised.
by lawn | 2025-12-13 21:21:02+00:00
Rust has macros that make serde very convenient, which Gleam doesn't have.

Could you point to a solution that provides serde level of convenience?

Edit: The difference with generating code (like with Gleam) and having macros generate the code from a few tags is quite big. Small tweaks are immediately obvious in serde in Rust, but they drown in the noise in the complete serialization code like with the Gleam tools.
by dahart | 2025-12-13 21:21:18+00:00
Yes, training data is a plausible answer to your own question there, as well as mine above. And that explanation does not support your claims that AI is writing differently than humans, it only suggests training sets vary.

Repeating your thesis three times in slightly different words was taught in school. Using outline style and headings to make your points clear was taught in school. People have been writing like this for a long time.

If your argument depends on your subjective idea of “good writing”, that may explain why you think AI & blog styles are changing; they are changing. That still doesn’t suggest that LLMs veer from what they see.

All that aside, as other people have mentioned already, whether someone is using AI is irrelevant, and believing you can detect it and accusing people of using AI quickly becoming a lazy trope, and often incorrect to boot.
by kotaKat | 2025-12-13 21:21:31+00:00
Meanwhile I see the most bizarre changelogs that I don't understand why Apple approves.

https://apps.apple.com/us/app/chime-mobile-banking/id8362152...

"Choose your own update notes adventure! Pick only one: A, B, or C.

A. The holidays are coming up and we've been busy planning a celebration of bug bashes and performance enhancements, so get merry and smash that update button.

B. Shorter days, longer nights, colder temps. You know what helps the Winter blues?

Instant gratification. Tap update, watch that progress bar fill up, and feel the dopamine flow.

C. Whoever made up the mistletoe thing was crazy. You know what's not? Updating your app."

This... also serves no useful purpose.
by gtowey | 2025-12-13 21:22:27+00:00
It's because companies are no longer run by engineers. The MBAs and accountants are in charge and they could care less about making good products.

At Microsoft, Satya Nadella has an engineering background, but it seems like he didn't spend much time as an engineer before getting an MBA and playing the management advancement game.

Our industry isn't what it used to be and I'm not sure it ever could.
by ViewTrick1002 | 2025-12-13 21:22:38+00:00
The problem is that we can’t be wasting money and opportunity cost that could have larger impact decarbonizing agriculture, construction, aviation, maritime shipping etc on handouts from tax money to new built nuclear power.

As soon as zero fuel cost renewables enters the picture the mix of extremely high CAPEX and acceptable OPEX for new built nuclear makes it the worst companion imaginable.

The problem is that the setting nuclear power makes sense in is for the people living north of the arctic without abundant hydro or a transmission grid.

We’re now down to a handful communities in Russia, the US and Canada and Svalbard.

If these communities pertaining a few hundred thousand people keep running on fossil fuels while we achieve larger impact elsewhere that’s perfectly acceptable.
by foltik | 2025-12-13 21:22:40+00:00
No idea what this vibe code is doing, but two processes on the same machine can always share a mapping, though maybe your PL of choice is incapable. There aren’t many libraries that make it easy either. If it’s not two processes on the same machine I wouldn’t really call it IPC.

Of course a round trip will take more time, but it’s not meaningfully different from two one-way transfers. You can just multiply the numbers I said by two. Generally it’s better to organize a system as a pipeline if you can though, rather than ping ponging cache lines back and forth doing a bunch of RPC.
by machomaster | 2025-12-13 21:23:04+00:00
"Should be", "I think". Shouldn't you check the official rules first before writing opinions of how ought to be organized in your opinion?

The facts are:

1. The only EU-wide visa is 90/180. Citizens of UK don't need to apply for a separate visa.

2. Past the duration of 90 days, the matter goes to the national level. EU-wide long-term travel does not exist legally and this is done purposefully!

3. So the long stays require one country as your base. Long STAYS, not TRAVELS. Meaning that you get your official EU country of residence. Yes, you can travel to other EU countries, but outside travel still remain capped at 90/180, which is not useful in case of traveling through more than 2 countries.
by phrasecode | 2025-12-13 21:23:10+00:00
Author here — thanks for checking it out.

Short answer: the core LinkedQL live query engine runs on the backend today, and there’s an embeddable variant (FlashQL) that runs directly in the frontend with the same LinkedQL capabilities – live queries, DeepRefs, etc.

1. Pure frontend / local data

For data that can live entirely on the client, you can spin up an in-browser FlashQL instance:

const client = new FlashQL(); // runs in the page / worker

await client.query(` CREATE TABLE users ( id UUID PRIMARY KEY, name TEXT ) `);

// Live query works the same way as on the backend: const result = await client.query( 'SELECT * FROM users', { live: true } );

From there, result is a live result set: inserts/updates/deletes that match the query will show up in the rows, and all the same features (live queries, DeepRefs, etc.) behave as they do on a backend instance.

At the moment FlashQL is in-memory only; persistence backends like IndexedDB / LocalStorage are on the roadmap.

2. Remote database from the frontend

If your source of truth is a remote Postgres/MySQL instance, the model we’re building is:

a LinkedQL engine next to the database, and

a FlashQL instance in the frontend that federates/syncs with that backend engine.

That federation/sync path is in alpha right now (early docs here: https://linked-ql.netlify.app/flashql/foreign-io ), so today the “stable” story is:

run LinkedQL on the backend against Postgres/MySQL,

expose whatever API you like to the frontend,

and use FlashQL locally where a client-side store makes sense.

The goal is that the frontend doesn’t need a special framework — just a LinkedQL/FlashQL client wherever JavaScript runs.
by tlarkworthy | 2025-12-13 21:23:24+00:00
also after you have a to-and-fro to course correct it on a task, run this self-reflection prompt

https://gist.github.com/a-c-m/f4cead5ca125d2eaad073dfd71efbc...

That will moves stuff that required manually clarifying back into the claude.md (or a useful subset you pick). It does a much better job of authoring claude.md than I do.
by Noel04 | 2025-12-13 21:24:30+00:00
You’re absolutely right, SMS itself is commoditized, and there are many solid providers. Console.text() isn’t trying to compete as “yet another SMS API”. The focus is on developer ergonomics and intent, not transport: one-line, code-level alerts (console.text("error")) built for early-stage teams that don’t want to wire PagerDuty / Datadog yet
by Beijinger | 2025-12-13 21:24:42+00:00
Yes, I don't understand the advantage or disadvantage of this. Let's say I need a Colombian IP address, I would figure it out pretty quickly it this was not genuine, except if the geo-block protection would be fooled too.

Most of the "problem" countries are tiny places. Monaco, Andorra etc. It might be tough to rent a server there. And your list of clients should be minimal.
by tptacek | 2025-12-13 21:24:54+00:00
Another canard, unfortunately. "Segfault" is simply Go's reporting convention for things like nil pointer hits. "Segfaults" are not, in fact, part of the definition for memory safety or a threshold condition for it. All due respect to Ralf's Ramblings, but I'm going to rest my case with the Prossimo page on memorysafety.org that I just posted. This isn't a real debate.
by jsnell | 2025-12-13 21:25:04+00:00
The _Science_ paper linked is paywalled, is anyone aware of a preprint?

I find it a bit curious that they've chosen to use SMS verifications as a proxy for the difficulty of creating an account, when there are similar marketplaces for selling the actual end product of bulk-created accounts. Was there some issue with that kind of data? SMS verification is just one part of the anti-bulk account puzzle, for both the attacker and defender.
by ak217 | 2025-12-13 21:25:04+00:00
China is governed by the CCP, which holds the world record for the number of people murdered by the state, feeds its citizens militaristic propaganda at scale, is currently controlled by a guy who fancies himself a dictator, and is politically stable only as long as it continues to suppress free speech and free trade. It takes a dangerous kind of willful naivete to just ignore that fact.
by ok123456 | 2025-12-13 21:25:25+00:00
> Makes sense basically creating an easy to point out pattern for static analysis to find everything security related.

This is essentially already the case whenever you use encryption, because there are tell-tale signs you can detect (e.g., RSA S-Box). But this will make it even easier and also tip you off to critical sections that are sensitive yet don't involve encryption (e.g., secure strings).