🚀 DeepSeek-V4 Preview is of­fi­cially live & open-sourced! Welcome to the era of cost-ef­fec­tive 1M con­text length.

🔹 DeepSeek-V4-Pro: 1.6T to­tal / 49B ac­tive params. Performance ri­val­ing the world’s top closed-source mod­els.

🔹 DeepSeek-V4-Flash: 284B to­tal / 13B ac­tive params. Your fast, ef­fi­cient, and eco­nom­i­cal choice.

Try it now at chat.deepseek.com via Expert Mode / Instant Mode. API is up­dated & avail­able to­day!

📄 Tech Report: https://​hug­ging­face.co/​deepseek-ai/​DeepSeek-V4-Pro/​blob/​main/​DeepSeek_V4.pdf

🤗 Open Weights: https://​hug­ging­face.co/​col­lec­tions/​deepseek-ai/​deepseek-v4

DeepSeek-V4-Pro​

🔹 Enhanced Agentic Capabilities: Open-source SOTA in Agentic Coding bench­marks.

🔹 Rich World Knowledge: Leads all cur­rent open mod­els, trail­ing only Gemini-3.1-Pro.

🔹 World-Class Reasoning: Beats all cur­rent open mod­els in Math/STEM/Coding, ri­val­ing top closed-source mod­els.

DeepSeek-V4-Flash​

🔹 Reasoning ca­pa­bil­i­ties closely ap­proach V4-Pro.

🔹 Performs on par with V4-Pro on sim­ple Agent tasks.

🔹 Smaller pa­ra­me­ter size, faster re­sponse times, and highly cost-ef­fec­tive API pric­ing.

Structural Innovation & Ultra-High Context Efficiency​

🔹 Novel Attention: Token-wise com­pres­sion + DSA (DeepSeek Sparse Attention).

🔹 Peak Efficiency: World-leading long con­text with dras­ti­cally re­duced com­pute & mem­ory costs.

🔹 1M Standard: 1M con­text is now the de­fault across all of­fi­cial DeepSeek ser­vices.

Dedicated Optimizations for Agent Capabilities​

🔹 DeepSeek-V4 is seam­lessly in­te­grated with lead­ing AI agents like Claude Code, OpenClaw & OpenCode.

🔹 Already dri­ving our in-house agen­tic cod­ing at DeepSeek.

The fig­ure be­low show­cases a sam­ple PDF gen­er­ated by DeepSeek-V4-Pro.

API is Available Today!​

🔹 Keep base_url, just up­date model to deepseek-v4-pro or deepseek-v4-flash.

🔹 Supports OpenAI ChatCompletions & Anthropic APIs.

🔹 Both mod­els sup­port 1M con­text & dual modes (Thinking / Non-Thinking): https://​api-docs.deepseek.com/​guides/​think­ing_­mode

⚠️ Note: deepseek-chat & deepseek-rea­soner will be fully re­tired and in­ac­ces­si­ble af­ter Jul 24th, 2026, 15:59 (UTC Time). (Currently rout­ing to deepseek-v4-flash non-think­ing/​think­ing).

🔹 Amid re­cent at­ten­tion, a quick re­minder: please rely only on our of­fi­cial ac­counts for DeepSeek news. Statements from other chan­nels do not re­flect our views.

🔹 Thank you for your con­tin­ued trust. We re­main com­mit­ted to longter­mism, ad­vanc­ing steadily to­ward our ul­ti­mate goal of AGI.

Prefix Note

As this post is gain­ing more at­ten­tion than ex­pected on HN, I want to make some things clear - al­though I thought they are ob­vi­ous.

It sounds like a rant about Claude’s qual­ity in gen­eral - if you don’t read to the end. But my con­cerns are more fo­cused on the sup­port per­for­mance and to­ken is­sues - fully aware of the chal­lenges a com­pany this size faces and as­sum­ing the peo­ple at Anthropic are work­ing hard to make things bet­ter. I am point­ing at some “bad de­sign de­ci­sions” they prob­a­bly made. The “quality is­sues” are just the cherry on top of the cake.

After all, Claude Code is de­liv­er­ing and I use it to build stuff. Still, I ex­pe­ri­enced a degra­da­tion in qual­ity. It just takes longer. Which is a rel­a­tive ob­ser­va­tion. However I know that this is highly sub­jec­tive, too. That’s what that com­ment in a para­graph means: “The fail­ure usu­ally ap­pears in front of the screen”. Of course the agent is only as good as the op­er­a­tor and their in­struc­tions.

I am cod­ing for a cou­ple of decades now, I like to get my hands dirty. Three years ago I im­ple­mented AI into my work­flow. It started with code com­ple­tion and now I am at the point where I barely write code. For me “software en­gi­neeer­ing” is not con­sti­tuted by the sim­ple act of writ­ing code. It’s about con­duct­ing tools, be­ing cre­ative, un­der­stand­ing the prob­lem and de­liv­er­ing a so­lu­tion. Still - and that what this com­ment in an­other para­graph means: “While I was brows­ing the mod­el’s think­ing log - which I strongly sug­gest do­ing not only oc­ca­sion­ally” - I am es­cort­ing the agent while it’s work­ing. I still have to fig­ure out a con­cept, think about a data model and ver­ify it’s im­ple­men­ta­tion. That’s what soft­ware en­gi­neer­ing is about. It’s not n LOC…

Having said that - en­joy this post and stay happy, fel­low de­vel­op­ers.

First en­thu­si­asm

A cou­ple of weeks ago I sub­scribed to Claude Code, and dur­ing the first few weeks I had a re­ally nice ex­pe­ri­ence. It was fast, the to­ken al­lowance was fair, and the qual­ity was good.

I learned they had

raised the to­ken al­lowance for non-rush hours

, and since they op­posed some gov­ern­men­tal rules, it felt good to sup­port the right cause.

(づ ￣ ³￣)づ

However… for about three weeks now my ini­tial en­thu­si­asm has been rapidly wan­ing.

It be­gan with an is­sue three weeks ago. I started work­ing in the morn­ing af­ter about a ten-hour break; enough time for my to­kens to re­fresh.

I sent two small ques­tions to Claude Haiku. They were sim­ple ques­tions, not even re­lated to the repos­i­tory.

Suddenly, to­ken us­age spiked to 100%.

Have a nice break…

I con­tacted their “AI sup­port bot”, which re­turned some de­fault sup­port non­sense and did­n’t re­ally un­der­stand the prob­lem. So I asked for hu­man sup­port. A cou­ple of days later a - what ap­peared to be - hu­man sup­port per­son sent a re­ply. It be­gan like this:

“Our sys­tems are de­tect­ing your in­quiry is re­gard­ing us­age lim­its on your Pro or Max plan.”

Yeah, well — it’s the Pro plan. Seems like your sys­tems weren’t ac­tu­ally queried; it was just a de­fault in­tro and prob­a­bly a de­fault an­swer, be­cause:

This was fol­lowed by an ex­ten­sive what seems to be copy-and-paste an­swer from their docs ex­plain­ing how daily and weekly lim­its work.

And it closed with the typ­i­cally frus­trat­ing line, that no cus­tomer likes to read at the end of an e-mail and which is just the clas­si­cal mid­dle-fin­ger of cus­tomer sup­port - we don’t care if your prob­lem is solved or not, we de­clared it closed.

“Note that fur­ther replies to this ticket may not be mon­i­tored. If your re­quest is not re­gard­ing us­age lim­its on your Pro or Max plan, or you need ad­di­tional sup­port, please visit our help page at”

Great! Sending an au­to­mated e-mail that does not re­fer to the ac­tual prob­lem and then clos­ing the chan­nel. Thanks for noth­ing, I guess? Or was I wrong. I asked Claude Haiku:

@Haiku:

See the cus­tomer’s re­quest here and the re­sponse from the AI and later W***** - did they an­swer the con­cern/​ques­tion of the cus­tomer?

See the cus­tomer’s re­quest here and the re­sponse from the AI and later W***** - did they an­swer the con­cern/​ques­tion of the cus­tomer?

(╯°_°）╯︵ ┻━┻

Declining qual­ity

In the fol­low­ing days and weeks, the qual­ity was far from sat­is­fy­ing my needs or match­ing my ini­tial ex­pe­ri­ence. While I used to be able to work on up to three pro­jects at once, now the to­ken limit was ex­hausted af­ter two hours on a sin­gle pro­ject.

And the qual­ity was de­grad­ing. I am fully aware this is quite sub­jec­tive and that the qual­ity of the agent is al­ways heav­ily im­pacted by the op­er­a­tor. The fail­ure usu­ally ap­pears in front of the screen. But hey, I also de­velop us­ing Github’s Copilot, OpenAI’s Codex and I am run­ning my own in­fer­ence with OMLX and Continue us­ing Qwen3.5 – 9B. I’m not the ex­pert, I’m lazy some­times but I prob­a­bly know a thing or two.

Let me give you this won­der­ful ex­am­ple: yes­ter­day I asked Claude Opus to refac­tor a pro­ject.

While I was brows­ing the mod­el’s think­ing log - which I strongly sug­gest do­ing not only oc­ca­sion­ally - I found this:

Rather than edit­ing every slider in JSX, I’ll add a generic ini­tial­izer in ui-events.js that auto-in­jects value dis­plays for all range in­puts that lack one.

Rather than edit­ing every slider in JSX, I’ll add a generic ini­tial­izer in ui-events.js that auto-in­jects value dis­plays for all range in­puts that lack one.

This is clearly bad prac­tice. It’s a cheap workaround you would­n’t ex­pect even from a ju­nior dev; it reads like some­one who just does­n’t want to de­liver a good re­sult. My re­sponse:

“you can’t be se­ri­ous — is this how you fix things? just WORKAROUNDS????”

At least Opus ad­mit­ted:

“You’re right, that was lazy. Let me do it prop­erly — add the la­bels di­rectly in the JSX and wire them ex­plic­itly.”

Needless to say, this short­cut cost me around 50% of my five-hour to­ken al­lowance.

(ง •̀_•́)ง

And even more…

Now this cache topic comes up

-

among oth­ers

. at least they are talk­ing about it openly. The prob­lem was: when you get back to work af­ter some time, your con­ver­sa­tion cache is gone and the model starts read­ing your code­base again. Cost-wise this is smart. But ex­pe­ri­ence-wise? It means you paid to­kens for the ini­tial load and, af­ter a forced break be­cause the five-hour to­ken win­dow hit its limit, you pay again for the same load.

Think that’s all? Wait, I also got this funny anec­dote: all of a sud­den the weekly win­dow changed from to­day to Monday. OK, I was thank­ful be­cause it came with a re­set to zero. But still: what is go­ing on, Anthropic? Not only that — while I was work­ing on my pro­ject, watch­ing to­ken us­age with Argus-eyed vig­i­lance, this lit­tle warn­ing popped up:

Wait, what? I’m nei­ther part of an or­ga­ni­za­tion nor do I see any hint why I sud­denly have to worry about a “monthly us­age limit” — also the hourly and weekly lim­its were still not ex­ceeded. What is hap­pen­ing right now?

Turns out — two hours later - it al­lowed me to con­tinue work­ing. The warn­ing was gone.

At least

this doc­u­men­ta­tion

does not men­tion a monthly us­age limit. And the set­tings page only lists the lim­its for the cur­rent ses­sion and week.

So… what is this monthly limit all about, Anthropic?

Sorry to let you down, Anthropic

I am a huge fan of the prod­uct. Theoretically every­thing just works like a charm; it of­fers so many op­por­tu­ni­ties. I built my

Please make sure your browser sup­ports JavaScript and cook­ies and that you are not block­ing them from load­ing. For more in­for­ma­tion you can re­view our Terms of Service and Cookie Policy.

Hi friends,

I’ll be at­tend­ing Babashka Conf on May 8 and Dutch Clojure Days on May 9.

If you’re at­tend­ing ei­ther (or just vis­it­ing Amsterdam), drop me a line!

When I have an idea for a pro­ject, it tends to go in one of these two di­rec­tions:

I just do it. Maybe I make a few mi­nor re­vi­sions, but of­ten it turns out ex­actly how I’d imag­ined and I’m happy.

I just do it. Maybe I make a few mi­nor re­vi­sions, but of­ten it turns out ex­actly how I’d imag­ined and I’m happy.

I think, “I should look for prior art”. There’s a lot of prior art, deal­ing with a much broader scope than I’d orig­i­nally imag­ined. I start to won­der if I should in­cor­po­rate that scope. Or per­haps try to build my thing on top of the ex­ist­ing sorta-nearby-so­lu­tions. Or maybe I should just use the pop­u­lar thing. Although I could do a bet­ter job than that thing, if I put a bunch of time into it. But ac­tu­ally, I don’t want to main­tain a big pop­u­lar pro­ject, nor do I want to put that much time into this pro­ject. Uh oh, now I’ve spent a bunch of time, hav­ing nei­ther ad­dressed the orig­i­nal is­sue nor ex­pe­ri­enced the joy of cre­at­ing some­thing.

I think, “I should look for prior art”. There’s a lot of prior art, deal­ing with a much broader scope than I’d orig­i­nally imag­ined. I start to won­der if I should in­cor­po­rate that scope. Or per­haps try to build my thing on top of the ex­ist­ing sorta-nearby-so­lu­tions. Or maybe I should just use the pop­u­lar thing. Although I could do a bet­ter job than that thing, if I put a bunch of time into it. But ac­tu­ally, I don’t want to main­tain a big pop­u­lar pro­ject, nor do I want to put that much time into this pro­ject. Uh oh, now I’ve spent a bunch of time, hav­ing nei­ther ad­dressed the orig­i­nal is­sue nor ex­pe­ri­enced the joy of cre­at­ing some­thing.

I pre­fer the first out­come, and I think the piv­otal fac­tor is how well I’ve in­ter­nal­ized my own suc­cess cri­te­ria.

For ex­am­ple, last week­end I hosted my friend Marcin and we de­cided it’d be fun to do some wood­work­ing, so we threw to­gether this shelf and 3d-printed hang­ers for my kitchen:

Absolute banger of a pro­ject:

brain­stormed the de­sign over cof­fee

did a few 3d-print it­er­a­tions for the Ikea bin hang­ers (OnShape CAD, if you want to print your own)

used ma­te­r­ial left­over from my work­bench

rounded the cor­ner by eye with a palm sander

sealed the raw ply­wood edge with some left­over paint from a friend

done in a week­end

The main suc­cess cri­te­ria was to jam on wood­work­ing with a friend, and that helped me not over­think the ob­ject-level suc­cess cri­te­ria: Just make a shelf for my ex­act kitchen!

In con­trast, this past Friday I no­ticed diff­tas­tic did a poor job, so I de­cided to shop around for struc­tural/​se­man­tic diff tools and re­lated work­flows (a topic I’ve never stud­ied, that I’m in­creas­ingly in­ter­ested in as I’m re­view­ing more and more LLM-generated code).

I spent 4 hours over the week­end re­search­ing ex­ist­ing tools (see my notes be­low), go­ing through dark pe­ri­ods of both “semantic tree diff­ing is a PhD-level com­plex prob­lem” and “why do all of these have MCP servers? I don’t want an MCP server”, be­fore I came to my senses and re­mem­bered my orig­i­nal suc­cess cri­te­ria: I just want a nicer diff­ing work­flow for my­self in Emacs, I should just build it my­self — should take about 4 hours.

I’m cau­tiously op­ti­mistic that, hav­ing had this re­al­iza­tion and com­mit­ting my­self to a min­i­mal scope, I’ll be able to knock out a pro­to­type be­fore run­ning out of mo­ti­va­tion.

However, other long-run­ning in­ter­ests of mine:

in­ter­faces for pro­to­typ­ing hard­ware (discussed September 2023)

a pro­gram­ming lan­guage that fuses what I like about Clojure and Rust (November 2023)

a pro­gram­ming lan­guage for CAD (constraints, bidi­rec­tional edit­ing, other du­bi­ous ideas)

seem to be deep in the well of out­come #2.

That is, I’ve spent hun­dreds of hours on back­ground re­search and lit­tle pro­to­types, but haven’t yet syn­the­sized any­thing that ad­dresses the orig­i­nal mo­ti­vat­ing is­sue.

It’s not quite that I re­gret that time — I do love learn­ing by read­ing — but I have a nag­ging sense of un­ease that my in­ner critic (fear of fail­ure?) is si­lenc­ing my gen­er­a­tive ten­den­cies, keep­ing me from the much more en­joy­able (and pro­duc­tive!) learn­ing by do­ing.

I think in these cases the suc­cess cri­te­ria has been much fuzzier: Am I try­ing to re­place my own us­age of Rust/Clojure?

Only for some sub­set of prob­lems?

Or is it that I ac­tu­ally just need a play­ground to learn about lan­guage de­sign/​im­ple­men­ta­tion, and it’s fine if I don’t end up us­ing it?

Ditto for CAD: Am I try­ing to re­place my com­mer­cial CAD tool in fa­vor of my own?

Only for some sub­set of sim­ple or par­tic­u­larly para­met­ric parts?

Do I care if it’s use­ful for oth­ers?

Does my tool need to be leg­i­bly dif­fer­ent from ex­ist­ing open-source tools?

It’s worth con­sid­er­ing these ques­tions, sure.

But at the end of the day, I’d much rather have done a lot than have only con­sid­ered a lot.

So I’m try­ing to em­brace my in­ner clue­less 20-year-old and just do things — even if some turn out to be “obviously bad” in hind­sight, I’ll still be com­ing out ahead on net =D

Conservation of scope creep

Of course, there’s only so much time to “just do things”, and there’s a bal­ance to be had. I’m not sure how many times I’ll re-learn YAGNI (“you ain’t gonna need it”) in my ca­reer, but I was re­minded of it again af­ter writ­ing a bunch of code with an LLM agent, then even­tu­ally com­ing to my senses and throw­ing it all out.

I wanted a Finda-style filesys­tem-wide fuzzy path search for Emacs.

Since I’ve built (by hand, typ­ing the code my­self!) this ex­act func­tion­al­ity be­fore (walk filesys­tem to col­lect paths, in­dex them by tri­gram, do fast fuzzy queries via bitmap in­ter­sec­tions), I fig­ured it’d only take a few hours to su­per­vise an LLM to write all the code.

I started with a “plan mode” chat, and the LLM sug­gested a li­brary, Nucleo, which turned up since I wrote Finda (10 years ago, eek!).

I read through it, found it quite well-de­signed and doc­u­mented, and de­cided to use it so I’d get its smart case and Unicode nor­mal­iza­tion func­tion­al­ity.

(E.g., query foo matches Foo and foo, whereas query Foo won’t match foo; sim­i­larly for cafe and café.)

Finding a great li­brary was­n’t the prob­lem, the prob­lem was that Nucleo also sup­ported some ex­tra func­tion­al­ity: an­chors (^foo only matches at the be­gin­ning of a line).

This got me think­ing about what that might mean in a cor­pus that con­sists en­tirely of file paths.

Anchoring to the be­gin­ning of a line is­n’t use­ful (everything starts with /), so I de­cided to try and in­ter­pret the an­chors with re­spect to the path seg­ments.

E.g., ^foo would match /root/foobar/ but not /root/barfoo/.

But to do this ef­fi­ciently, the in­dex needs to keep track of seg­ment bound­aries so that the query can be checked against each seg­ment quickly.

But then we also need to han­dle a slash oc­cur­ring in an an­chored query (e.g., ^foo/bar) since that would­n’t get matched when only look­ing at seg­ments in­di­vid­u­ally (root, foo, bar, and baz of a match­ing path /root/foo/bar/baz/).

Working through this took sev­eral hours: first throw­ing around de­sign ideas with an LLM, hav­ing it write code to wrap Nucleo’s types, then re­al­iz­ing its code was bloated and did­n’t spark joy, so fi­nally writ­ing my own (smaller) wrap­per.

Then, af­ter a break, I re­al­ized:

I can’t think of a sit­u­a­tion where I’d ever wished Finda had an­chor func­tion­al­ity

In a cor­pus of paths, I can an­chor by just adding / to the start or end of a query (this works for every­thing ex­cept an­chor­ing to the end of a file­name).

So I tossed all of the an­chor­ing code.

I’m pretty sure I still came out ahead com­pared to if I’d tried to write every­thing my­self sans LLM or dis­cus­sion with oth­ers, but I’m not cer­tain.

Perhaps there’s some kind of con­ser­va­tion law here: Any in­creases in pro­gram­ming speed will be off­set by a cor­re­spond­ing in­crease in un­nec­es­sary fea­tures, rab­bit holes, and di­ver­sions.

Structural diff­ing

Speaking of un­nec­es­sary di­ver­sions, let me tell you every­thing I’ve learned about struc­tural diff­ing re­cently — if you have thoughts/​feel­ings/​ref­er­ences in this space, I’d love to hear about ’em!

When we’re talk­ing about code, a “diff” usu­ally means a sum­mary of the line-by-line changes be­tween two ver­sions of a file.

This might be ren­dered as a “unified” view, where changed lines are pre­fixed with + or - to in­di­cate whether they’re ad­di­tions or dele­tions.

For ex­am­ple:

We’ve re­moved cof­fee and added ap­ple.

The same diff might also be ren­dered in a side-by-side view, which can be eas­ier to read when there are more com­plex changes:

The prob­lem with these line-by-line diffs is that they’re not aware of higher-level struc­ture like func­tions, types, etc. — if some braces match up some­how be­tween ver­sions, they might not be shown at all, even if the braces “belong” to dif­fer­ent func­tions.

There’s a won­der­ful tool, diff­tas­tic, which tries to ad­dress this by cal­cu­lat­ing diffs us­ing treesit­ter-pro­vided con­crete syn­tax trees.

It’s a huge im­prove­ment over line-based diffs, but un­for­tu­nately it does­n’t al­ways do a great job match­ing en­ti­ties be­tween ver­sions.

Here’s the diff that mo­ti­vated this en­tire foray:

Note that it does­n’t match up struct PendingClick, it shows it deleted on the left and added on the right.

I haven’t dug into why diff­tas­tic fails to match here, but I do feel like it’s wrong — even if the over­all diff would be longer, I’d still rather see PendingClickRequest and PendingClick matched up be­tween both sides.

Here’s a sum­mary of tools / ref­er­ences in the space:

The most “baked” and thought­ful se­man­tic diff tool I found is, per­haps un­sur­pris­ingly, se­man­ticd­iff.com, a small German com­pany with a free VSCode plu­gin and web app that shows diffs for github PRs. Unfortunately they don’t have any code li­braries I can use as a foun­da­tion for the work­flow I want.

this se­man­ticd­iff vs. diff­tas­tic blog post cov­ers a lot of great de­tails (including that diff­tas­tic does­n’t even show se­man­ti­cally mean­ing­ful in­den­ta­tion changes in python !!!)

one of the au­thors has great HN com­ments with hard-won back­ground knowl­edge. E.g., they moved away from treesit­ter be­cause it’s un­re­li­able for se­man­tics:

Context-sensitive key­words in par­tic­u­lar were a con­stant source of an­noy­ance. The gram­mar looks cor­rect, but it will fail to parse be­cause of the way the lexer works. You don’t want your tool to abort just be­cause some­one named their pa­ra­me­ter “async”.

The most “baked” and thought­ful se­man­tic diff tool I found is, per­haps un­sur­pris­ingly, se­man­ticd­iff.com, a small German com­pany with a free VSCode plu­gin and web app that shows diffs for github PRs. Unfortunately they don’t have any code li­braries I can use as a foun­da­tion for the work­flow I want.

this se­man­ticd­iff vs. diff­tas­tic blog post cov­ers a lot of great de­tails (including that diff­tas­tic does­n’t even show se­man­ti­cally mean­ing­ful in­den­ta­tion changes in python !!!)

one of the au­thors has great HN com­ments with hard-won back­ground knowl­edge. E.g., they moved away from treesit­ter be­cause it’s un­re­li­able for se­man­tics:

Context-sensitive key­words in par­tic­u­lar were a con­stant source of an­noy­ance. The gram­mar looks cor­rect, but it will fail to parse be­cause of the way the lexer works. You don’t want your tool to abort just be­cause some­one named their pa­ra­me­ter “async”.

Context-sensitive key­words in par­tic­u­lar were a con­stant source of an­noy­ance. The gram­mar looks cor­rect, but it will fail to parse be­cause of the way the lexer works. You don’t want your tool to abort just be­cause some­one named their pa­ra­me­ter “async”.

diff­sit­ter

built on treesit­ter, has MCP server. README in­cludes list of sim­i­lar pro­jects.

lots of github stars, but does­n’t seem par­tic­u­larly well-doc­u­mented; I could­n’t find an ex­pla­na­tion of how it works, but the diff­tas­tic wiki says it “runs longest-com­mon-sub­se­quence on the leaves of the tree”

diff­sit­ter

built on treesit­ter, has MCP server. README in­cludes list of sim­i­lar pro­jects.

lots of github stars, but does­n’t seem par­tic­u­larly well-doc­u­mented; I could­n’t find an ex­pla­na­tion of how it works, but the diff­tas­tic wiki says it “runs longest-com­mon-sub­se­quence on the leaves of the tree”

gumtree

re­search / aca­d­e­mic ori­gin in 2014

re­quires Java, so no-go for my use case of a quick tool I can use via Emacs

gumtree

re­search / aca­d­e­mic ori­gin in 2014

re­quires Java, so no-go for my use case of a quick tool I can use via Emacs

mer­gi­raf: treesit­ter-based merge-dri­ver writ­ten in rust

very nice ar­chi­tec­ture overview; tool uses Gumtree al­go­rithm

docs and adorable il­lus­tra­tions in­di­cate this pro­ject was clearly writ­ten by a thought­ful hu­man

se­man­ticd­iff.com au­thor in HN com­ments:

> GumTree is good at re­turn­ing a re­sult quickly, but there are quite a few cases where it al­ways re­turned bad matches for us, no mat­ter how many fol­low-up pa­pers with im­prove­ments we tried to im­ple­ment. In the end we switched over to a dijk­stra based ap­proach that tries to min­i­mize the cost of the map­ping

mer­gi­raf: treesit­ter-based merge-dri­ver writ­ten in rust

very nice ar­chi­tec­ture overview; tool uses Gumtree al­go­rithm

Please make sure your browser sup­ports JavaScript and cook­ies and that you are not block­ing them from load­ing. For more in­for­ma­tion you can re­view our Terms of Service and Cookie Policy.

For years, the best way to get 10 gi­ga­bit net­work­ing on lap­tops was to buy an ex­pen­sive, large, and hot 10 GbE Thunderbolt adapter. With new RTL8159-based 10G USB 3.2 adapters com­ing onto the mar­ket, the bulky adapters might be a thing of the past. Just look at the size of the thing in com­par­i­son to my Thunderbolt adapters:

2.5G and even 5G USB adapters have been out for a while, but some­times you need more band­width.

The 10G adapter I’m test­ing is this $80 model from WisdPi. That’s dou­ble the price of most 5G/2.5G adapters, but less than half what I paid for my Thunderbolt 10G adapters.

If you need 10 gigs, this might be the best op­tion, if you use RJ45 and not SFP+. If you don’t need 10 gigs, a 2.5 or 5 Gbps adapter is still the best value.

Also, you might not even get 10 Gbps with these new adapters, de­pend­ing on your com­puter. I’ll sum­ma­rize why af­ter the video:

USB is fast frus­trat­ing

I tested this adapter on four com­put­ers:

Framework 13 with AMD Ryzen AI 5 340 (includes USB 4 / USB 3.2 Gen 2)

MacBook Neo (USB 3.1 and USB 2.0)

M4 MacBook Air (USB 4 / USB 3.1 Gen 2)

Desktop with AMD Ryzen 7900x with B650 moth­er­board (USB 3.2 Gen 2x2)

Getting those spe­cific USB port specs is a bit of a chore (some web­sites don’t even tell you if it’s ‘3.2 Gen 2’ or ‘3.0’, and Windows it­self only says “USB 3.0” when you plug in a USB 3.2 Gen 2x2 de­vice like the 10 Gbps NIC!)

I was only able to get full 10 Gbps speed (minus a lit­tle over­head) on the AMD Desktop, which has a sin­gle USB 3.2 Gen 2x2 port good for 20 Gbps of through­put. The other ma­chines got around 6 – 7 Gbps:

The Macs have the same per-port band­width (USB 3.1 Gen 2x1, for 10 Gbps), but the per­for­mance is con­sis­tently worse than the Framework.

On the Macs, the adapter was cor­rectly iden­ti­fied when I plugged it in, and worked straight­away, with no ex­tra dri­ver in­stal­la­tion. The ‘Hardware’ tab in the Network set­tings in­cor­rectly re­ported a con­nec­tion speed of 2500Base-T.

On Windows, the adapter was rec­og­nized when plugged in, but would­n’t con­nect to the net­work un­til I in­stalled the lat­est Realtek dri­ver, down­loaded from their web­site.

Bidirectional band­width test­ing of­fered an in­ter­est­ing con­trast; the Macs both han­dled traf­fic sym­met­ri­cally, while the Framework was wildly dis­parate. The desk­top PC gave a full 9.5 Gbps down, and around 5 Gbps up.

The main take­away is this adapter only reaches its full po­ten­tial if you have a USB 3.2 Gen 2 2x2 20 Gbps port.

And con­sid­er­ing the mess of USB nam­ing over the past decade—and the fact Microsoft re­ports all USB 3.x con­nec­tions as “3.0” in their Device Settings pane, good luck fig­ur­ing out your own com­put­er’s sup­port with­out glanc­ing at spec sheets!

A few com­put­ers I’ve seen ac­tu­ally la­bel the USB port speed (e.g. ‘10’ or ‘20’), but that seems fairly rare. Most man­u­fac­tur­ers seem to fol­low Apple in es­chew­ing la­bel­ing en­tirely!

At least Apple has the ne­go­ti­ated port speed vis­i­ble in the ‘System Information’ app—I could­n’t find that de­tail any­where on Windows.

5G and 2.5G a bet­ter value?

With re­duced speed due to in­ad­e­quate USB port band­width, would a 2.5 Gbps or 5 Gbps adapter be a bet­ter value?

Testing the WisdPi 5 Gbps adapter pic­tured above on my M4 Air, it got 4.6 Gbps. The 10 Gbps adapter is 1.4x faster, but for more than 2x the price ($30 vs $80).

I think, if you al­ready have a 10 Gbps net­work, you use RJ45 and not SFP+ con­nec­tions, and you want a more com­pact adapter (compared to the bulky, hot Thunderbolt adapters), it’s a good deal. But if you need that full 10 Gbps or SFP+ sup­port, Thunderbolt adapters are still the best if you have Thunderbolt ports that don’t sup­port USB 3.2 Gen 2 2x2.

If you don’t need 10 Gbps, though, stick to 2.5 or 5 Gbps adapters—they are still the best value right now.

Thermals and Power Draw

I also checked ther­mals and power draw—though my tests are not com­pre­hen­sive. Measuring the ab­solute power draw is dif­fi­cult be­cause my USB-C power mea­sure­ment de­vices down­grade the con­nec­tion speed to USB 2, which means I’m not test­ing at full per­for­mance.

At the slower USB 2 speed, the adapter uses about 0.86 Watts of power.

And it does­n’t get that hot, which was sur­pris­ing. All my Aquantia-based 10 gig adapters turn into lit­tle ovens. That’s why they’re so big: the en­clo­sures are gi­ant heatsinks.

But the WisdPi only got up to 42.5°C af­ter run­ning a bidi­rec­tional iperf3 test for a few min­utes.

That’s warm, but not so hot that I’d burn my­self touch­ing it like I have with other 10 gig adapters.

Conclusion

If $80 is too rich, this is­n’t the only op­tion that uses the new chip; AliExpress is lit­tered with al­ter­na­tives. And you can get it on PCI Express cards, which by­passes the USB port re­quire­ment on desk­top PCs.

In the midst of all the price in­fla­tion in per­sonal com­put­ing, it’s nice to find a new de­vice that’s cheaper, faster, and (depending on your USB port) bet­ter.

Back in March, Firefox 149 was re­leased with many changes, like a free built-in VPN, a Split View that al­lows the load­ing of two pages side by side, and the XDG por­tal file picker as the new de­fault on Linux.

However, an in­ter­est­ing ad­di­tion had gone mostly un­no­ticed un­til now.

Firefox has Some Brave in it now

Shivan Kaul Sahib, the VP of Privacy and Security at Brave, has put out a blog post about some­thing that did­n’t make it into the Firefox 149 re­lease notes at all. The browser now ships ad­block-rust, Brave’s open source Rust-based ad and tracker block­ing en­gine.

The change landed via Bugzilla Bug 2013888, which was filed and han­dled by Mozilla en­gi­neer Benjamin VanderSloot. The bug is ti­tled “Add a pro­to­type rich con­tent block­ing en­gine,” and keeps the en­gine dis­abled by de­fault with no user in­ter­face or fil­ter lists in­cluded.

For in­for­ma­tional pur­poses, ad­block-rust is the en­gine be­hind Brave’s na­tive con­tent blocker (aka ad blocker). It is writ­ten in Rust and li­censed un­der MPL-2.0, han­dling net­work re­quest block­ing, cos­metic fil­ter­ing, and fea­tures a uBlock Origin-compatible fil­ter list syn­tax.

Shivan also men­tions that Waterfox, the pop­u­lar Firefox fork, has adopted ad­block-rust, build­ing di­rectly upon Firefox’s own im­ple­men­ta­tion.

Want to test it?

Before start­ing, head to Enhanced Tracking Protection’s shield icon in the ad­dress bar and turn it off for the web­site you will be test­ing this with. This way, ad­block-rust is do­ing the work, not Firefox’s ex­ist­ing fea­ture.

🚧

I sug­gest test­ing this ex­per­i­men­tal fea­ture on a throw­away in­stal­la­tion of Firefox.

Now open a new tab and go to about:con­fig. Accept the warn­ing when it shows up. Search for pri­vacy.track­ing­pro­tec­tion.con­tent.pro­tec­tion.en­abled and set it to “true” by click­ing on the tog­gle. 👇

Next, search for pri­vacy.track­ing­pro­tec­tion.con­tent.pro­tec­tion.test_list_urls, click on the “Edit” but­ton, and paste the fol­low­ing value to add the EasyList and EasyPrivacy fil­ter lists to Firefox:

https://​ea­sylist.to/​ea­sylist/​ea­sylist.txt|https://​ea­sylist.to/​ea­sylist/​easypri­vacy.txt

Remember to click on the blue-col­ored “Save” but­ton be­fore mov­ing on.

Left: ad­ver­tise­ment shown; Right: ad­ver­tise­ment blocked

Now visit a site with known ads, like Yahoo (as I did above). If it’s work­ing, ad slots will still ren­der in the page lay­out, but the ac­tual ad con­tent will be blocked. In my test, the ban­ner on Yahoo came up show­ing only the text “Advertisement” with the ad­vert bit stripped out.

Support in­de­pen­dent Linux jour­nal­ism! If you think we are do­ing a good job at help­ing peo­ple use Linux on their per­sonal com­put­ers, sup­port us by opt­ing for Plus mem­ber­ship.

Here’s what you get with It’s FOSS Plus mem­ber­ship:

✅ 5 Free eBooks on Linux, Docker and Bash✅ Ad-free read­ing ex­pe­ri­ence✅ Badges in the com­ment sec­tion and fo­rum✅ Support cre­ation of ed­u­ca­tional Linux ma­te­ri­als

Join It’s FOSS Plus

About the au­thor

Sourav Rudra

A nerd with a pas­sion for open source soft­ware, cus­tom PC builds, mo­tor­sports, and ex­plor­ing the end­less pos­si­bil­i­ties of this world.

last year i bought a Rodecaster Duo to solve some au­dio woes to al­low my­self and my girl­friend to have mi­cro­phones to our re­spec­tive com­put­ers when gam­ing to­gether and talk­ing on dis­cord in the same room with­out any echo, and to be able to swap that to my work pc eas­ily. the rode­caster is re­ally nice, it’s pretty ef­fort­less to use and works great for our home. I would gladly rec­om­mend it to any­one look­ing for a sim­i­lar so­lu­tion.

as is usual for any de­vice in my house, i try to en­sure when it’s time to up­date the firmware I have enough tool­ing in place to cap­ture how firmware up­dates work, or to at a min­i­mum cap­ture a firmware blob to try and re­verse en­gi­neer it and poke around for fun and/​or to see the of­ten hor­rific re­al­ity that is the in­dus­try we work in.

fw up­date

I was feel­ing pretty lazy and as­sumed that rode would dump the firmware some­where on my com­puter be­fore flash­ing the de­vice, so i set up Instruments on ma­cos to cap­ture disk ac­tiv­ity, and found where the fw was dumped, and sur­pris­ingly it was just a gzipped tar­ball. The de­vice I did this up­date on hap­pened to have the abil­ity to write to USB disks dis­abled, so the up­date ac­tu­ally failed.

Poking around a bit, i found the bi­na­ries of the stuff that ac­tu­ally runs on the de­vice, as well as a shell script that han­dles the up­dates them­selves. there are two par­ti­tions on the disk, so that if you brick one it boots from the other. It also does­n’t have any sig­na­ture checks or any­thing on the in­com­ing firmware. I’m used to many ven­dors of this style of de­vice re­quir­ing signed firmwares or some­thing nowa­days, kind of nice to ac­tu­ally own a de­vice I can mod­ify. I also no­ticed that ssh seemed to be en­abled by de­fault, and plugged in an eth­er­net ca­ble and saw that ssh in­deed is en­abled w/ pub­key auth only. Here are the keys that are added by de­fault:

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQCX/bCFTDgViuPvdFL/VMMVRrw9b5S8HcDQk17qoCEYwmI+IIG8rEAsLiaeCOwyhf9IN+8/LRaN0Z5ZfU3WMbmsKEg8zd1Yvqq74nFbhO47vbtzmCi9S4ucIKkBEVOyvyN5lt9hWf5t5nZSmlfldZK3Pem5y8wHM5A+K/gSnzp4gwQ1QYfFb068uQ+ciIdOhb8SkUs8CwzotglIbp19I6ZmXmsNj/TmpbUf5rMfUAf1gysZ5j1UdRWrvWVh5daqvZRsBBPbXEeJfDU3Nr3HR14XYt9mgexrz/5oyKSj/lQYLmh9cDfsxvkGNIQ8fF9l+n2L1KZM4lLgiGk4KFBjQHaIBZx9OebCiiZCO4NTJUBDk9a+SZpiDiipADV07s7vTInYyFA6GrmKtnq3M6upT4WJBvVuL/BMnK5yY1RZtoqox2/pcCg2rH5S1GIy0v0HFJisl7kWInlaG2mdsaCx19wAjCFe/qT9LyxjQ6+0rArI55/JJFDkNeMjrewRQwNdASjCox8vqXCBfjvsR9qv70/ywcymgsnLAnq2LuYg5FYwMMDYOvVnhACC+BYTdNDTn5oeMIjQCUenY/DPCHpJkf4YOf3YCMUTEU9tExhtwW/X+m21hS3+STLtTfqbUeg9CeuPQZgfl9vc65n3tMxAdlEGEDoTaNMAgr2TzJv92Ka9iQ==

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIDaNyzPfIcEeQsfzyQs/wyX6mX52kiS+4eNHfCaxFlgj

since our up­date failed, i swapped to a win­dows pc and set up wire­shark with USBPcap and then ran the up­date thru the rode­caster app. I roughly glanced at the pcap file and looked at where the up­date started, since it was a lot of traf­fic as I was also us­ing it for au­dio on an­other com­puter. I wrote down the packet num­bers I thought were in­ter­est­ing and threw them to claude code to dig thru the pcap while I was do­ing other stuff.

A bit later (cc only took 10 min­utes or so but I was busy for a while) I came back to a break­down of the struc­ture, and a python script to man­u­ally up­date a de­vice. The RODECaster App sends some HID con­trol stuff to the de­vice, one com­mand to en­ter the up­date mode (the ‘M’ com­mand), and then an­other (the U com­mand) to trig­ger the up­date. Both are just sin­gle ASCII char­ac­ters sent over HID re­port 1.

I am but a yaml-writ­ing slave and some­times a be­low-av­er­age ghidra user, and don’t of­ten in­ter­act with hard­ware de­vices, so get­ting some help from CC in dis­cov­ery was use­ful, as well as point­ing me to re­sources to ac­tu­ally learn more about hid de­vices.

The struc­ture was pretty sim­ple, you send the m com­mand, and then copy archive.tar.gz and archive.md5 (obviously just with md5­sum of the archive) onto the newly ex­posed disk. then you send the U com­mand to trig­ger the flash­ing it­self.

so the flow is:

plug in the rode­caster and power it on (or vice versa)

send the ‘M’ com­mand

mount the disk and copy archive.tar.gz and archive.md5 to it

chmod 777 both of them be­cause i dont care to fig­ure out how to do it prop­erly

un­mount the disk

send the ‘U’ com­mand

wait for the thing to re­boot into your new firmware

cus­tom firmware

I was still work­ing from my mac, and wanted to cre­ate some cfw to be able to ssh into the de­vice, so i just used a con­tainer to en­able pass­word au­then­ti­ca­tion for ssh (don’t shoot me) as well as add my own pub­key to the au­tho­rized keys, and dump out an archive for me to flash. you don’t re­ally need much to ac­tu­ally flash the de­vice, see here (example of the func­tions its not re­ally much to add the rest.)

run your script to flash the thing and bingo bongo you can ssh to it

con­clu­sion

I was re­ally sur­prised that I could ac­tu­ally flash firmware so eas­ily to this, and it is re­ally nice to own a de­vice. It’s a re­ally nice piece of kit and just kinda blends into the back­ground and I never have to think about it. I don’t re­ally know why ssh was en­abled, or why it had this key added by de­fault, but I sub­mit­ted a ticket to RODE for this as I could not find an ob­vi­ous se­cu­rity email to re­port to. I did not hear back, but I will watch to see if fu­ture firmware up­dates change any­thing.

It’s been a few months since i’ve done any­thing with this, and I am try­ing to just dump out my thoughts into a notepad and only very lightly edit it and then just poast. I re­ally love all of the RODE stuff I have, and yet again just want to buy more gear.

if you want to ask me ques­tions about this or have any ques­tions, you can reach me with the pri­mary let­ter of this do­main, at this do­main.

thanks com­puter, un­til next time

and oth­ers

added 30 com­mits

Seeking breaks oth­er­wise. We might be able to just fflush() be­fore or seek­ing

in­stead?

Turns out DosBox-X was hav­ing trou­ble with the Sound Blaster or some­thing;

stan­dard DosBox works cor­rectly di­rectly from the in­ter­rupt han­dler, and

with­out dou­bling the buffer size.

This is MUCH faster than just leav­ing buffer­ing dis­abled, and also works

around get­ting bo­gus reads af­ter an fseek. SDL_LoadWAV on test/​sam­ple.wav

no longer takes sev­eral sec­onds to fin­ish, and comes up with the cor­rect

data.

I won­der if we’re trig­ger­ing this in LoadWAV be­cause we’re mal­loc’ing data

be­tween seeks/​reads, and it’s caus­ing the djgpp trans­fer buffer to change. Or

maybe the Fat DS trick is con­fus­ing it? I don’t know, I haven’t had time to

de­bug it, it might just be a le­git libc bug in djgpp too, for all I know.

This uses an old trick we used in SDL 1.2 for MacOS Classic, which did its

au­dio call­back in a hard­ware in­ter­rupt. If the au­dio is locked when the

in­ter­rupt fires, make a note of it and re­turn im­me­di­ately. When the lock is

re­leased, if the in­ter­rupt has been fired, run the au­dio de­vice it­er­a­tion

right then.

Since there is­n’t a big de­vice lock in SDL3 (available to the app, at least),

this keeps a counter of when any SDL_AudioStream is locked, which is prob­a­bly

good enough.

This uses VESA in­ter­faces to man­age the dis­play and works with the soft­ware

ren­derer.

Events aren’t hooked up yet, so pre­pare to close DosBox on each run.  :)

…upport.

This gets most of the ren­der­ing ex­am­ples, which use SDL_GetBasePath() to

find tex­tures to load, work­ing.

Of course Quake 1 solved this bet­ter, haha. It’s smart: less mem­ory, dirt

sim­ple, and you don’t even have to worry about syn­chro­niz­ing with the

in­ter­rupt han­dler, be­cause it’s safe for both sides no mat­ter when an

in­ter­rupt fires.

[sdl-ci-filter djgpp]

[sdl-ci-artifacts]

- SDL_runapp.c: Add SDL_PLATFORM_DOS to the ex­clu­sion list so the

generic

SDL_RunApp() is dis­abled when the DOS-specific one is com­piled.

- SDL.c: Exclude SDL_Gtk_Quit() on DOS. DJGPP de­fines __unix__ which

sets

SDL_PLATFORM_UNIX, but DOS has no GTK/display server. The GTK source

is not com­piled (CMake UNIX is false for DOS) so this was a link

er­ror.

- sdlplat­form.cmake: Add DOS case to SDL_DetectCMakePlatform so the

plat­form is prop­erly de­tected from CMAKE_SYSTEM_NAME=DOS.

- i586-pc-ms­dos­d­jgpp.cmake: Add i386-pc-ms­dos­d­jgpp-gcc as a fall­back

com­piler name, since some DJGPP tool­chain builds use the i386 pre­fix.

- Implement dou­ble-buffered page-flip­ping for VBE modes with >1 im­age

page

- Save and re­store full VBE state on video init/​quit for clean mode

switch­ing

- Improve DOS key­board han­dling: sup­port ex­tended scan­codes and Pause

key

- Lock ISR code/​data to pre­vent page faults dur­ing in­ter­rupts

- Always vsync when blit­ting in sin­gle-buffered modes to re­duce tear­ing

Move au­dio mix­ing out of IRQ han­dler to main loop for im­proved

sta­bil­ity and to avoid reen­trancy is­sues. Add SDL_DOS_PumpAudio

func­tion, up­date DMA buffer han­dling, and ad­just sam­ple rate to 22050

Hz.

Silence stale DMA buffer halves to pre­vent stut­ter dur­ing load.

Detect SB ver­sion and se­lect 8-bit mono or 16-bit stereo mode.

Handle DMA and DSP setup for both SB16 and pre-SB16 hard­ware.

Add FORCE_SB_8BIT op­tion for test­ing in DOSBox.

- Poll Sound Blaster DSP sta­tus in­stead of fixed de­lay af­ter speaker-on

- Clarify DPMI con­ven­tional mem­ory is al­ways locked; up­date com­ments

- Document and jus­tify DMA mem­ory al­lo­ca­tion strat­egy

- Free IRET wrap­per af­ter restor­ing in­ter­rupt vec­tor to avoid leaks

- Throttle joy­stick axis polling to ~60 Hz to re­duce BIOS tim­ing loop

cost

- Always poll joy­stick but­tons di­rectly for re­spon­sive­ness

Implement banked frame­buffer ac­cess for VBE 1.2+ modes with­out LFB.

Detect and ini­tial­ize banked modes, copy frame­buffer data us­ing bank

switch­ing, and blank the frame­buffer on mode set. Page-flipping is

dis­abled in banked mode.

Open

Open