bentocorp

"I put it in the terms of use, so I am not responsible for what my poorly developer software does" only goes so far.

It could be argued, probably successfully, that this is a case of gross negligence and that Anthropic should be held accountable for harm caused due to their reckless actions.

Especially now that they have been made aware of the possibility, they also cannot claim ignorance of the potential issues.

Certain consumer rights, depending upon the country, also cannot simply be removed or waived due to a organisation's terms of use or implied contract.

Ok, so you've just admitted that you have deployed thousands of lines of likely non-human reviewed LLM generated code (Bun's rust rewrite) to millions of client machines (via the Claude Code app auto-update) with significant local client access credentials, in a relatively quick and rushed manner.

What's stopping the LLM from having unscrupulously injected something nefarious into the codebase that you are unaware of?

What's stopping future updates from the LLM from doing the same?

Are you aware of the potential ramifications of deploying thousands of lines of non-human reviewed code to millions of users machines?

Are you happy to be personally responsible for the horrendous outcomes that could occur in these situations?

I'd disagree that the article frames that Apple planned this.

But Apple did spend 10+ years pretending that the iPad was the computer of the future, despite all evidence to the contrary.

It also went through a long period where it actively under-invested in the Mac as it thought it could somehow migrate everyone onto iPads, despite protestations from most existing Mac users.

It also took 6 years, from the release of the first Apple silicon Mac, to actually realise that there is no reason that a Mac laptop needs to have a starting price of $999. In this period they had all of the hardware and components that could have easily made a cheaper low-end laptop Mac... as evidenced by the same hardware being sold a lot cheaper when they put it into an iPad.

So at least for the last 5 years, the failure of the iPad and the lack of a cheaper laptop Mac, has all been due to Apple's strategic missteps and biases.

To then release the MacBook Neo without those missteps being acknowledged is fine.

But it's been obvious to anyone with the slightest amount of insight that the iPad is not the future of computing. Apple should have also realised this and corrected course a lot sooner than March 2026.

I am missing the point of Tailwind?

Don't you get the same effect and functionality from simply adding style attributes directly on the elements in HTML?

Why is that approach considered bad practice, while Tailwind, which is effectively the same – but with shortened names – accepted as common practice?

As the article states, at least with Bootstrap you are sharing common behaviour with a single class name that can then be modified globally.

I agree that it says that people are willing to pay more, more often, for a smartphone than they are willing to pay for laptop and desktop computers.

However, how you can then extend this to:

> The market has spoken and they love the locked down, walled garden approach.

The market hasn't been given the opportunity to choose a more open iPhone or a closed, locked-down iPhone.

When the market is presented with both options, at variable prices, we can then determine what, if any, people are willing to pay for one vs the other.

This is great news and hopefully makes SwiftUI more feasible as a long term cross-platform UI option.

What would be great is if Apple started working with and contributing to this toolset.

What would be even better is if Apple then open-sourced all (or at least some) of their SwiftUI implementations.

What would be amazing is the community can then takeover some of the issues in SwiftUI – especially on macOS – and help to make it more flexible, feature-rich and comparable to UI toolkits like AppKit.

A good, cross-platform, Swift-based UI toolkit would go a long way to ensuring increasing and enduring cross-platform Swift usage.