Antti

@zeddotdev @valigo Also let us disable extension autoupdates.

We try to make things "just work" as much as possible for our users. We ship with Node because a ton of language servers and now MCP servers are JS-based, including the one we use for our JSON settings. However, we understand auto-downloading is not ideal, especially given the recent supply chain attacks. It's something we're aware of, and we want to solve this in a way that we aren't introducing undue friction for our users who appreciate having this functionality built in. As always we'd love help: github.com/zed-industries…

"But Linux package maintainers are so needed" and here we see Arch packagers hard-require a supply chain provider when you install Zed editor, even if you never plan on using it for web projects. Of course, Zed is a little bit to blame here - by default, Zed ships with Prettier enabled for JSON and markdown files, so what it'll do even if you just download it from official site - it'll detect that prettier needs to be installed, it'll download bundled nodejs and npm from nodejs site, and then will install prettier from npm (see screenshots). Completely behind your back! Now, if Linux package maintainers actually upholded their self-assigned Importance Mission, here's what they would have done: 1) Patched Zed to disable prettier by default 2) Provide npm and node as _optional dependencies_ 3) Patch out managed node/npm download from zed But instead they just decided to cope out (they will say excuses like "unpaid labor" and stuff) and subject ANYONE who wants to use Zed even for Rust/C/C++ programming to security nightmare that is npm. So yeah, Zed does some shady stuff for sure - in my humble opinion, a text editor SHOULD NOT DOWNLOAD STUFF FROM THE INTERNET BY DEFAULT BEHIND USER'S BACK. On the other hand, huge L for Arch Linux.

@valigo @ryanflorence Have you ever baked cookies at home? They've got plenty of butter :)

@ryanflorence all these junk food places (and honestly even mid-tier restaurants) use ungodly amount of oil that is not very good for you. And I guess it's even worse in America.

Crazy how when you eat out you feel like crap immediately but you can bake cookies at home, eat a dozen of them, and feel mostly fine

@buildwithdanm Oxc is faster and has more rules, and js-plugins. But it's only faster if you don't use js-plugins, which you probably will use.

I am thinking about a replacement for ESLint. Biome vs. Oxlint? I see an advantage in Biome because it includes a formatter, so I will probably choose that one.

@zeddotdev Please make TypeScript lsp go brr too :) The new native lsp is in beta.

Big diff go brrrrr

@devongovett @theorangenotice oxlint is faster than biome, but when you start using oxlint your lint time will most likely be slower, because you'll start using js-plugins :)

@theorangenotice does it support running eslint plugins? we have a lot of custom rules that we need to enforce. oxlint worked with them without any changes which was nice.

Tried out oxlint on the React Aria repo: eslint: 78.13s oxlint: 35.27s oxlint without react-compiler rules: 2.9s Can't wait for the React Compiler Rust port. 😅

@devongovett Fun fact, eslint-plugin-react-x is doubly faster than eslint-plugin-react-hooks and has almost all the same rules.

@iamsahaj_xyz I'm not the only one thinking this! Been thinking of adding a dedicated cursor parking spot.

places to rest your mouse when you're not clicking anything

@glcst @tursodatabase nanoid has a nice collision calculator zelark.github.io/nano-id-cc/

I was planning to use UUIDs to represent the databases we have on the @tursodatabase Cloud. I got a bit worried that we would perhaps run out of UUIDs. I just double-checked and I think we'll be fine for the next year or so. Will use UUIDs for now, and if needed, rearchitect later.

@ryanflorence Oh yes, full of juicy corner cases. If you throw in retries and retry error messages. How to store them, where's the state, state updates for multiple processes, update favicon based on state, what if you deploy while task is running, authing and rate limiting the socket...

@Hiljaa oh you want github actions I see

What do you want to see me build with Remix 3 to get a feel for it?

I think example.com has been updated. It used to look a bit different.

@zeddotdev Might be asking too much but make toggling JSX comments sane please :)

Arriving this Zednesday: a dedicated action to toggle block comments. `cmd-k, cmd-/` (or `ctrl-k, ctrl-/`)

@jdxcode @OneManSaas Got `fetch` and `deploy` commands too, nice :) So far those two have been pnpm's moat basically.

@OneManSaas pnpm but faster

I wrote another package manager. aube.en.dev

Just yesterday for the millionth time I opened the notification panel on accident in @zeddotdev while trying to open the agent panel and stopped to think what does this thing even do? Guess nothing :)

@ryanflorence @DavidKPiano Holy grail layout :)

@DavidKPiano history, context, canvas I think some variation of it is the final UI

Just realized I have at least 4 installed apps that look almost exactly like this

@beeman_nl @zkochan @pnpmjs @NxDevTools @turborepo Nice. I've been using proto version manager from @tothemoonrepo. Very handy.

@Hiljaa @zkochan @pnpmjs @NxDevTools @turborepo A global install and per project. Codex found it and fixed it for me though, check here

It looks like @pnpmjs has been changing it's lockfile format (in a minor release). I've been getting warnings from both @NxDevTools and @turborepo 👀 Very inconvenient and pretty annoying - seems it should have been a breaking change, not ship in a minor version bump.

@mitchellh Simple landing pages are great, concentrate shipping the feature first, then polish the landing page :)

One of the most requested GitHub features in years and the website looks like it was designed by someone 9 years into a 2 year community college program. github.github.com/gh-stack/

@beeman_nl @zkochan @pnpmjs @NxDevTools @turborepo How do you manage your pnpm versions?

This screenshot is from my root directory that doesn't have a package.json I do see this (screenie 1) appear in one of my projects which seems to hint at v11. If I look into the ~/Library/pnpm/pnpm (screenie 2) it seems to be linking to 10.33.0. In `~/Library/pnpm/store/*` I see v11 did appear. I'm fairly sure I didn't update to v11 as I don't like running beta versions on my daily driver, I'm confused how it seems to have sneaked in here. Also both projects that have this symptom have a packageManager set in package.json which should make it use that version, right? Any tips that I can check where it is and get rid of it? Really appreciate your response 🙏

@pnpmjs Great! Meanwhile something like:

@Hiljaa Yes, in the next major version of action-setup it should work.

pnpm 11 RC 0 is out! github.com/pnpm/pnpm/rele…