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.

Going against a trend is never easy. Ya gotta want it.

All of the listed problems are surmountable. This little test had insufficient will, determination, and resources behind it.

With little more than a token gesture like this, failure was inevitable.

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.

nah, a RS code can correct a tiny bit of loss but two metadata copies can correct a bad sector or even track if you're lucky.

Different requirement spaces.

The idea this guy has might make embedded devices slightly more long-lasting.

They usually have quantity one of a cheap storage part and a bad block in the wrong place could brick the whole thing.

It would only be useful in the case where maybe the build is 12MB and the chip is 16.

Most vendors won't ever pay extra for this.

I suspect the people who hate it don't have problems it solves.

Maybe a very basic home laptop is fine with SysV today and they don't want to learn anything new.

Personally I've been able to retire thousands of lines of scripts I'd written to handle complex things with many edge cases and ugly devops modules that are no longer needed with more recent releases.

There's just no userland interface to many of the events it can respond to and it's not easy to write a new C++ daemon to handle each need that comes up.

At this point it's largely a functional API to kernel events in the way I use it. That's the DOTADIW perspective for me. I still have services call my scripts where it doesn't handle what I need. It would be crazy to ever expect it to handle everything.

But just because I need to handle complex things at scale sometimes doesn't mean everybody else does. If I want to run debian with X11 and emacs and you want to run Devuan with Wayland and vi, you'll get no argument from me.

Who has time for drama these days?

If AI winds up costing us a fortune and never actually making businesses that use it profitable, then we don't need to actively resist it. The market will kill it naturally. There might be a bit of a mess left behind to clean up, but, we will be paid to do that clean up (or in the case of FOSS, devoted volunteers will do the clean up).

If, on the other hand, AI does wind up saving a lot of money (even if not in all the places we had hoped), then resistance is futile. There is too much wealth and power behind it. The power asymmetry is too great. They will get what they want, and our resistance will just be speed bumps on that road. This isn't a very happy situation for most of us, but it's the way the world actually works and always has worked.

In either case it still makes sense to do things like protest and politically block the creation of data centers in one's area until the harms that a data center causes are properly offset by the owners and operators (with real legal teeth behind that). That is a battle that we stand a chance of winning if we actually keep up the good fight.

Everything else is pretty inevitable, though, and only hinges on how profitable AI use actually turns out to be once the chips land.