Constantly ran into showstopping bugs in the compiler chain, that led us to think not many people were actually using in anger. Some of the bugs weren’t present on their devcloud, we assume they had livepatched some of them out.

And every few months they decide to reorganise or rename oneAPI, and every time they do this all the documentation URL change so it’s impossible to find old docs.

Then they deprecated the card we bought the month after, promised ongoing support, but the only available oneapi required RHEL8, whereas the drivers for the card only supported RHEL7. They removed the docs saying how to resolve this, and they didn’t work any more anyway if you had saved. And you couldn’t get old oneAPI without a paid support contract (and that had the bugs that we had proven to them anyway).

Long story short, will never, ever, ever touch anything INTEL software ever again.

Wasn’t https://anchor.host/someone-bought-30-wordpress-plugins-and-... like, a month ago?

No, the plugin is downloaded at runtime on first launch

The amount of outright obfuscation with this issue is absurd. Either many of the big names that have jumped on the bandwagon are credulous idiots or deliberately misrepresenting what has happened for their own gain.

GitLab has just as many outages, just nobody notices/cares so much

Bambu doesn’t want to serve people who reverse engineer the new (again, closed source) binary blob.

All of this being about the AGPL is just disingenuous ragebaiting.

2017 GTX 1070 and 32GB ram. I don’t run games 4K and still haven’t had any problems running reasonably pretty recent stuff.

I guess this, lowers the barrier to entry for this extremely specific niche?

What other VCS behaves this way by standard? If it's not in e.g. .gitignore "git status" will show that it's aware of it, but won't automatically absorb them into the commit? https://github.com/jj-vcs/jj/issues/5596 doesn't seem to be the oldest instance of this problem, but does seem to be the current discussion, and there seems to be no consensus on how to fix.

Oh, and ISTR submodules were a pain to work with.

Edit: https://github.com/jj-vcs/jj/issues/323#issuecomment-1129016... seems likely to be the earliest mention of this problem

- All of everything good about it breaks down the instant you want to share work with the outside world. It's git on the backend! Except there isn't any concept of a remote jj so you have to go through the painful steps of manually naming commits, pushing, pulling, then manually advancing the current working point to match. And in doing so, you lose almost everything that gives it value in the first place - the elegant multi branch handling, anonymous commits, the evolog. Even if you want to work on the same project on two machines your only choice for this is without breaking everything via git is to rsync the folder. Yes, you can write alias to do all this like git. I might as well use git if I can't use the nice features.

- All files automatically committed is great until you accidentally put a secret in an unignored file in the repository folder. And then there is no way to ensure that it's purged (unlike in git) - the community response as far as I can tell is "Don't do this, never put a file that isn't in gitignore".

- And adding to .gitignore fails if you ever want to wind back in history - if you go back before a file was added to .gitignore, then whoops now it isn't ignored, is all part of your immutable history, and disappears if you ever switch off of that new commit state.

And then does every stage without running any of the validation. It's your agent's plan, it should probably be generated in a way that your own agent can follow it.

> Shortwave radio is more challenging than you might imagine.

Super shady and opaque. And this is just the start of the enshittification slope…