Capitalism was never about âoeyou or me.â It was and still is all about accumulation of assets, wealth, and power and the expense of the working class. The layman boomer worldview of capitalism oddly shaped by a gentler and kinder state capitalism checked by a functional welfare state. Somewhere along the way people forgot the âoestateâ part and the âoewelfareâ part, which leaves us with this late-stage capitalist hellscape controlled by the geriatric class.

Read the fine print. PYUSD is not guaranteed to trade at par in all circumstances. Itâ(TM)s a claim it cannot legally make.

Accenture digital marketing business is one of the biggest digital marketing providers in the world. Intel is in an aggressive cost out transformation so if they are going with a premium rate card service provider like Accenture, that tells me their existing cost base is insanely bloated or low quality.

US has shifted its production from domestic shores to Chinese shores. CO2 generated from American consumption of Chinese goods needs to be reallocated to America to understand who and what is driving CO2 in aggregate. If America were to reshore all Chinese production with our current infrastructure, CO2 would go through the roof because of our inefficient infrastructure

Indian homes are not usually insulated well or at all and are typically very exposed to elements in key areas with sub par windows and doors. This is why homes quickly heat up again after switching off the AC. Leakage is real. Not just true for Indian but for so many countries in Europe, Asia, Africa, America.

Insulate like you live in Scotland, then no problems

MMT, heterodox and Post-Keynesians is where the serious analysis is happening and where smart money is looking to for predictive power.

This might actually mean that the impact of this particular patch is even greater as it is disproportionately impact colocation and enterprise DCs that operate far more inefficiently than MAGS hyperscalers (based on PUE)

Only when using these models from service providers. When the same models are run locally, they work well.

âoeStupid Opinions for $500â

No one cares about efficiency when national security is at stake. America is so behind on securing key earth minerals that itâ(TM)s a national security issue.

It is insane how much value Chinese cars deliver for a 45000â SUV/Car. I rented a Lynk & Co SUV for a week in France and was inspecting every inch of the build quality, and critiquing the ride and handling. I would totally purchase in America if I could.

I was living a large flat in London that had multiple Sonos units. I listened to so much more music and the experience of the music blending with the vibe of the flat was next level. I decided that when I get a permanent place I would get a similar setup.

Multi room music listening just hits different as you go about your routine and day.

I want to add that adding color was essentially the last step in the redesign. It does not play an important role overall, it literally can't.

You'll find if you look at the posts in https://mastodon.social/@julia... from 11th/12th that the color landed fairly close to the end of the first round per request to make it look more like a diff.

The evolution was:
1. 10:36 PM initial terse UI proof of concept: use less words (https://mastodon.social/@juliank/112254503514992757)
2. 10:51 PM add spaces and hide the progress from reading lists and building dependency tree (https://mastodon.social/@juliank/112254562137228107)
3. 11:22 PM merge the columnar display branch from 2 years ago (https://mastodon.social/@juliank/112254684145776880)

Friday:
4. 11:45 AM removing duplicate "additional packages will be installed" section, instead moving dependencies out of the main section (https://mastodon.social/@juliank/112257600155511076)
5. 12:33 PM adding color for popey locally and then grewing to like it (https://mastodon.social/@juliank/112257793195180589)
6. 02:45 PM opening merge request

All times in CEST.

At some point I moved the removals to the end, essentially reordering the blocks by priority without (or well as little as possible) breaking reasoning context (i.e. Suggested packages need to come after Installing because they are suggested by the packages being installed).

I like to believe that even without colors as it was for most of the time in the evolution this is a big step up from the wall of text you had before in terms of easily making sense of it.

I understand your concern but I want to point out that red/green here resembles the colors you normally use for a diff; as the solution is a diff for your package. That's why red and green are sadly the natural choices because somebody picked that decades ago.

For colorless systems, there's emphasis on dangerous actions due to their heading being all uppercase. It's not particularly good emphasis, but it's better than before when the upper case was inside a longer sentence (people actually complain about seeing upper case now).

Essentially we have three categories of package lists that can be displayed:

- Non-destructive actions that will be performed, like installs and upgrades
- Destructive actions like removals and downgrades (red and yellow color coded to match error/warning)
- Notes that show packages that can be autoremoved or suggested packages that will not be installed, or packages not upgraded (usually due to the archive issues)

The first goal when you look at the screen is to draw your attention away from the "notes" kind of things such that you can easily glance what the changes are that actually will be performed.

The second goal should be to focus on any destructive actions in particular such that you spot the common issue where you get many packages removed due to conflicts.

Now the problem without colors all we have left to draw your attention is bold/bright, underline and italic.

Now assume I mark removals bold because I want to draw your attention to it, I don't have a good way left to draw your attention away from other notes because underline and italic are awkward.

Of course you can reconfigure every color in APT with the APT::Color option space but it needs more documentation.

We have to think about apt-*s future in about 3-4 years. With apt(8) now getting versioned output you can get the same "scripting interface stability" of 5 years as for APT's ABI (and mostly API) you will just need to request it. But really either interface is not made for scripting.