Having worked on a product that actually did this, it's not as easy as it seems. There are many ways of drawing text on the screen.

GDI is the most common, which is part of the windows API. But some applications do their own rendering (including browsers).

Another difficulty, even if you could tap into every draw call, you would also need a way to determine what is visible on the screen and what is covered by something else.

I'm guilty of doing this (just reading the headlines) as well. I usually do it for these reasons:

• I don't care enough to want to read more. For example, news about US politics. I don't live in the US. I feel that reading the headlines is enough to keep me informed about what's happening, but I really don't care any more than that.

• The details aren't valuable to me. For example, the Apple anti-trust lawsuit... Is it important? Yes. I'm already well aware of the horrible anticonsumer practices of Apple. But do I need to know all the particular details about the lawsuit? Not really. In fact, the only thing that matters is the final verdict, which hasn't happened yet.

• I care, but I already know enough details.

• I don't feel like the article would bring a lot of value, especially if the title is click-baity. I've encountered too many articles that are void of content, just the title repeated in 10x more words.

I don't like visiting news sites because, in addition to all of them being obnoxious and ad riddled, I feel like I'm wasting a lot of time reading long articles that could be rewritten as 3 bullet points. On platforms like lemmy, users will highlight the important bits in the comments which saves a lot of time.

Because Amazon is shitty with the sellers, the good ones can't make profit on the platform. All that's left is the Chinese garbage sold at huge margins, where the seller doesn't care if it gets returned.

Writing the actual code is the easy part. Thinking about what to write and how to organize it so it doesn't become spaghetti is the hard part and what being a good developer is all about.

First couple of minutes would be nice to catch up with world events. I would take some time to find money making strategies, like learning what to invest in, or what about to buy. If the person has any knowledge about some revolutionary technology, it would be nice to learn about it. Maybe we could use the knowledge to advance mankind. I would also want to learn about things to watch out for. Maybe I should move to some other country because the one I'm in goes to shit.

I would just undo all the mergers and acquisitions. In 90% of cases, this just results in the games being worse, and the magic that made the studios great is extinguished.

I use the smell test. If it smells weird in any way, it goes to the wash.

Guess who doesn't have to login to a Rockstar account? That's right, pirates.

It's obvious that autonomous drones are more difficult to create than they seem... I think delivery robots that go on the ground are much safer and more feasible. They can carry heavier packages, they are less dangerous and can travel at less dangerous speeds.

Same applies to basically anything.

Driving is awesome, but when you are driving because you are commuting, or you have to drive your kids to kindergarten/school it becomes a chore and you no longer enjoy it.

I love programming. But when I have to do it for someone else to earn a living, and do it in a specific manner that they dictate, it feels like a chore and I no longer enjoy it.

Having a workplace that is fun and enjoyable isn't about doing the thing you love. It's about a lot of other things, such as the people you work with, the company culture, how much freedom and choice you are granted.

What I think the biggest problem with the traditional package managers is that (1) they don't isolate packages from each other (when you install a program files are placed in many random places, like /usr/bin, /usr/lib etc) and (2) you can't have multiple versions of the same package installed at the same time.

This creates a lot of work for package maintainers who need to constantly keep packages up to date as dependencies are updated.

Also, because of this, every distro is essentially an insane dependency tree where changing even one small core package could break everything.

Because of this, backwards compatibility on Linux is terrible. If you need to run an older application which depends on older packages, your only choice is to download an older distro.

This is what snap and flatpak try to solve. I think they are not great solutions, because they ended up being an extra package manager next to the traditional package managers. Until we see a distro that uses flatpak or something similar exclusively, the problem is not solved.

There are 2 big obstacles we need to overcome. The first is corporate ownership of residential property. This needs to go away.

The second big issue, we need to build higher density housing, and get rid of the enormous parking spaces that take up our downtowns. Not everyone needs a house. And you can absolutely build medium density housing that doesn't feel cramped. Sure, living in an apartment is not perfect, but you are closer to the places you want to go, and public transportation is more feasible. It's a win-win for everyone.