Yeah. Firefox will gladly make itself comfy in my 32Gb… It’s annoying because just because 80% of RAM is “used” doesn’t mean it is really.
Yeah. Firefox will gladly make itself comfy in my 32Gb… It’s annoying because just because 80% of RAM is “used” doesn’t mean it is really.
Macbooks would not survive the antarctic outdoors…
Then we need reverseX and reverseY
Like driving a shitty car because you really like a certain brand of seat covers.
Is this for real or a joke? I can’t tell anymore.
Patient HP kept dropping to zero after resetting, but we don’t have budget to investigate why and this was supposed to be worth only 1 story point, so we set up a microservice that runs a job every 200ms to set HP back to 100. So long as nothing shuts down the service, patient should be fine. Marking as Done.
They are a doctor of computer science, not a doctor of design. You need a design phd to pick correct fonts.
I prefer that than to sneak defects in huge PRs.
I know this is a joke, but it you did that I would reject the pr with the reason of too many things at once. Reopen separate PR to refactor variable names. I actually constaly get people doing this and it’s dangerous exactly for the reason you’re joking about. Makes it easier for errors to slip in.
This meme only works if you don’t include any example that is better than others in every regard.
You’re not alone… This makes no sense.
Do retros every week or two and use them to improve the process. Best way to learn from others.
I’m the opposite. I will write literally a book of poetry for the tiniest feature to justify my pay raise at the end of the year.
As I said: they are worth the price. Did you read half my comment and and jumped to mansplain my own phone to me?
They are not pricey but have the specs of a phone 1/3 the price. But I still find them worth the price.
Fortunately there are several brands now offering android updates for 5+ years.
The problem is that what users consider low hanging fruit is often not, and what is low hanging fruit for devs, is invisible stuff that users don’t notice. The intersection is the tastiest low hanging fruit, but as such it’s also rare and easily picked by anyone.
Even then, there are bugs that need multiple people (design, engineering, content, QA, etc) and are not something that can be fixed on a whim.
They do, and they have a backlog of hundreds of issues to fix and they must prioritise then. If fixing a bug doesn’t make money, it’s not priority.
You got it wrong actually. Firefox is not really actively using all the ram. It’s more like reserving it. The system does that too. When the actual used RAM gets low, Firefox releases some of this unused RAM.