Live data from Hacker News

Zed DeltaDB

zed.dev

321–329 of 329 posts

Re: Zed DeltaDB

#321
post #165

Earlier quoted context omitted.

> They'll re-invent/re-write things constantly Re-invent is fine, that's how we actually get the good stuff we use. Re-write (frequently) is usually a sign of bad power dynamics in the team, code rot and generally bad engineering management, in my experience. That's why most React shops end up in this vicious cycle of constant re-writes of a perfectly fine working system for this reason. Yeah, must be really nice get…

Sometimes I feel like the software field is just begging to be "disrupted" by AI. So much bad management and useless wheel-spinning, all with salaries far above what is typical for any given area. It's like taxis and Uber. Yes it's probably bad long-term that local taxi companies have been replaced by a mega-corporation. But there were so many bad taxi companies with rude dispatchers, lazy drivers, cars that show up…

That is mostly an US SV thingie, in many European countries, it is a comfortable office worker salary, just like the other folks on the office having jobs with any kind of degree above standard high school.

Re: Zed DeltaDB

#322
post #243

Earlier quoted context omitted.

And the cherry on the cake: you get paid to work on your engineering project, get traction around it as opensource and if there is enough traction, leave the company and spin-off a new one to sell the same product to other companies! It's surely a lot of work but you get basically the discovery phase til market fit with your ass covered. Kudos to the engineers that pull that out, I really mean it!

That’s why nowadays every company will require that they legally own projects you work on during work hours unless explicitly asked. And many ask you to sign non compete clauses so you don’t take all the knowledge you acquired on the job to the competition, including your own projects, through this is quite hard to really enforce.

That seems to be common sense, is it not the default? That should be the norm if it isn't, it's like being a freelancer and being hired and publishing the project in your own name, that's borderline criminal imo.

Re: Zed DeltaDB

#323

Whoever on the zed team came up with this must be coding with agents way more than i am, because it hasn't come up for me as something I'd really need yet. But it sounds cool anyway. I guess it's kind of like undo history but persistent and with more visibility, and with branching? Anyone from zed here to comment?

The fallacy here is that if you have LLM then just start a new thread. That's what all vibe coders do anyways

Not sure I get what you're saying?

Re: Zed DeltaDB

#324
post #243

Earlier quoted context omitted.

That’s why nowadays every company will require that they legally own projects you work on during work hours unless explicitly asked. And many ask you to sign non compete clauses so you don’t take all the knowledge you acquired on the job to the competition, including your own projects, through this is quite hard to really enforce.

That seems to be common sense, is it not the default? That should be the norm if it isn't, it's like being a freelancer and being hired and publishing the project in your own name, that's borderline criminal imo.

A lot of companies were founded by one or a group of people leaving a company and opening a competitor with the knowledge they gained while working for them. Anthropic, as I understand it, is an example (from OpenAI). Even the company I work for was founded by people who used to work at the "old" industry giant and today we compete with them directly. This is not criminal unless you signed a contract forbidding doing that, though you may certainly claim it's morally a gray area. But yeah, it's very common. You don't get lots of domain knowledge, which is required to start most kinds of businesses, until you've worked in the area for someone else for a long time.

Re: Zed DeltaDB

#325

Earlier quoted context omitted.

The fallacy here is that if you have LLM then just start a new thread. That's what all vibe coders do anyways

Not sure I get what you're saying?

Vibe coders don't bother reading code. They won't bother reading the logs

For any problem they just start chatting with LLM for 4 straight hours.

Re: Zed DeltaDB

#326

Earlier quoted context omitted.

Right, my point being that it's should be up to the user to decide, because most of the times I run programs, I actually want them to be able to gobble up GB of disk, RAM and fully make use of my CPU. That's why I bought the hardware I have :)

Isn't that the default? The user has access to all available memory unless they (or an admin) set a restriction. Unavailable memory is only unavailable because writing to it crashes the kernel, thus preventing you from using your hardware!

> Isn't that the default?

Yes, it is, and for good reasons. That's why I disagreed with the original "An unprivileged userspace application, even if coded poorly, shouldn't crash the machine" part.

Re: Zed DeltaDB

#327
post #257
post #233

Earlier quoted context omitted.

Breaking an illegal monopoly takes decades but, as it happened with Internet Explorer 6, it's finally happening for Windows.

70% market share, plus all the games that Proton depends on.

And trending down.

IE6 was 97%, how did that work out?

Re: Zed DeltaDB

#328
I don't see a need for a code editor anymore, though I understand that others feel differently. However, I think zed is going against the tide, and not in a productive way.

Re: Zed DeltaDB

#329

Earlier quoted context omitted.

Isn't that the default? The user has access to all available memory unless they (or an admin) set a restriction. Unavailable memory is only unavailable because writing to it crashes the kernel, thus preventing you from using your hardware!

> Isn't that the default? Yes, it is, and for good reasons. That's why I disagreed with the original "An unprivileged userspace application, even if coded poorly, shouldn't crash the machine" part.

I don't follow. The default today is that an unprivileged user space application should not crash the machine. The kernel reserves what it needs, then hands the rest to user space. Thus, all available memory should not crash the machine.

https://en.wikipedia.org/wiki/User_space_and_kernel_space

https://en.wikipedia.org/wiki/Virtual_memory

Post reply on HN