All code is technical debt.

If rsync releases used to have 500 lines changed and 5 bugs in and AI-powered rsync releases have 50000 lines and 500 bugs, it's the same bugs/line but much worse experience for the user?

I've not looked into the details of this case and I do use AI assistance coding at work but in my experience, the problem is that it's too easy to write lots of code and therefore hard to review the huge volumes of code and this analysis will ignore that?

edit: actually your table shows there weren't unusually large numbers of commits in this release, so perhaps my initial skepticism shows a bias I have?

The UK's NHS is not why it's not taking part in this mess.

I don't notice "disjointed communities" I just look at the posts from people I follow without knowing which server they are on. I'm aware you can see a list of posts on your local server but I imagine people on most instances (unless the instance has a strong theme like for people from a particular location) never use it.

It's Arduino based and it turns out the iCal format has a lot more complexity than I'd guessed so there are still bugs/incorrectly shows some events but it mostly works for me. I work on it very intermittently over a few years and find it quite cathartic.

It's cool having my code hung on my wall. https://github.com/jonquark/InkyCal

I'm confused

In more complicated situations (e.g. "outgoing" persistent messages buffered for individual clients (i.e. each client has a "message inbox"), Kafka is less obviously useful (it's an anti-pattern to try and random-seek the messages from Kafka topics as clients connect). In this kind of pattern, the main architecture pattern I see are clients partitioned across (highly available) MQTT brokers. If the messages come from MQTT clients directly to other clients (e.g. instant messaging (Facebook Messenger uses MQTT), having these broker in a cluster sharing a topic tree is very useful.

If the outgoing messages don't get buffered whilst the clients are off-line (e.g. because these are responses to client requests) then you don't need each client to be routed to a "home" broker that buffers the messages - it can connect anywhere.

It all depends on the shape of the message flow you're designing the system to support (but to say MQTT is a toy for small numbers of topics as it seemed to me that you argued up-thread seems misguided).

(disclosure, I work on Eclipse Amlen and it does not - but people often rig it up to a subscriber that funnels (some/all) messages into databases

Disclosure: I'm biased - I've worked on the MQTT spec and I'm the lead for Eclipse Amlen

Comments URL: https://news.ycombinator.com/item?id=31203114

Points: 2

# Comments: 0

The Standard Model is built out of quantum field theories that take as a given our experiment results that matter on quantum scales is unlike the "large scale" matter we see around us.

The problems described in the articles are unexpected results that we see in our experiments compared to the Standard Model, "weird/nonintuitive" aspects of modern particle physics would be a separate article.

(disclosure: I work on Amlen)