Calculating the digits of pi seems like a poor benchmark for comparing various languages in the context of backend web application performance. Even the GitHub readme points out the benchmark is entirely focused on floating point performance.

This is the way.

That’s correct, it is just plain text and it can easily be spoofed. You should never perform an auth check of any kind with the user agent.

In the above examples, it wouldn’t really matter if someone spoofed the header as there generally isn’t a benefit to the malicious agent.

Where some sites get into trouble though is if they have an implicit auth check using user agents. An example could be a paywalled recipe site. They want the recipe to be indexed by Google. If I spoof my user agent to be Googlebot, I’ll get to view the recipe content they want indexed, bypassing the paywall.

But, an example of a more reasonable use for checking user agent strings for bots might be regional redirects. If a new user comes to my site, maybe I want to redirect to a localized version at a different URL based on their country. However, I probably don’t want to do that if the agent is a bot, since the bot might be indexing a given URL from anywhere. If someone spoofed their user agent and they aren’t redirected, no big deal.

User agents are useful for checking if the request was made by a (legitimate self-identifying) bot, such as Googlebot.

It could also be used in some specific scenarios where you control the client and want to easily identify your client traffic in request logs.

Or maybe you offer a download on your site and you want to reorder your list to highlight the most likely correct binary for the platform in the user agent.

There are plenty of reasonable uses for user agent that have nothing to do with feature detection.

JSON Problem Details

https://datatracker.ietf.org/doc/html/rfc9457

• It has a specification, so a consumer of the API can immediately know what to expect.
• It has a content type, so a client sdk can intelligently handle the response.
• It supports commonly needed members which are a superset of all of the above JSON examples, including type for code and repeating the http status code in the body if desired.
• It is extensible if needed.
• It has been defined since at least 2016.

This specification’s aim is to define common error formats for applications that need one so that they aren’t required to define their own …

So why aren’t you using problem details?

Its use looks contrived to me on the linked GitHub page. The comparison with @ and # is flawed because those symbols are part of the resource name, whereas here the symbol is superfluous. It’s like adding a 🌐 in front of every web URL.

This isn’t the evolution of C at all. It’s all just one language and you’re simply stuck in a lower dimension with a dimensionally compatible cross-section.

I’m sure the original comment had incorrect units as used, but this explanation that cumulative units “can’t peak” seems wrong.

If you consider the total stored energy (Wh) over time of a solar-battery system under load, there certainly will be peaks or, in other words, maximal excess capacity of the system.

So no, it’s not impossible to define a unit of Whp as such. “Cumulative” and “momentary” values are not exclusive and also do not have any bearing on whether a function of such values has maxima and minima.

Those companies aren’t “the Internet.” They’re products connected to the Internet.

The OP argument is like saying the Internet is dead because Netflix is down.

Doubtful. By far, most servers responsible for Internet traffic are not running crowdstrike software.

This incident was a bunch of fortune 500 companies caught with their pants down.

Isn’t it available on PS5?

Thanks for the clarification and I believe I misunderstood your original comment.

To add to your list there is an often underutilized feature of GitHub for discussions too.

You mean pretty much a single GitHub account?

Also your quick question may have already been asked and answered but difficult to find on Discord. Or if it hasn’t been asked yet, now a future person can’t discover the same question easily. So either way you’re just wasting other people’s time.

The distinction is web workers and offline mode.

It means your PWA can preload everything it needs to run offline, and you can actually use it offline. That is different from a “cached website” which can only cache the pages you’ve already visited and otherwise does not allow you to update data locally.

Yes, although that recently changed in the EU (only) with the Digital Markets Act.

deleted by creator

Really interesting! I wonder what would happen if you combine these two properties. Suppose some length of the middle is all walls, and the hooks are infill, or vice versa. Is there an optimal mix that maximizes the weight it can support in your testing, or have you found the optimal configuration (with infill along the entire length) already?

I recently went through these exact pains trying to contribute to a project that exclusively ran through Discord and eventually had to give up when it was clear they would never enable issues in their GitHub repos for “reasons.”

It was impossible to discover the history behind anything. Even current information was lost within days, having to rehash aspects that were already investigated and decided upon.

You can also mark designs as ready-only and they no longer count, so this limit is really 10 concurrently editable designs. I just keep everything read-only unless I’m actively working on it.

You’re right, “pounds” is ambiguous.