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

Chrome on my work laptop sits around 20-30GB all day every day.


I wonder if having less RAM would compel you to read, commit to long term memory, and then close those 80 tabs you have open.


The issue for me is that bookmarks suck. They don't store the state (where I was reading) and they reload the webpage so I might get something else entirely when I come back. They also kinda just disappear from sight.

If instead bookmarks worked like tab saving does, I would be happy to get rid of a few hundred tabs. Have them save the page and state like the tab saving mechanism does. Have some way to remind me of them after a week or month or so.

Combine that with a search function that can search in contents as well as the title, and I'm changing habbits ASAP.


Regarding wanting to preserve the current version of a page: I use Karakeep to archive those pages. I am sure there are other similar solutions such as downloading an offline version, but this works well for me.

I do this mostly for blog posts etc I might not get around to reading for weeks or months from now, and don't want them to disappear in the meantime.

Everything else is either a pinned tab (<5) or a bookmark (themselves shared when necessary on e.g a Slack canvas so the whole team has easy access, not just me).

While browsing the rest of my tabs are transient and don't really grow. I even mostly use private browsing for research, and only bookmark (or otherwise save) pages I deem to be of high quality. I might have a private window with multiple tabs for a given task, but it is quickly reduced to the minimum necessary pages and the the whole private window is thrown away once the initial source material gathering is done. This lets me turn off address bar search engines and instead search only saved history and bookmarks.

I often see colleagues with the same many browser windows of many tabs each open struggling to find what they need, and ponder their methods.


I've started using Karakeep as well, however I don't find its built-in viewer as seamless as a plain browser page. It's also runs afoul of pages which combats bots due to its headless chrome.

Anyway, just strikes me as odd that the browsers have the functionality right there, it's just not used to its full potential.


Websites that are walled off behind obscure captcha don't do well in Karakeep for sure, but so far for me those are usually e-commerce sites or sites I don't return to anyway.


If I'm doing work than involves three different libraries, I'm not reading and committing to memory the whole documentation for each of those libraries. I might well have a few tabs with some of those libraries' source files too. I can easily end up with tens of tabs open as a form of breadcrumb trail for an issue I'm tracking down.

Then there's all the basic stuff — email and calendar are tabs in my browser, not standalone applications. Ditto the the ticket I'm working on.

I think the real issue is that browsers need to some lightweight "sleep" mechanism that sits somewhere between a live tab and just keeping the source in cache.


I wonder if a good public flogging would compel chrome and web devs to have 80 tabs take up far less than a gigabyte of memory like they should in a world where optimization wasn’t wholesale abandoned under the assumption that hardware improvements would compensate for their laziness and incompetence.


The high memory usage is due to the optimization. Responsiveness, robustness and performance was improved by making each tab independent processes. And that's good. Nobody needs 80 tabs, that's what bookmarks are for.


"that's what bookmarks are for"

And if you are lucky, the content will still be there the next time.


Is there a straightforward way to have one-process-per tab in browsers without using significant amounts (O(n_tabs)) of memory?


There is no justification for that IMHO. The program text only needs to be in memory once. However, each process probably has its own instance of the JS engine, together with the website's heap data and the JIT-compiled code objects. That adds up.


I'd very much like a crash in one tab not to kill other tabs. And having per tab sandboxing would be more secure, no?


What do you mean? All these features are provided by process per tab.


Thats a weird assumption to make.


~10 projects in Cursor is 25GB on it's own.


How much would it take up if there was less RAM available. A web browser with a bunch of tabs open but not active seems like the type of system that can increase RAM usage by caching, and decrease it by swapping (either logically at the application level, or letting the OS actually swap)


The computer has 18GB of total RAM so I would hope that it’s already trying to conserve memory.

It’s kind of humorous that everyone interpreted the comment as complaining about Chrome. For all I know, it’s justified in using that much memory, or it’s the crappy websites I’m required to use for work with absurdly large heaps.

I really just meant that at least for work I need more than 8GB of RAM.


I do work off of a Chromebook with 8GB of RAM total, but I do keep an eye on how many tabs I have open.


Perhaps a small nit, but the “design space tree” looks more like a directed graph.


You can try setting `export PYTHONWARNINGS="ignore"` to suppress warnings.


Anecdotally, I fly round trip out of SEA ~3 times a year and experience very bad turbulence on about half the flights. Earlier this year it was bad enough to suspend drink service.


I also fly commonly out of PDX and SEA. Generally anywhere near mountains is going to be bumpy (Denver is a roller coaster every single time).


> Earlier this year it was bad enough to suspend drink service.

If drink service wasn't suspended on others, it wasn't very bad turbulence. A rule of thumb is that if your seat belt isn't hurting you, it's moderate or lower intensity.


About a decade or two ago, turbulence seemed worse. My uncle told of a time when he saw people hit the ceiling. I've rarely had issues, although plenty of smaller pockets where service does get suspended. I fly out of SEA, but in my opinion, DEN is much bumpier because of the sheer winds from the Rockies.

My rule of thumb is if the drinks didn't fly into the air and spill, then turbulence is minor.

Also pilots largely avoid microbursts now:

https://www.aerotime.aero/articles/microbursts-the-danger-th...


> At Amazon you can't even open the building next door without approval.

This is not true.


This is absolutely true and has been for years. You’re granted access to the minimum number of buildings required for your job function, and can file a ticket for temporary access grants to other buildings based on need.


It’s absolutely not true and hasn’t been for at least the last 5 years, in my experience.

I have access to every building in my city despite only requiring access to one of them, and I didn’t have to request it.

When I visited Seattle, I had to request access (which required clicking a grand total of 5 buttons in an internal portal and was instantly auto approved) to “the Seattle campus” and was granted access to every building, and still have that access years later. It wasn’t temporary.

Ditto for the other offices I’ve visited, both domestic and abroad. One office internationally I literally showed up and walked to reception and said “hi I work here but I’m visiting from out of town” and they immediately gave me access. I don’t see how this is different from the “second passport” described in the article.*

There are a couple of limited-access offices such as for subsidiary companies, but those are not the majority.

* - the one big difference definitely is the amenities and food, though. Amazon offices don’t have great, or even good, food. And the amenities are lame, most offices don’t even have a gym. There isn’t much of a reason to stop by an office unless you’re specifically there to work.


I worked for Amazon for a bit over two years, followed by Google for a bit over the last decade.

It never would have occurred to me to visit an Amazon office, so I didn't know about the ticket thing. I rarely worked with anyone remote.

When I joined, Google encouraged travel (less so lately). In the time I've been here I've visited over a dozen offices around the world. Some of them on vacation, because I knew there would be something unique about the local office, but also because with the exception of one office (Copenhagen), I'd worked closely enough with someone there to drop by their desk, say hello, shake hands, and get the best restaurant and bar recommendations I've ever found (and some great unexpected dinners with colleagues!)


Guess it depends where you work, because it was certainly true for me.


This is a very important point.

I'd argue all these "publish your DB schema as a GraphQL endpoint" frameworks that seem to proliferate have done a lot of damage to GraphQL's reputation. Strongly coupling data to presentation seems like such an obvious anti pattern, yet tools doing just that seem to be very popular for some reason.


Agreed, the reason I really like GraphQL is you can map different parts of your schema "tree" to different backend systems, APIs, etc. This makes your API plane/BFF nicely decoupled from those details like DB tables, etc.


You might be interested in this: https://brandur.org/idempotency-keys


The objects directory stores every file (and tree, commit, etc). Pack files are an optimization storing diffs.


Which is such a genius implementation. You get the straightforward implementation of using plain files (e.g. not deltas), while also being able to get the storage boost from storing deltas.


Cassandra does not make you immune to database issues: https://monzo.com/blog/2019/09/08/why-monzo-wasnt-working-on...


Yes. You still have to read the docs before randomly setting “auto_bootstrap” to false.

Or just use Astra and not worry about scaling your own cluster.


Did GP make such a claim? I didn’t see it, but maybe the comment was edited.


The interior has been aluminum, but the band around the outside has been stainless steel.

> Ceramic Shield front, Textured matte glass back and stainless steel design

https://support.apple.com/kb/SP875?viewlocale=en_US&locale=e...


Interesting. 13 mini is

> Ceramic Shield front, Glass back and aluminum (sic) design

https://support.apple.com/kb/SP847?locale=en_GB


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

Search: