MurphyA/hacker-news huggingface dataset:
by Expurple | 2025-07-23 08:45:40+00:00
Ok, I have thought more about the topic. I was too concerned with "theory" in the above comment. Disregard it.

Web engines are a huge practical example in favor of MPL/LGPL. They suggest that MPL/LGPL may indeed have the best survival characteristics.

Companies love proprietary browsers. If there were a good-enough permissive web engine, a proprietary fork would happen and "win", even if as "a set of patches" on top of a permissive base maintained by the community for free. Luckily, the creators of FOSS web engines seem to have understood that and chose MPL/LGPL. This goes against the article.

Companies love proprietary browsers. They will never contribute to a GPL web engine. That's why we don't have any good GPL web engines. This supports the article.

Companies love proprietary browsers. Microsoft was one of the first movers on the web. They had the chance to create a competitive proprietary web engine from scratch. It was popular for a few decades. But eventually Microsoft gave up and adopted Chromium instead. Presumably, to reduce maintenance costs. It doesn't seem like their proprietary engine gave them any competitive advantages that would be worth the cost. This supports the article.

So, the article is correct regarding GPL and proprietary, even (indirectly) predicting the continued absence of GPL web engines and the death of proprietary web engines. In 2015, when the article was written, IE was still bigger than Firefox and Safari on the desktop: https://en.wikipedia.org/wiki/Usage_share_of_web_browsers

But the article completely misses the huge success of MPL and LGPL. You are 100% correct.
Proof by Contrapositive Is Wrong
by slack3r | 2025-07-23 08:46:12+00:00
Proof by contrapositive is wrong. There is a true, false and undecidable case also.

Let me explain how it works.

p. =>. q. does not necessarily imply not q ==> not p. There are three cases here. If not q is true, then p can also be undecidable.
by m4thias | 2025-07-23 08:46:51+00:00
I shipped lot of new features and improvements to the RewriteBar app, which I want to share:

Review window improvements:

The review window opens now directly with streamed content similar to ChatGPT

You can switch between Provider and Models and rerun the execution

UI: You can switch between styled and unstyled text.

Improvements to the position and size of the review window, which are also configurable

Settings and configuration

You can now configure which languages are available for the translate action. So, you can choose from ~1,000 languages and their dialects. This means you can also translate from UK to US English.

You can also configure which tones are available for the change tone action.

You can also reorder the options so your most used languages appear at the top.

New layout for the settings window

Improved localizations: The app is now almost completely localized. The last missing parts are the command templates, which are still in English.

Better light theme support: loading indicator has now a darker color

let me know If you have any feature request :)

PS: Looking forward to provide Apple Intelligence when macOS 26 will be released.
by chartered_stack | 2025-07-23 08:47:05+00:00
> I hope these OSS CC clones converge at some point.

Imo, the point of custom CLIs is that each model is trained to handle tool calls differently. In my experience, the tool call performance is wildly different (although they have started converging recently). Convergence is meaningful only when the models and their performance are commoditized and we haven't reached that stage yet.
by PeterStuer | 2025-07-23 08:48:47+00:00
I had given up long time ago on self hosted transformer models for coding because the SOTA was definetly in favor of SaaS. This might just give me another try.

Would llama.cpp support multiple (rtx 3090, no nvlink hw bridge) GPUs over PCIe4? (Rest of the machine is 32 CPU cores, 256GB RAM)
by criticalfault | 2025-07-23 08:49:45+00:00
I've been reading about this for a while. Will it. Won't it.

Does anybody know why is it such a big problem to add dom access to wasm?

In worst case, we should have a second option to Js (which is not typescript - typescript is just a lipstick on a pig). If wasm is not it, why not something different? Having dart in would be great.
by rwmj | 2025-07-23 08:50:38+00:00
We must have the same job! Generating code is a miniscule part of my job. We have the same level of organizational disfunction. Mostly the work part involves long investigations of customer bugs and long face to face calls with customers - I'm only getting the stuff that stumped level 1 and level 2 support.

I actually tried to use Qwen3[1] to analyse customer cases and it was worse than useless at it.

[1] We can't use any online model as these bug reports contain large amounts of PII, customer data, etc.
by pjc50 | 2025-07-23 08:51:12+00:00
> If there is a single case of a harmful vaccine, or even a reasonable probability of one, then it isn't irrational to be cautious of vaccines

The problem is that humans are really unsuited to statistical thinking, especially about risk, and what it means to "be cautious" about something. In this context, "being cautious" about vaccines means "being reckless" about disease, because you're rejecting the mitigation measures. It is not a good bet to roll the dice for your children against measles.

We have to recognize that there have been both incidents of vaccine contamination and of individuals who have had unexpected negative reactions to vaccines. You get advised about this every time you have one!

Perhaps the diagrams should include "one sided scale" as an argument.
by fanwood | 2025-07-23 08:51:44+00:00
The Trump regime is the modern equivalent to the Nazi regime. Just because we don't get to see through the perspective of history doesn't mean it doesn't share all the same characteristics. The only difference with Nazi Germany is that the current democratic institutions in the United States are somewhat stronger than the ones in Germany in the 1930s, which prevent the Trump regime to gain full power. But they have been systematically eroded in the last few years (and especially in the last 6 months), and eventually they will fail too.
by flohofwoe | 2025-07-23 08:52:11+00:00
Tbh I would be surprised if converting between UTF-8 and JS strings is the performance bottleneck when calling into JS code snippets which manipulate the DOM.

In any case, I would probably define a system which doesn't simply map the DOM API (objects and properties) into a granular set of functions on the WASM side (e.g. granular setters and getters for each DOM object property).

Instead I'd move one level up and build a UI framework where the DOM is abstracted away (quite similar to all those JS frameworks), and where most of the actual DOM work happens in sufficiently "juicy" JS functions (e.g. not just one line of code to set a property).
by cadamsdotcom | 2025-07-23 08:53:31+00:00
There’s writings about the early days of electronics when wire-wrapped RAM wasn’t terribly reliable. Back then, debugging involved a multi-meter.

Of course since then we found ways to make chips so reliable that billions of connections don’t fail even after several years at a constant 60deg. Celsius.

You just have to understand that the “debugging with a multi-meter” era is where we are for this tech.
by happymellon | 2025-07-23 08:53:39+00:00
No its not regularly, I think just once in at least 10 years, probably longer. And it could easily be either a Spring bug, or bad configuration through misunderstanding.

My point was more that it can be opaque when it doesn't act as expected. Sometimes heap inspection is helpful, but if you use Kafka or Spring Data, etc, it can easily just appear to be a char or int array.
by panabee | 2025-07-23 08:54:46+00:00
This is long overdue for biomedicine.

Even Google DeepMind's relabeled MedQA dataset, created for MedGemini in 2024, has flaws.

Many healthcare datasets/benchmarks contain dirty data because accuracy incentives are absent and few annotators are qualified.

We had to pay Stanford MDs to annotate 900 new questions to evaluate frontier models and will release these as open source on Hugging Face for anyone to use. They cover VQA and specialties like neurology, pediatrics, and psychiatry.

If labs want early access, please reach out. (Info in profile.) We are finalizing the dataset format.

Unlike general LLMs, where noise is tolerable and sometimes even desirable, training on incorrect/outdated information may cause clinical errors, misfolded proteins, or drugs with off-target effects.

Complicating matters, shifting medical facts may invalidate training data and model knowledge. What was true last year may be false today. For instance, in April 2024 the U.S. Preventive Services Task Force reversed its longstanding advice and now urges biennial mammograms starting at age 40 -- down from the previous benchmark of 50 -- for average-risk women, citing rising breast-cancer incidence in younger patients.
by boomskats | 2025-07-23 08:55:32+00:00
> So on the one side you have organizations that definitely don't want to easily give network/filesystem/etc. access to code and on the other side you have people wanting it to be easier to get this access

I don't think this is entirely fair or accurate. This isn't how Wasm runtimes work. Making it possible for the sandbox to explicitly request specific resource access is not quite the same thing as what you're implying here.

> The browser is the main driving force for WASM, as I see it

This hasn't been the case for a while. In your first paragraph you yourself say that 'the people furthering WASM are [...] building a whole new VM ecosystem that the browser people aren't interested in' - if that's the case, how can the browser be the main driving force for Wasm? It's true, though, that there's verey little revenue in browser-based Wasm. There is revenue in enterprise compute.

> because outside of the browser the need for sandboxing is limited to plugins (where LUA often gets used) since otherwise you can run a binary or a docker container

Not exactly true when you consider that docker containers are orders of magnitude bigger, slower to mirror and start up, require architecture specific binaries, are not great at actually 'containing' fallout from insecure code, supply chain vulns, etc.. The potential benefits to enterprise orgs that ship thousands of multi-gig docker containers a week with microservices architectures that just run simple business logic, are very substantial. They just rarely make it to the hn frontpage, because they really are boring.

However, the Wasm push in enterprise compute is real, and the value is real. But you're right that the ecosystem and its sponsorship is still struggling - in some part due to lack of support for the component model by the browser people. The component model support introduced in go 1.25 has been huge though, at least for the (imho bigger) enterprise compute use case, and the upcoming update to the component model (wasi p3) should make a ton of this stuff way more usable. So it's a really interesting time for Wasm.
by senko | 2025-07-23 08:56:14+00:00
I vibecoded something similar for myself, transcribes and summarizes the content into article format: https://github.com/senko/scribe

Uses yt-dlp, whisper, and a LLM (Gemini hardcoded because it handles long contexts well, but easy to switch) for summarizer.

I dislike podcast as a format (S/N level way too low for my taste), so use this whenever I want to get a tldr of some episode.

I should check out the SOTA models and improve the summarization prompt, but aren't in a hurry as this works pretty well for my needs already.
by thefz | 2025-07-23 08:56:56+00:00
I wanted to test Gemini's code generation so I asked it for a bash script iterating through an array of directory names and executing a command for each one.

It got it wrong. The command was generated outside of the for, and never updated inside the loop effectively making it useless.

Luckily I know bash so I spotted it immediately. But I wonder how it's "removing programming language barriers" when one that does not know its output language can not spot even such a glaring issue.
by Paradigma11 | 2025-07-23 08:57:12+00:00
I used a LSP MCP tool for a LLM and was so far a bit underwhelmed. The problem is that LSP is designed for human consumption and LLMs have different constraints.

LLMs don't use the LSP exploratory to learn the API, you just give it to it as a context or MCP tool. LLMs are really good at pattern matching and wont make type errors as long as the type structure and constructs are simple.

If they are not simple it is not said that the LLM can solve and the user understand it.
by isaachinman | 2025-07-23 08:57:28+00:00
As others have mentioned, the search and overall performance of "legacy" products like Gmail and Apple Mail are absolutely terrible, not because those companies lack the technical capacity to improve them, but because they have very little financial incentive to do so.

We’re building an IMAP-native email client:

https://marcoapp.io

All metadata is stored locally on the client, so full-text searches complete in single-digit milliseconds.

Most people have simply grown accustomed to the insanely slow search speeds of traditional IMAP clients and don’t realise how bad they are until they try something faster.
Tell HN: Cloudflare is ignoring Abuse reports for domains using their registrar
by seasicksteve | 2025-07-23 08:57:48+00:00
Unfortunately it has come to posting publicly on HN hoping that @jgrahamc may be able to get someone involved.

Fraudsters have registered with Cloudflare a very similar domain to that of my company. The fraudsters website is pretending to be us using our trademarked branding and legal entity.

The address they are using is deceiving as it’s intentionally close to our real registered office, the address listed on the website is for an apartment building, there are no businesses there.

Calling the phone number on the fraudsters website claims to be a subsidiary of the United Nations, clearly malicious.

I have followed their guidelines for registrar abuse reports but receive no response other than an automated "we have received your report".

24 June 2025 – initial report via email to registrar-abuse@cloudflare.com

24 June 2025 – web submission via https://www.cloudflare.com/abuse/

2 July 2025 – follow-up request to abusereply@cloudflare.com (listed in the original automated response from the web submission)

18 July 2025 - follow-up request to abusereply@cloudflare.com, registrar-abuse@cloudflare.com, abuse+law@cloudflare.com, legal@cloudflare.com

If there is someone from Cloudflare reading this, the report ids are #19590367 and 419957ad84b52e85
by theptip | 2025-07-23 08:58:00+00:00
Things will be moving faster in 2-3 years most likely. (The recursive self-improvement flywheel is only just starting to pick up momentum, and we’ll have much more LLM inference compute available.)

Figuring out how to stay sane while staying abreast of developments will be a key skill to cultivate.

I’m pretty skeptical there will be a single model with a defensible moat TBH. Like cloud compute, there is both economy of scale and room for multiple vendors (not least because bigco’s want multiple competing bids).
by hiAndrewQuinn | 2025-07-23 08:58:34+00:00
Taken to its logical conclusion one could even argue that ending government backed retirement pensions entirely and letting people make their own decisions is the best idea.

Some people might plan to work until the day they drop, which is obviously a laudable goal. It's good to contribute to the economy.

Others may purchase an annuity for a target date years or decades in the future, which pay out in basically the same way as social security tends to.

Some (maybe most) would just save more for retirement, because they know if they don't no one will.

Realistically I suspect most people would hedge their bets dynamically go for a combination of these things. Which isn't all that different from the current system, where SS despite being over 20% of the federal budget is considered by most to be woefully inadequate even in the current day for a retirement plan.
by 1718627440 | 2025-07-23 09:00:25+00:00
You don't need to tag, you also just specify the commit SHA, isn't that the same in jj? It's just convenience.

The difference here seams to be that in jj you're always in a commit while in git you're always outside. But that's the difference between one and two commands.

Tags are hardly a new concept, if anything they are easier then a rebase. You can't really expect to use something with knowing the core concepts. Thats true for every tool and also for software. Can you use jj without knowing what a commit is?

I didn't knew about --detach before. It was obvious from the error and easily found using autocomplete. Also you only need it, if you want to change something under yourself while you're already modifying it.
by DonHopkins | 2025-07-23 09:01:41+00:00
Unless I'm mistaken, the transformer architecture isn't your invention either, yet you claim to understand it better than Geoffrey Hinton.

Did you invent the transformer architecture yourself, and I am mistaken to guess that you probably understand it less than Geoffrey Hinton does?

I'll venture a wild guess that you probably haven't been working in the field as long as he has, and you don't personally know as many people in the field as he does, huh?

Or is my presumptuous chain of logic just a random thoughtless unconscious probabilistic stream of tokens that has nothing to do with reality, and I don't realize I'm speaking to Ashish Vaswani himself?

Then why don't you use your real name as you HN handle, are you really that modest, Ashish? And don't you have better things to do than posting to Hacker News? If you really wanted to win an argument from authority, you could at least post under your real name, Mr. Vaswani.
by flohofwoe | 2025-07-23 09:01:47+00:00
> that they are content with WASM being a second class citizen in the web world

Tbh, most of the ideas so far to enable more direct access of Javascript APIs from WASM have a good chance of ruining WASM with pointless complexity.

Keeping those two worlds separate, but making sure that 'raw' calls between WASM and JS are as fast as they can be (which they are) is really the best longterm solution.

I think what people need to understand is that the idea of having 'pure' WASM browser applications which don't involve a single line of Javascript is a pipe dream. There will always be some sort of JS glue code, it might be generated and you don't need to directly deal with it, but it will still be there, and that's simply because web APIs are first and foremost designed for usage from Javascript.

Some web APIs have started to 'appease' WASM more by adding 'garbage free' function overloads, which IMHO is a good thing because it may help to reduce overhead on the JS side, but this takes time and effort to be implemented in all browser (and most importantly, a will by mostly "JS-centric" web people to add such helper functions which mostly only benefit WASM).
by vintermann | 2025-07-23 09:01:48+00:00
YSEQ is a German mom and pop lab which does next generation sequencing for genealogists. It has rather little utility for genealogists, but some people are really into figuring out their place in the great Y chromosome haplotree, so apparently there is a market. Family Tree DNA also does some next generation sequencing, of the Y chromosome and mitochondria only - they have bigger trees than YSEQ, but YSEQ I believe gives you the option to get even more resolution on the Y chromosome.

YSEQ will do full genome NGS if you ask for it but it's expensive, can take six months or more, and the owners have apparently been known to cancel your order and refund you if you complain about the wait times.
by philipallstar | 2025-07-23 09:01:52+00:00
> That process is well on its way to completion.

That's not bombing. Bombing is generally from the air. I mean they went house to house and tried to clear things out and airdropped warnings at much greater risk to personnel than bombing. To minimise civilian casualties. Now the reality of that is painful still, because war is painful, but their strategy clearly wasn't just to level Gaza or they'd have never done it this way.

> Both should make you angry.

So don't bring the other thing up when I mention the first thing. You address the first thing instead of this whataboutism.

> More skeptical?

The pro-Palestinian take is the most credulous one, most likely to be adopted by children and young adults. I'm not saying it's wrong for that reason, but you absolutely need to be a sceptic to even consider Israel's position at all.
by hommes-r | 2025-07-23 09:02:16+00:00
Here I feel that having the right tools is going to prevent this kind of drift from happening.

Double entry bookkeeping to make sure the mutations are sound and solving the floating point error by this simple trick: https://news.ycombinator.com/item?id=21687430.

All major fintech's use these two tricks to prevent them from fundamentally screwing up. Believe me I worked at a really big one ;)
by pyman | 2025-07-23 09:02:43+00:00
This is what software engineers need to be more productive:

- Agentic DevOps: provisions infra and solves platform issues as soon as a support ticket is created.

- Agentic Technical Writer: one GenAI agent writes the docs and keeps the wiki up to date, while another 100 agents review it all and flag hallucinations.

- Agentic Manager: attends meetings, parses emails and logs 24x7 and creates daily reports, shares these reports with other teams, and manages the calendar of the developers to shield them from distractions.

- Agentic Director: spots patterns in the data and approves things faster, without the fear of getting fired.

- Agentic CEO: helps with decision-making, gives motivational speeches, and aligns vision with strategy.

- Agentic Pet: a virtual mascot you have to feed four times a day, Monday to Friday, from your office's IP address. Miss a meal and it dies, and HR gets notified. (This was my boss's idea)
by oblio | 2025-07-23 09:04:15+00:00
Can't these hyper-advanced-super-duper tools discover what UNIX tools since circa 1970 knew, and just have a flag/configuration setting pointing them to the config file location? Excuse me if they already do :-)

In which case you'd have 1 markdown file and at least for the ones that are invoked via the CLI, just set up a Makefile entry point that leads them to the correct location.
by madaxe_again | 2025-07-23 09:04:37+00:00
No, on the fact that there are plenty of known variants which increase the chance of lung cancer quite dramatically - moreso than smoking.

It’s not just lungs - things like FAP make your chance of getting colon cancer in your lifetime near to 100%, regardless of how many ginseng enemas you have or whatever the hell else you do.

Variants like TP53 (Li-Fraumeni) or EGFR mutations have measurable, population-level impacts on cancer risk.

Genetics loads the gun. Being alive then pulls the trigger.
by lan321 | 2025-07-23 09:05:13+00:00
Has anyone ever made a language or extended a language with serious issue tracking? I can definitely imagine a system where every folder and file can have a paired ticket file where past, future and current tasks are tracked. Theoretically, it could even bind to a source management extension for the past ones. It won't ever be as powerful and manager-friendly as JIRA, but it would be good enough for many projects.
by anthk | 2025-07-23 09:05:42+00:00
Org-Mode with Hyperbole it's like doing computing in 2070, but without bullshit AI LLM's. Try it and you'll understand.

https://www.youtube.com/watch?v=cFdgpb0TeQo

If you are a Lisp programmer, you can OFC use ob-lisp with it (and maybe there's ob-elisp to learn Elisp in a literate way).

This is like a Jupyter netbook, with steroids. Org Babel:

https://orgmode.org/worg/org-contrib/babel/

Supported languages:

https://orgmode.org/worg/org-contrib/babel/languages/index.h...