Surely finding is the hard part, and any LLM should be able to easily exploit a vulnerability it already knows about?

For example, if you take out a loan and you sign terms and conditions which say you agree to pay it back and then later your circumstances change and you can't pay, that's probably just a civil matter. But if, at the time you signed the agreement, you had planned to deliberately not pay it back, that's fraud and therefore criminal. The fraud is in the fact that you are making a false representation: you are saying you will pay it back, but you know that to be false. It's a very different thing from believing it to be true, but it then later turns out not to be true.

The same principle applies to LLM subscriptions (or any other contract).

The good thing about a total wipe is that it's very easy to implement, and it's hard for it to go wrong. You just encrypt the whole drive and, when you want to wipe it, erase the key.

In which sense? Intel is neither a full monopolist (AMD, ARM) nor has progress stalled (we're still getting a regular cycle of new generation CPUs which improve on the previous).

Also, it's far less likely than you're suggesting that I would need the exact major OS version I started with. The majority of apps survive an OS upgrade just fine. In my case, I use NixOS, so that isn't even an issue at all since every package can have all of its dependencies frozen for as long as you like, even with a new major OS version.

If I buy version 2 then it's mine and I can continue to use it for as long as I want, if I'm happy with the feature set. I can ignore version 3 or choose to buy it. If I buy it then I now own two products instead of one. Sometimes the older version might even be better (e.g. features I like have been removed or made worse).

With a subscription model I'm forced to pay again and again even if I'm perfectly happy with version 2.

- Subscriptions are marketed as being a lot more than just bugfixes - new features being the big one. But there's usually no cheaper "bugfix-only" subscription, which means that someone who doesn't care about new features has to pay for them anyway.

- To be honest - yes, I do expect bugfixes for free if I've paid to buy the product. After all, a bug is a defect, and products are usually sold with the expectation that they will be fit for purpose. That's the principle which applies to physical consumer products, so why should it be any different for software? If I bought software that calculates my taxes for me, and it turns out a bug means that it applies the wrong tax rules, then I haven't got what I paid for. Why am I expected to pay every month just to make my software do what it was supposed to do in the first place?

- The developer is still incentivised to fix bugs in order to attract new purchasers.

- Subscriptions aren't a magic solution financially anyway, because there's an average limit to how long a customer stays subscribed for.

People are however consistently willing to regularly make one-off purchases to get something they can "own". I've bought way more lifetime licenses for software than I've taken out subscriptions. When you consider that nobody stays subscribed for life, there's always a number that you can charge for lifetime which is in fact functionally equivalent to a subscription anyway.

A great example for me is the Xodo app on Android. It's by far the best PDF editor that I've found on Android, particularly for annotating with a digital pen. Some features are locked. If I want to unlock them, it's $5 a month. I get nothing out of that which isn't already in the app. I'm happy to pay a one-off fee for the work the developers have done up to that point. I'm definitely not happy to add another $5 a month to my pile of subscriptions.

For me the boundary is this: (1) If I get something of value every month (e.g. use of a cloud server, or something which obviously needs regular updating like Netflix) -> subscription justified; (2) If I just want to use what I can already see in the app -> very unlikely I'll ever subscribe unless the product is absolutely essential to me and there are no competitors.

A good example of the latter is Skritter. I don't care about new functionality, but there literally isn't another app which can do what it does, so I pay the subscription.

This is clearly incorrect given that there are plenty of software developers who offer lifetime purchases. In fact there was a time that subscriptions for software were virtually unheard of.

On a lower level, all that matters is the numbers. If your average customer stays subscribed for 24 months, then charging a lifetime fee equal to 24 months is equivalent to a subscription model. At that point it's irrelevant what's "sustainable" since 24 months is the max you can expect to charge on average anyway.

I don't think it's that unusual. It seems to me just to be a narrower version of panpsychism:

https://en.wikipedia.org/wiki/Panpsychism

My brain can only generate electrical signals. My hand responds to electrical signals and can interact with the real world. The two together can do more than just what my brain alone can do.

If you don't trust a particular brain, don't put a gun in the hand which is connected to it. If you don't trust a LLM, don't connect it to a harness which has access to your production database and only recent backups (https://www.theregister.com/2026/04/27/cursoropus_agent_snuf...).

Better than before, yes. Good for general legal work that doesn't require robust legal research, yes. Sufficient for full legal research, no.

The problem is that "a lot of case law" isn't enough case law. You need close to everything. Otherwise this can happen: Canlii case X -> Legal principle Y. Westlaw case Z not on Canlii -> X overriden, Y no longer good law. Or you might simply not find a case which cogently supports your argument, when one does in fact exist. Or, conversely, you are unaware of a detrimental case which your opponent knows about because they have Westlaw.

In theory, any member of the public can obtain a judgment by applying for one at the court and paying a fee. That's fine if you just need a one-off judgment, don't mind paying the fee, and you're not in a hurry. It also assumes that you know which case you need.

For realistic legal research, you might need to wade through dozens of cases just to even know if any of them are relevant, you might have a deadline of tomorrow to get it done, and you might not want to pay that fee for a bunch of cases that you aren't going to end up needing. Only a company which already has a comprehensive copy of virtually every important case can help you here.

A typical workflow for a complex piece of legal research might look like this:

1. You need to research a legal topic.

2. Do some Googling, or chat to your LLM, to get a rough overview and some pointers for further research (but don't completely rely on what you find).

3. Read some professional content (e.g. Practical Law articles relevant to the topic, or a legal textbook).

4. Read the relevant legislation.

5. Use a legal database to download all the cases you found from steps 2 and 3 which seem like they might be relevant.

6. Use a legal database to download all the cases which cite the relevant legislative provisions you found in step 4 and seem like they might be relevant.

7. Use the legal database to confirm that those cases are still good law (not overridden or criticised by a later case).

8. Skim read them, discard those that turned out to obviously not be relevant.

9. Read the remaining ones more closely.

10. Note any useful-looking cases which are cited in the ones from step 9, and recursively work your way through those cases as well.

Relying on court-provided copies of judgments won't realistically help you with most of these steps.