grodriguez100

The author does not say that you “should not add v1”. They say that versioning is how you change your API responsibly (so, endorsing versioning), but that you should only do it as a last resort.

So you would add “v1”, to be able to easily bump to v2 later if needed, and do your best to avoid bumping to v2 if at all possible.

CLOCK_MONOTONIC is affected by NTP skewing but should still always increase monotonically (i.e. never decrease)

Looks like I misinterpreted both embedded and real-time then.

Sounds very good, and I can see many use cases in embedded systems. But that probably requires 32-bit arm support. Is that planned ?

I don’t think “web searches” requires “a deep level of technical literacy”…

Can’t help reading that as “Skynet” every time.

> I actually set a piece of homework "marking" chatGPT, which went well and students seemed to enjoy!

This. This should be done everywhere. It is the best way to let students see first hand that LLM output is useful, but can be (and often is) wrong.

If people really understands that, everything will be better.

Sure, it may not apply in this specific case. But you said “This is the first I've heard of using an open pipe to poll for subprocess termination” and I was just pointing out that this is a well known technique.

This is actually a well known technique, often called the self-pipe trick. There’s a good overview in the following SO answer from Rich Felker, muslc’s author:

https://stackoverflow.com/questions/3703013/what-can-cause-e...

They actually did B:

“[…] if the environment variable STDDATA_FD is present or set to the descriptor to produce the JSON output on.”

ZeroSSL works very well for me. I found it because it is now the default for the acme.sh client.

Old Macs (pre-OS X I think) used CR only as line terminators.

Right, sorry. Didn’t notice.

a) Correct. b) Not relevant. The license says what it says regardless of what upstream does or doesn’t do. If someone wants to use the code they should comply with the license requirements.

A README is often included with binaries. That’s a good place to include any licensing information.

Indeed.

It is “nice” but that does not make it compliant.

“Linking to a page that includes” is not the same as “including”. I don’t think that the requirement is satisfied.

It is the same license but the copyright notice is different, so no, not sufficient.

I’m browsing from an iPhone in Europe right now and can browse source code just fine without being logged in.

Misleading headline? It links to an unresolved GH issue, so no evidence that there is an actual change of policy (rather than, let’s say, a bug, or a temporary hiccup)

No, VAT is not a tariff. It applies to all goods sold, not only imported ones.

Planned features: acquire JetBrains

(https://wiki.ms-paint-i.de/features)

Looks good to me. Solid product and a solid roadmap :-)

Also I’d be surprised if an average human can even reach 10% of these.

I mean, some humans can score far better. But try picking a random person in the street.

Yes, indeed. And I wonder what this type of question has to do with intelligence. Think of the 10 most intelligent people you know. How many of them know the answer to this?

This is testing “knowledge”, not intelligence. And with access to most of the knowledge in the world and basically infinite memory, that’s not very exciting for an AI.

Sure, but they use the “AI is now available to everyone” to justify the price increase.

Opting out of the functionality I don’t need is not particularly useful (I won’t use it anyway) but the thing is I will be charged for it anyway.

So we don’t want to use this, but there is no way to opt out and we still have to pay X extra per user :-/

Looks great. I am missing an index of existing posts, either on a separate index page or in a sidebar.

That was a fun one but I think they changed it already.

https://www.bbc.com/news/world-asia-66028606.amp

Also the default image host for stackoverflow.

Yes, of course. I was just describing what most existing engines currently do.

> I am so much more used to the short versions hence I prefer `grep -RF` over `grep --dereference-recursive --fixed-strings`. Also, my go-to documentation about these commands (POSIX) doesn't even know about the long options. I know that the advice to prefer the long options is repeated pretty often so it might just be me :)

It is not just you.

I also prefer short options for most “standard” commands (e.g. everything POSIX). I don’t see any value in educating readers in the long options of grep, or ls, or cat.

OTOH using long options may be useful for less common commands, or if the commands are specific to the software the tutorial is about.