Mercure’s spec has a bit more meat on its bones in terms of providing an adequate description of the protocol.

From https://mercure.rocks/spec :

Mercure provides a common publish-subscribe mechanism for public and private web resources. Mercure enables the pushing of any web content to web browsers and other clients in a fast, reliable and battery-efficient way. It is especially useful for publishing real-time updates of resources served through sites and web APIs to web and mobile apps.

Subscription requests are relayed through hubs, which validate and verify the request. When new or updated content becomes available, hubs check if subscribers are authorized to receive it then distribute it.

You are making an extreme assumption, and it also sounds like you’ve misread what I wrote. The “attempts” I’m talking about are studies (formal and informal) to measure the root causes of bugs, not the C or C++ projects themselves.

I think you’re talking past the point I’ve made.

The point I’ve made is that the bulk of these attempts don’t even consider onboarding basic static analysis tools for projects. Do you agree?

If you read the post of other studies you’ve quoted, you’d be aware that some of them quite literally report results of onboarding a single static analysis tool to C or C++ projects. The very first study in your list is quite literally the results of onboarding projects to Hardware-assisted AddressSanitizer, after acknowledging that they haven’t onboarded AddressSanitizer due to performance reasons. The second study in your list reports results of enabling LLVM’s bound sanitizer.

Yet, your personal claim over “the lack of memory safety” in languages like C or C++ is unexplainably based on failing to follow very basic and simple steps like onboarding any static analysis tool, which is trivial to do. Yet, your assertion doesn’t cover that simple step. Why is that?

Again, I think this comparison is disingenuous. You take zero effort to address whole family of errors and then proceed to claim that whole family of errors are not addressed, even though nowadays there’s a myriad of ways to tackle those. That doesn’t sound like a honest comparison to me.

Was this thing generated by a poorly trained LLM?

C syntax is simple, yes, but C semantics are not; there have been numerous attempts to quantify what percentage of C and C++ software bugs and/or security vulnerabilities are due to the lack of memory safety in these languages, and (…)

…and the bulk of these attempts don’t even consider onboarding basic static analysis tools to projects.

I think this comparison is disingenuous. Rust has static code analysis checks built into the compiler, while C compilers don’t. Yet, you can still add static code analysis checks to projects, and from my experience they do a pretty good job flagging everything ranging from Critical double-frees to newlines showing up where they shouldn’t. How come these tools are kept out of the equation?

Are you going to post links to all Wikipedia articles here?

What problem do you have with Wikipedia?

I found that it was worth sharing this list of IP protocols because more often than not developers are only faced with two of them, TCP and UDP, but there are over a hundred of IP protocols, most of which are never discussed or see the light of day. One I find particularly interesting is UDP-lite.

“GitUI is amazing, although unusable.”

Ergonomic keyboards are not a result of “the size of the keyboard”, but the shape.

I apologize for the mistake. Even though I referred to size, what I had in mind was geometry/layout.

Without any real studies on it mentioned so far you’re relying on gut feeling and logic here.

Are there actually any studies suggesting that ergonomic keyboards prevent RSI? As far as I could gather, there’s a correlation between higher RSI incidence and keyboard usage, but nothing suggests ergonomic keyboards lead to a lower incidence of RSI.

Not to be a spoilsport, but as I predicted the .NET MAUI community in programming.dev is of course dead on arrival.

The last post was two weeks ago, and the next to last one dates over one month.

There was far more effort invested in requesting the creation of a community than to actually have a community. The request to create the community received more messages than those the actual community received in over a month.

What’s the point of creating these communities?

Wouldn’t wrist position be considered part of your overall posture?

There are far more factors determining wrist position than the size of the keyboard, and only a very small fraction of all keyboard users end up developing any form of issue.

Moreover, I’d wager that the number of people enduring bad laptop keyboards greatly outnumber those developing any kind of RSI issue, let alone those who feel strongly enough to buy ergonomic keyboards.

It would be interesting to see how many ergonomic keyboards end up being snakeoil preying on people with more disposable money than good judgement.