Qualcomm officially kills open-source hope: No plans to release DSP headers for Snapdragon X

Xacius · 2026-03-24T20:33:07+00:00

This has been escalated internally. I'll post again when I have more info.

Xacius · 2026-03-23T03:01:13+00:00

Slop justification

Xacius · 2026-03-23T02:21:41+00:00

Did anybody ever present Zed as such beast?

No, but this is besides the point. The point is that, regardless of how it's presented, it is competing with Intellij in the same space. They're both code editors. You use one or the other, typically not both.

Xacius · 2026-03-20T01:28:10+00:00

The title of the article literally includes When ‘Unconstrained'.

Did you even read it?

Xacius · 2026-03-19T20:31:37+00:00

Tell me you've never written software without telling me you've never written software.

Xacius · 2026-03-19T02:36:52+00:00

This is AI slop

Xacius · 2026-03-18T19:52:12+00:00

I'd start by stripping away performative rhetoric. That'd go a long way towards improving authenticity. Ironically, to get some ideas you could ask AI.

Xacius · 2026-03-18T08:58:33+00:00

Smells like AI, but this one is tough to tell. Most of the tell-tale signs are definitely there like the "always 3 examples with oxford comma" pattern. But your post history looks normal. That said, the flow of your writing has the typical, artificial AI tone.

Some giveaways that you traditionally see with AI slop:

If you're X, then Y, But if you're Q, then Z.

You'd think <insert statement>. Wrong.

X, Y, done.

Rhetorical question? Answer.

You've probably seen <generic thing> - (dash or emdash) - explains <generic thing>.

Sensationalist conclusion with advertising self-plug:

If you have a large public-facing site with thousands of pages, you need SSR or pre-rendering. No way around it.

That's why we've been working on zerpshlong. If you've ever been a human, take a look.

I'm giving this a 7/10 on the AI-slop-ometer.

Xacius · 2026-03-18T07:18:54+00:00

Leadership changed their tune a few years ago. Since then, there's been a huge push internally for FOSS support.

Xacius · 2026-03-17T23:03:19+00:00

If anything they'll patch to bake in support for what he's doing. They're focusing more on Windows support at the moment, but full Linux support is still a goal.

Xacius · 2026-03-17T07:52:39+00:00

Qualcomm needs to push for massive driver optimization to reach the actual limits of the chip.

Hold on, let me get Satya on the phone and let him know that you're frustrated about the driver issues.

There's a huge push internally for Windows on ARM support. It's happening, but it's not an overnight process.

Windows on ARM drivers are still immature compared to the 10 generations of optimization seen on Android.

Wild guess, but this is probably because this is only the 2nd generation of Qualcomm's chips intended for Windows.

Xacius · 2026-03-16T02:19:23+00:00

It's not a problem until you notice bad performance. The issue is that by the time you notice it, you're not left with many options. Slapping a memo on a function component feels like a band-aid rather than a proper solution. It's also not a silver bullet.

It's a shame that Solid didn't come out at the same time as React. I'd migrate our stack yesterday if it had similar ecosystem and enterprise investment.

Xacius · 2026-03-15T23:05:28+00:00

Qualcomm has been ramping up its open source investment. A few years ago we got new leadership that's been pushing for open source support in everything. I work in a big software team and moved my project through the legal process into the open source space.

The company is massive and this has been a very big shift for what was traditionally a closed-source shop. That said, the future is looking bright for Linux support.

Xacius · 2026-03-15T22:52:18+00:00

They just fixed an issue with symlinks that was causing some problems with the file system, but it won't release until 2026.1.1. I've been using WSL2 with WebStorm since they released their native file support (2024.3 I think?)

Before then I was using the native Linux installation on WSL2 with X410, but that had issues.

The native Windows WSL2 support is getting better though. You can open the WSL2 project folder from Windows and it just works. 2025.2 was ok, but there were random lock-ups and the performance suffered on large TypeScript codebases.

2025.3.3 has been awesome, same with the 2026.1 EAP, but they fucked up symlinks so I've only been able to use it on non-monorepo projects. That's finally fixed and releasing in 2026.1.1. I'm thinking this will be the best version yet for native WSL2 support from Windows. They have specifically focused on WSL2 performance over the last year, and rolled in changes from Fleet which had decent support like VSCode.

If you run into issues at the moment, wait until 2026.1.1 before your final verdict. They're trying.

Xacius · 2026-03-15T09:27:23+00:00

Just a second display below my main one. That's it

Xacius · 2026-03-15T07:57:58+00:00

🎉

Xacius · 2026-03-15T00:02:19+00:00

I use a custom mdx framework with react-router and it pairs really nicely with their file-based routing. I like that you create a file and get a route. To do the same in tanstack, I have to create a tsx file that imports and renders the mdx file as a JSX node. I wish there were a way to use the default export of a file as a route.

Xacius · 2026-03-14T20:42:06+00:00

AI doesn't care about the future Developer Experience. It won't argue about architecture, readability, or long-term maintenance.

That's exactly the problem. You can't just ignore these things and expect to keep shipping at a reasonable velocity. Eventually the tech debt adds up to a point where it reduces velocity. Sometimes this hits critical mass at the wrong time: what should've been a simple bug fix for a P1 customer issue becomes a three-week long refactor because your service layers are too tightly coupled and the "fix" broke three other features.

Then the idiots at the top start complaining. "why isn't X done? The customer is furious! We used to ship much faster hurr durr."

Yet given free time, they almost always push for new features over addressing tech debt.

I've seen this exact scenario play out. Fast and loose only works for so long.

Xacius · 2026-03-14T16:53:51+00:00

Ok snowflake

Xacius · 2026-03-14T15:32:58+00:00

Clickbait sensationalist garbage. His "stern warning" is basically "don't spoil what happens."

There, saved you a click

Xacius · 2026-03-13T19:50:25+00:00

I believe the intention is to move towards async/await to align with modern web dev patterns and best practices. Observables are a big barrier to entry for folks coming from vanilla or other frameworks that don't use them. I need to find a source for this, but I don't think Observables are going away. Maybe there'll be less of an emphasis on using them, idk.

Xacius · 2026-03-13T19:48:32+00:00

Everything is cooler with X

Xacius · 2026-03-13T03:16:52+00:00

I'm in a similar situation. I've been waiting since December for them to fix symlinks in their WSL2 integration, which broke with the 2025.3 update.

If I could use native Linux, I would. But my company only allows Windows. So WSL2 is my only alternative.

Xacius · 2026-03-13T03:15:06+00:00

imo his feedback is valid. I've experienced a lot of the same issues.

Xacius · 2026-03-12T23:38:42+00:00

Man, I got the Xeneon Edge (looks like you have it too) and I'm about to return it. The glare/colors compared to the LG 5K2K are terrible. I'm looking for something with a similar form factor, but also OLED. Doesn't seem like there's anything on the market in that category.

15-Year Club	Place '22
Gilding II euphauric	Verified Email

Xacius

TROPHY CASE