Will this likely fix stability issues in the Bun Workers API? https://bun.com/docs/runtime/workers

You could solve this fairly easily by giving an LLM the json definition of your sublime text theme and just transforming it onto a zed spec theme? No need for screenshots.

Wasn't enough (at least with Gemini 3). I had do a few round trips with screenshots until it got all the details.

Interesting - now that I think about it, feeding Claude my particular Xcode theme from VS code to replicate in Zed, the color tones were quite far off how it looked in cursor. I don't know enough about color rendering to know why that is, but I feel you!

I think this article (and the author's previous articles on their blog) is quite clearly AI written. It has such a frustratingly punctuated cadence and really does not serve the reader anything valuable.

What really does not serve the reader any value is this comment now appearing on nearly every single HN thread. (And neither does my comment, sorry about that.)

If you like the article, upvote. If you don’t, don’t.

I appreciate when people tell me something is AI written, so I can avoid reading it.

But people claim that text is AI-written on the most ridiculous grounds, like using proper typography. You might be missing out on interesting stuff!

I'm always missing out on interesting stuff. There's more great stuff being produced every day than can ever be read. It's just one more heuristic to apply.

I would usually agree, but I think we should be obligated to call out slop when we see it.

why would we read something nobody bothered to write?

It did give a few examples of common pitfall.

Not well organized, but not zero value.

Is GC useful for a static type checker? Or did they make a new runtime?

The point is that having a GC will affect your data structure and algorithm design, so it’s easier to automatically transform JS or TS to Go than to rust because you’re mostly reducing things down to one problem (translation) rather than multiple intertwined problems.

tyscript compiler is a cli tool. and is run for short periods of time. GC collection and memory leaks should be least of issue to look for

I've recently been dipping my toes into k8s / kustomize / helm, and I recently had a situation where having a base deployment yml template that I wanted to reuse across various deployments. I had a look at Helm and I was frankly shocked how bad the templating was with Go templates, it was close to unreadable and felt very brittle!

Shared up the chain, but bringing your attention to it as well: https://nixidy.dev/ solves all of these issues.

Yeah, that's fair. I don't think it's as bad if you make your own charts and can more liberally hardcode things. Community charts tend to have an insane amount of "knobs" so you can basically change everything being templated.

I don't know if I'd necessarily call it brittle, though. You can use `helm template` and various linters to validate the generated yaml is correct (and use something like pre-commit to autorun)

I did that too, and ended up just skipping helm and using envsubst to interpolate the values I need at runtime from env vars. Nearly everyone preferred that approach. YMMV of course.

I think that's a good approach if it works for your use case. Sometimes you might want something slightly more sophisticated like basic logic (loops/conditionals). In those cases, you can still use helm but you have an extremely simple template and avoid many of the "can't read this template" helm pitfalls.

BTW, this is what Flux V2 (GitOps) supports as well and we do at our company. It's worked well and covered almost all our use cases.

How so? I find it much the same to other templating engines like Jinja, though I'm definitely not a fan of the syntax. But that hardly matters anymore with LLMs.

I think it's a combination of text templating + yaml (which is whitespace delimited). When templating html with Jinja, it's not a big deal if the indentation isn't right. In helm, best case you get a syntax error, worst case you end up overwriting keys and producing something syntactically but not logically correct.

Specifically with YAML, Go templating requires some special operators to get anything useful done and it ends up being an unreadable mess.

On the contrary, anecdotally, myself and every engineer I know have switched fully from cursor to claude code since the start of the year. I now use zed with cc. I personally could not stand the buggy mess and constant UI changes of cursor. It’s also not good value in terms of claude tokens compared to claude code.

What sold you on Zed?

I recently switched as well. Being able to work in a large monorepo without the editor freezing and taking 15+GB of RAM was a strong selling point :)

It’s fast, looks nice and since i really just review agent output these days, that’s good enough. They don’t move everything around and it moves at a nice pace.

I think a more generous interpretation of dang's comment is that it's fine to use LLMs / tools to fix grammatical errors / spellchecking, but a heavier pass where the prose, wording and tone is altered (even mildly) can create a 'slop ambience' over time, death by a thousand paper cuts.

There's a gradient here for sure, but it's getting clear that people using LLMs "only" for grammar and spelling fixes are underestimating how much else the LLMs are doing.

Slop ambience just sure sounds to me like HN is banning a prose style. I guess I just think that if this is how the rule will be enforced, that is how it should be written.

HN already does a decent amount of content-policing, which helps keep the discussion higher quality. I don't see a huge diversion here from the usual moderation.

Home can be sure the LLM is modifying just the prose style? Moreover, prose style is one of signal that convey information about what you are trying to transmit (unlike code, which is totally debatable if it should have meaning on its own).

If you're referring to speaking in English - in general I think there is a huge amount of flexibility for making mistakes in English. I'm a native speaker, I am so used to hearing various levels of English from different nationalities that i'm almost blind to it. I much prefer to hear someones true voice even if there are a few inaccuracies, so much of a person's personality is conveyed through their quirks and mistakes.

Huh. I have the opposite opinion. I'm monolingual English for all intents and purposes but I gathered that opinion from quite a few sources, including:

- We had to take spelling tests in school

- English speakers make (generally light) fun of other's spelling or grammar mistakes in a casual setting

- In a professional setting, a lot of time is taken to proofread our own emails

- There's de jure spellings for every word

- Some online communities are really weird about pointing out grammar and spelling mistakes (namely Reddit)

Language is meant to be a fluid, evolving thing but I always felt like English was treated the opposite way. Maybe that's also why it's the de facto Lingua Franca.

I do think, and hope, that this rigidity will change thanks to AI. I've started to embrace my mistakes. I care a lot less about capitalization and punctuation in my Slack messages, for example.

I agree with this, and I’d even say that all the grammatical and spelling mistakes, awkward constructions, and labored phrasing is what makes a person’s posts sound like themselves. If people commonly use LLMs to rewrite themselves, then everyone starts sounding the same. And the posts, the users, and the entire site all become a lot less interesting.

I'm absolutely with both of you, but I'd like to point out that non-native speakers often tread a very fine line. They need to fear sounding either too convoluted or a bit of a simpleton. Proficiency levels vary wildly, and not everybody in the audience is as receptive and welcoming to slight mistakes as you are, even tough I have to admit HN in particular is pretty tolerant.

I for one don't think I'll ever AI-wash my texts or use AI translations verbatim. If everybody else did, it would certainly be a sad loss of diversity, but IMO it's only going to make the people who put in their own effort stand out more. Hopefully in a positive way. Time will tell if we're a dying breed.

I'm afraid the need for anybody to learn foreign languages will be subject to much change and discussion for upcoming generations.

I literally got a taxi today in Berlin because the trains were on strike, and the other day because the trains and trams were broken due to ice. You really can’t think of valid uses for a taxi?

For one, it has dynamic memory allocation and is much faster and resource efficient. Drop in replacement. It also has a rather nice UI,