has dust changed

Dust. Dust never changes.

Copy of Outlook Final (2) (new)

One day Gregor Samsa woke up and realized he had at least three friends.

Yep. I run Garuda and the main pull is that it’s a more user-friendly Arch with a lot of stuff I want to use preinstalled. I don’t really care about how XTREME it is or whether I might potentially get 1 FPS more.

All other things aside, which Logitech mouse are you talking about? Both my G Pro and my G 305 work out of the box. Logitech also advertises them as ChromeOS compatible and AFAIK the Logitech wireless dongles are USB HID compliant so seeing a Linux straight up refuse to interact with them sounds very weird.

Android already does that, no AI required. Some fairly simple math is enough.

The device first charges to 80% and holds there. It also calculates how long it will need to charge from there to full and when it will need to resume charging so that it will hit 100% just before the next alarm goes off. Then it does that.

I think a good way to handle this – as well as the wildly unpopular accessibility functions the post is about – would be to have it configurable and simply ask about it during initial user setup (aka OOBE).

That way people who didn’t need it can turn it off and won’t stumble over it after accidentally pressing the Windows key or holding down Shift a bit too long. People who need it can have it enabled right from the get-go without having to trigger some dialog first. Everyone’s happy and having one extra step during initial setup isn’t that much of a hassle.

Bonus points if Windows had configurable global hotkeys and I could make the Windows key do whatever I want. But the OOBE thing would be a good solution already.

I agree that it should be easily reachable. Just not through one single keypress. macOS’s Spotlight serves a similar purpose and is reachable via Cmd + Space (with the Cmd key being right next to the space bar). That’s just as easy to do as hitting one button but is extremely unlikely to happen by accident.

I personally use the start menu mainly for shutting down the computer as all commonly used programs are pinned to the task bar. A shortcut that opens it has no value to me as opposed to e.g. one that shows or hides a terminal window or one that mutes/unmutes me in Teams even when it’s in the background.

And I do consider it disruptive because having the start menu unexpectedly pop open and swallow several keypresses (and in the worst case launching some application I didn’t want to run) takes my attention away from what I was doing and forces it into something completely irrelevant. If this pulls me out of deep focus I can lose the equivalent of ten minutes of work due to one keypress.

The core of the problem is that this behavior is very annoying for people who don’t use the start menu all the time and there’s no way to change it. If it was just a default for a rebindable shortcut then it’d be a minor hassle once and nobody would complain. But the way it is it feels like Microsoft is trying to force-feed me the start menu, workflow be damned.

I think it’s extremely badly designed. A single keypress – especially if the key is in such an easily reachable position – shouldn’t steal focus. It doesn’t matter if I’m in a game or in Visual Studio, it’s disruptive.

This behavior would make sense as a media key somewhere near the F-keys. But as the default action on a modifier key it’s just bad design.

I can’t believe that launching the start menu is an action on par with opening an application menu or typing a capital letter.

The Windows key as part of a combination is great. It’s an extra modifier key.

The Windows key by itself is terrible because it immediately steals focus from the current application and can’t be disabled without something like AutoHotkey.

That image doesn’t look AI generated to me. GANs are typically terrible at keyboards.

Also, Ubuntu is moving towards using snaps for everything so they’re pretty much the successor to PPAs.

Mostly yes but there’s one other option that simplifies the whole thing: Chromebooks. They’re actually pretty decent for someone who doesn’t need much beyond a browser, a mail client, and a basic office suite.

Sure, they’re tied to Google with all that entails but they can be a real option for someone like a senior who relies on relatives for tech support.

Unbothered by typos. Moisturized. Happy. In My Lane. Focused. Flourishing.

I’d love to but on my gaming rig Wine/Proton will absolutely refuse to install the Visual C++ runtime, making me unable to play most games. On another, virtually identical, Linux installation it works without issue; in fact, I have fewer weird issues like a game randomly not connecting to EOS.

I consider it karmic justice for buying Nvidia; that’s the major difference between the two systems.

(Update: The latest Wine version seems to have fixed this. I’m certainly not complaining.)

When AMD introduced the first Epyc, they marketed it with the slogan: “Nobody ever got fired for buying Intel. Until now.”

And they lived up to the boast. The Zen architecture was just that good and they’ve been improving on it ever since. Meanwhile the technology everyone assumed Intel had stored up their sleeve turned out to be underwhelming. It’s almost as bad as IA-64 vs. AMD64 and at least Intel managed to recover from that one fairly quickly.

They really need to come to with another Core if they want to stay relevant.

I use interactive rebases to clean up the history of messy branches so they can be reviewed commit by commit, with each commit representing one logical unit or type of change.

Mind you, getting those wrong is a quick way to making commits disappear into nothingness. Still useful if you’re careful. (Or you can just create a second temporary branch you can fall back onto of you need up your first once.)

Or, if the team does allow refactoring as part of an unrelated PR, have clean commits that allow me to review what you did in logical steps.

If that’s not how you worked on the change than you either rewrite the history to make it look like you did or you’ll have to start over.

To be fair, he also had an eye for good product design. Not the skills to implement it but the ability to see whether a design is good.

Of course he expressed this skill by yelling at his engineers and designers. A lot. Because he was an asshole.

I actually went back to a light gray theme for my new Linux machine after I’ve been stuck with Windows’s options of “flat pure black with hairlines” and “flat bright white with hairlines” for too long.

I don’t actually need dark mode that much (except for coding) if a bright mode theme is easy enough on the eyes. Windows 10 is just so ugly that only the dark mode is halfway palatable.

If only the old themexp.dll hacks still worked I could have a decent looking desktop on all of my machines…