djray

Unrelated to the subject matter, but something that I never fail to appreciate is just how well-written the majority of Cloudflare's posts are. (There was an article on Merkle Tree Certificates which was phenomenal.) There is real skill in creating an informative work which condenses complex technical subject matter into something that a technically-inclined non-expert can understand.

Could someone knowledgeable please explain why an AI-focused CPU is superior to a GPU-based solution with an ARM CPU driving the high-level operations, please, especially when the RAM isn't on-chip?

I know that for GPU's the model weights have to be transferred over the bus initially, but that only has to occur once for inference use cases, so is the Fujitsu system more about training scenarios? Or is the focus more about efficiency, as these are ARM-based cores with AI additions?

They misspelled their own company name:

"...working together to bring Mistal’s scientific innovations to consumers around the world"

A quick proof-read wouldn't have gone amiss here.

I also fail to see how privacy is enhanced by sending private browsing data to a cloud service which then forwards it to an LLM, in addition to storing 'memories' and dredging through my browser history.

No, the model has answered correctly. Your question is poorly phrased (possibly deliberately).

Your question would correctly classify the user's input as requesting a human support agent, but at an indeterminate time.

If you wanted to determine whether the user wants to speak to a human support agent immediately, you would have to correctly qualify your question, e.g. "Does the user want to speak to a human support agent now?". You could have another question which is "Is the user requesting a call-back from a human support agent?". Or you could have a multiple choice query which would filter the conversation into one of a number of pre-written possibilities.

This is nothing to do with accuracy or hallucination. It's a different method of interacting with the model where you are relied upon to be precise.

Your default should be WCAG-compliant. That's the whole point! A visually-impaired user shouldn't have to customise your site for it to be readable. Your site will be failing some accessibility metrics until you do that, and that will affect your search ranking etc. Plus it's generally a good audience-friendly thing to do.

I was aware of the poll, but putting that up after the fact and it being only about the timestamp is a bad signal, too. It says that you're willing to pull the rug on whole sets of features at a whim and just because _you_ think it's the right thing to do. If you're trying to foster a community, I'd argue that this is not the best approach. These sorts of things could be reversible experiments - such as a banner at the top of the page saying "We're trying out removing timestamps and counters like likes! Click here to give us feedback or to switch back to the old UI." And then you keep track of everyone who switched back or re-enabled the feature you're fiddling with. Or you let people switch for a while and give their opinion after the test period.

Her playing at Glastonbury here in the UK only seems like the other day, but I just checked and it's been _12 years_! She played her most popular songs and the audience treated her like the star she was. What an incredible, talented, kind-hearted woman. An inspiration to so many for all the best reasons.

I agree with removing the obvious dopamine-related signals, but removing timestamps is a mistake, as they are vital for technical and news-based posts. They're a valuable relevance signal in many cases, not 'noise'. At least make them available on-hover or as a user option. Yes, you could try with a 'limit to historical posts' option, but that's going to be difficult as some topics move a lot faster than others, e.g. current affairs versus web standards.

This sort of unilateral action-before-asking is imo not a great signal to send out if you're trying to grow a platform. If you're going to run experiments, let people know first.

Could I also suggest making the comment text size larger (it's smaller than CSS 'small'), changing the typeface to be proportional, and most importantly making sure the contrast between foreground and background elements is WCAG-compliant? Most of the text is less than 3:1. Currently the site may be quite challenging to access for a visitor with visual impairments, and I think many such users would enjoy a site such as this if it were more accessible. Thanks.

"If the online check fails and you’re otherwise online, it gets revoked"

That's not being offline ;)

> If you are online, and the rights service is failing, it will revoke your key.

Do you have evidence of this? I've played Xbox for 25 years and never seen this.

One would hope that you change minds and differentiate yourself through the strength of your argument, rather than the anfractuosity of your prose or a propensity for sesquipedalian verbiage.

Clarity does not equate to genericity. I am regularly struck by clear writing that is both lucid and powerful without resorting to ten-dollar words or tortured syntax.

The fact that AI text is often so easily spotted is a clear sign that so-called 'slop' is not the same as a writing style focused on brevity and understanding over florid meanderings.

They aren't equal, as the faster version does an unconditional memory write instead of only writing to the array if the condition is satisfied. The compiler is strictly forbidden from turning a conditional write into an unconditional one.

Large organisations have advocacy, support and friendship groups for many underrepresented or protected groups, such as those for religions, mental health issues, physical disabilities etc. I imagine this is simply one of those internal group's organisational repos.

Just fucking use the language appropriate to the task you're trying to accomplish.

Just fucking use the language your colleagues can understand and support for the next few years.

Just fucking use the language with the framework and tooling you need to get your job done efficiently and effectively, and one at the appropriate level of abstraction for the project.

Just fucking use the language which AI agents can read and write well, because we're in the End Times and this stuff matters.

Just fucking use the language with great testing and CI/CD support because you'll be spending longer supporting your code than writing it.

The skill is choosing well, and a key realisation is that it's never a one-size-fits-all thing. That's why an article like this is less than helpful, gosh darn it.