What?

Re-read what you wrote and go off and think about it...

HJKL navigation is not QWERTY-dependent, it works just fine on Dvorak-layout keyboards, although key placement/layout is a bit non-sensical, but "h" Dvorak moves the cursor exactly the same way "h" does on QWERTY.

EMACS is my favorite operating system...

Yes, but not for you and me. Graphics designers have been using stylus-displays for years and years, because it's great to draw on the thing you are making instead of drawing on a different surface like a Wacom.

But I'm like you, I don't have a use case for a touchscreen and if you touch my notebook screen I'll be angry because I prefer it without fingerprints, thanks. So my first question is: Do they offer this thing with OLED but without touch? I guess not. Pity.

I've been slowly moving towards my dream setup: Solar panels, battery, EV car, island mode capability. This is one thing that'd be a factor in my buying decision. Using your car as a battery or secondary battery is a big plus, and if they built the necessary equipment to run independent of the power grid, it'd come in a neat package.

While power failures are rare where I live, I expect them to become more common with the move to renewable energies. I support that, but it's more fragile than constantly running power stations. So being able to run your home at least for a few hours on your own energy is something that I consider a good idea.

I've only been paying attention since 1990 but every single time a feature they don't offer "is stupid" until they offer it.

Even when I liked the company this Cluster B behavior always bothered me.

If there's an example of "that's a really nice feature our competitor has but we don't offer it yet" I haven't seen it.

The closest I can think of was offering WebObjects for Solaris. Not sure if that ever shipped or we just had a beta. I bailed from that Healthcare IT team when the CIO pulled funding for two-phase commit among disparate patient medication systems with the rationale "even if medication errors kill someone it'll be cheaper to settle the lawsuits than pay for the license." Enough people left that they outsourced and everybody still hates that replacement system.

I learned too late that MBA's don't care about quality.

> everything you do has fucked the consumers

Say more ... how has suing to end the Play App Store monopoly 'fucked consumers'?

Let them do their thing.

I remember in High School the Camaro guys couldn't stop talking about how their Camaros were better than Mustangs but the Mustang guys never felt the need to denigrate the Camaros.

It's a matter of nature.

unrelated: Tailscale is so fooked today:

https://www.bleepingcomputer.c...

Some people here may need to panic right about now.

You missed the point.

A friend of mine made a tea-timer app for the iPhone. Where you enter what tea you are making and it sets the correct number of minutes. Today, people would ask ChatGPT before they go on the App Store to search for something like that. That's the point. Not what YOU would do, but what the general public does. And for Jane Doe, ChatGPT has replaced a lot of these specialty apps.

Skills are great until they aren't. The problem is exactly what you say: You can literally create a skill by telling the LLM to create a skill. Which is... why the f do I need to make a skill if the AI already knows how to do it?

Properly created skills, that include reference material, specific instructions, and expert knowledge the LLM doesn't have or that's buried somewhere under 10 layers of reddit posts is genuinely useful. But most skills aren't. I'm constantly underwhelmed by hyped-up skills that, when I look at them, turn out to be bland, basic instructions.

The right way to do this is to hire a group of developers and have test volunteers report workflow problems - then FIX them - then iterate. That's the point of choosing an open source solution.

Eventually there would be no problems remaining.

But so many possible scenarios exist that it's impossible to guess what happened here.

PS _NSA_KEY

There are apparently other unpatched vulnerabilities that are known but 'too busy':

It sounds like this fix got done because it was 'accidentally' posted as a public PR.

https://github.com/tianocore/e...

Yeah, the threat actor would need a foothold on the PXE network, which is a private VLAN (or better) in the competent case.

That's why we worry about APT's and such.

Granted, you'll find people on certain cloud providers who do far too much on a public IP.

What if someone has fifty windows open with fifty tabs each?

Asking for a friend.

Solid effort - good job.

It's a bummer if any of the employees got rug-pulled but many of the best employees will strike out on their own, form new companies with working conditions they value, and likely hasten Skydance's demise.