Tell HN: I used the same computer since 2007 (with minor upgrades)

But even an old Nokia can only survive that many drops, so one day the phone screen stopped working. The phone would still turn on, make a startup sound, but it would only show white. Must be a display thing.

So we opened up the old Nokia, which meant lots of little screws. Inside we found that the screen and the main board were nog one part, but instead connected through a flat wire with like 10-12 lanes. Careful inspection of the wire showed there was a cut in the last two lanes. So part of the display signal was not reaching the display. Yeah, that might be an issue.

Searching the internet for the Nokia manual/design revealed the part number of the flat wire. AliExpress didn't have the part. In a stroke of luck, we actually found a webshop in the UK that sold the part for like 4 dollar. Ordered and two weeks later we got the part.

Opened up the phone again, replaced the wire, and the screen is working again.

I do want to say the phone is still in use, but unfortunately there are two issues we have been unable to solve:

1. The battery is no longer charging. The phone boots, and runs, but on the first incoming call, it drains so much power it just does. Unless on a charger of course. We have not been able to find a replacement battery yet (haven't searched either).

2. This is a phone from 2007, which means it has no 4G. 3G is already turned off and 2G is expected to be turned off in 2-3 years. This means this phone can no longer be used as a phone in my country. Such a shame really. We have bought a replacement Nokia 110 4G, but it is larger, heavier and has a illogical menu settings. I wish we would just have an upgraded version of the old phone with 4G. Snake is still there though, so we got that going for us.

Gmail currently does easily over 50 HTTP requests when loading, and browsers limit the number of connections:

https://docs.pushtechnology.com/cloud/latest/manual/html/des...

The net effect is that you wait at least 8x (but probably much more) your ping to the server for the page to load.

It's sort of a plague in enterprise web apps and stems from the fact that nowadays you have small teams working on independent modules, which do their own requests. Banking apps are the worst offender here.

Also some people are simply unaware of/ignore the issue. The other day I inspected an e-store my friend paid decent money to set up and the first thing that I noticed was that it was firing 200+ requests, because the devs neither bundled nor minified their code.

I thought this was because it was still in development - nope - another store by the same company had the same issues, causing the site to load 12s+ on a good connection, and 30s+ on a 4G simulator.

SSD/nvm are same defaults for me.

Memory I currently have 48gb in my desktop for running a VM properly.

My last CPU upgrade was necessary when I got a new camera and the raw files grinded Lightroom to a snail.

My keyboards are either full metal base with real cherry MX keys or a expensive ergonomic keyboard also with cherry MX keys.

I sit too long on my device every day to cheap out.

My displays always are at least IPS panels but my current display is already 6 years old. Still IPS with 27" and 1440 resolution.

I think it's good that you can work with your setup and your situation is a little bit harder I guess but make sure that you don't need to wait unreasonably long for your PC doing it's tasks.

And never use a HDD as your main hard disk!

I do a lot of things which just wouldn't be possible on his setup at all.