Hacker Newsnew | past | comments | ask | show | jobs | submit | rootnod3's commentslogin

And same as vibe coding, microwaves just reheat old stuff and create bland food.

So, best to just use <insert most popular language> for maximum results? And have the LLM just rehash the majority of what that language's code looks like? Because a lot of say Javascript code I have seen floating around on Github has been absolutely atrocious. That doesn't really give a good basis for LLMs.

I agree that stronger type systems might help. But a good swatch of unit tests should still accompany that code.

The Clojure code I have worked with usually had a damn good array of unit tests as its more of the "clojure" culture to do so.


Because most languages don't have a full interactive REPL like for example Common Lisp has. The Python REPL for example is a joke compared to it. Clojure is very closely there, but not quite yet.

Live image editing is just pure bliss.


Then why would SuSE spend money on it?

Cool, one more layer of indirection and abstraction. May I ask why? I fail to see the point, but I might just be grumpy.

I don't even know where to begin here... Using Haskell, the one language where you really DESIGN by types and use your brain and then using LLMs....

That should be off by default. That alone is a "I won't use this" for me.

I was willing to give it another go. Now I read on this thread that it installs tons of node packages (so much for Rust native code) and even Go packages, and gets many extra processes running along with it.

https://github.com/zed-industries/zed/issues/7054

https://github.com/zed-industries/zed/issues/12589

TL;DR: Mix of language tooling, unsigned proprietary blobs, corrupted and/or GLIBC-dependent files, redundant copies of already-installed executables. The Node packages especially are able to run scripts on install. Personal preference aside, might also create issues with security laws, certifications. All without user consent.

Issues opened in January and June 2024. They've been rejected, closed, and opened a couple times since then. No changes directly improving this yet as of April 2026.

Personally, I think even if they eventually fix this, given the attitude shown towards their users' machines, I should probably just use an editor where I don't have to worry about it.


Modern software. That's why I stick with Emacs or Neovim.

> Our priorities are clear: availability first

That's a delayed April fool's right?


No, just a 6 month old memo that was first opened today, as they said literally the same 6 months ago.


Hardcover not available on .co.jp, shame


And that expert will not have their knowledge from learning through AI


why not?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: