Hacker News .hnnew | past | comments | ask | show | jobs | submit | rstat1's commentslogin

So I'm not so sure how you arrived at your conclusion of Zed having higher memory use than VSCODE but in testing just now that's not at all close to true.

Zed for me on my Linux machine opened to a massive C++ project (the Ladybird browser if you were curious) is (not including LSP or extension processes) using around 480MB of memory.

VSCode on the other hand with nothing open but a 20 line JSON file is (again not including any LSP or extension processes) using around 920MB of memory as reported by its own builtin task manager thing.

I suppose 480MB for a text editor might be a tad high but calling it worse than VSCode is a massive stretch.


If editors own memory usage is your main concern then you should use emacs or even better mg or vi.

The editor + its plugins + it's LSP server is what counts. I dont care if zed is written in rust and uses 400MB when it spawns a multi GB nodejs process when I work on my tiny golang project.


I mean all 3 of those also support LSP plugins, so would also spawn "multi GB nodeJS processes" with your tiny golang projects if you enable them.

Yeah but other editors do not foolishly choose to install and run those things out of the box.

and limited to one type of device that not everyone can get or wants.

Only because this is the one family of the devices secure enough to even bother with software security.

It's not their fault (plus since 2027 we expect the first Motorola handset secure enough tu be supported by GOS)

And at least they don't cheat on patches :)


Which when I last used it they forced you to do. I'm assuming this has changed in the several years since?

Correct, we got rid of this requirement a couple of years ago. No login required at all, except for using AI and team features.

> we got rid of this requirement a couple of years ago.

Do you regret having this requirement in the first place?

Personal feedback: I live in a terminal 24x7 for the last 30+ years and once Warp came out I wanted to try it out immediately, but I was impressed by the requirement. So I never had a chance to try it out.


Yes use Bitlocker, the thing that uploads the encryption key to OneDrive "for convenience" thereby negating the whole point of FDE in the first place


by default, yes. Can be disabled with a single click. That's something that even your Grandma can do, as opposed to installing VeraCrypt (with dozens of options on what to encrypt, and how, and when, ...)


Well no actually I do not think either of my granmothers could have done that, nor would they have even known (or cared) what a Bitlocker even was.


In my opinion if you learned something from it, it was useful. Bonus points if others learn from it as well, but if not then as long as you did then it doesn’t matter. AI age or not.

I’ve always found hobby OS projects like this interesting, and I hope there’s never a shortage of them in the future


That's a good way to look at it, and on reflection I feel the same way.

It's certainly useful _to me_ and has helped me really nail down concepts I thought I already understood, but it turns out I didn't.

I just hope that, in an age where it feels like code, and maybe even deep technical knowledge have diminishing value, projects like this don't become completely anachronistic.


The US has been doing that for years already. There's plenty of stories of people (US citizens included) being detained by border agents in US airports for refusal to provide said agents with access to their devices.


They can detain you and take your device, but they cannot compel you to give up your password, to be clear. As a US Citizen you have a right to re-enter the country.


The letter of the law says you are correct. Reality however disagrees. People who are most definitely US citizens have in fact been put in jail for the simple not-crime of refusing to provide passwords to their devices to law enforcement.


So if a company uses as part of its marketing for a product the phrase "advanced security, privacy, and connectivity for homes of every shape and size" and then is later found to have lied about the "advanced security" and "privacy" part of their marketing by shipping firmware with security bugs, does that not now fall under the "deceptive" category of the "unfair, deceptive and fraudulent business practices" part of the FTC's mission?

Sounds like it does to me. Also you're forgetting the part where the FTC under a prior administration either banned DLINK from selling in the US or heavily fined them for selling routers in the US that they knew were running insecure, buggy firmware.

(both quotes were taken verbatim from first, Netgear's US website, and secondly the Bureau of Consumer Protections' section of the FTC's website)


If that is truly what you think, then you clearly haven't used a Linux desktop distro since then because that absolutely incorrect.


OS makers should not be in the business of enforcing censorship. If you want to shield your children from the "horrors" of the internet either use proper parental control software, or don't allow access at all like you said until your kids are mature to understand what's going on

The onus is on the parent to the be parent. Not the tech industry, and especially not the government.


If the solution is parental control software, that also puts onus on operating systems to present the means for such software to work properly. This does not mean the OS should censor, it might mean the OS offers a censorship interface.

At least we seem to agree the solution lies with better tools for parents.


Who are you to decide what should or should not be?

"proper parental control software" doesn't exist for a lot of the platforms.


Google did it with the Tensor-powered Pixels a while back, from w/e they shipped with to 6.1


Okay, but 6.1 is still from December 2022. Like... it's an improvement, but as my desktop sits at 6.19 and 7.0 is impending, I have to question why they lag so much.


OP was talking about that they now have and pursue the intention of upgrading the kernel during the lifetime of the device. Instead of device launching with LTS kernel, which is supported for many years upstream, and always using it, instead LTS kernels are supported for 2 years (or extended like here), and the devices keep moving on to the next lts branch during their lifetime (usually not immediately, but after the regressions fixed for next branch, tested well before that in avf VMS etc)


Consider applying for YC's Summer 2026 batch! Applications are open till May 4

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

Search: