Hacker Newsnew | past | comments | ask | show | jobs | submit | maxbond's commentslogin

I got 42. I was very impressed by how it handled more and less specific categories. It also understood rotifers were a microscopic animal, which I half expected not to work. Great project.

We should be friends. I got 47. In my defense, I was tired.

I was the first to post my score and I thought I did pretty well. Pure hubris! Looking forward to brunch (/j, I'm pretty far away).

Imho it's pretty messed up that their translation tool doesn't actually translate the page and only translates one element. For the most part the site is a lark and the text unimportant. But the banner disclaiming any affiliation with any meme coin really ought to be translated.

https://icannwiki.org/.cat

> Administered by the non-profit Fundació puntCAT under the oversight of ICANN, registrations are available only to individuals and organizations demonstrating use or promotion of the Catalan language and culture.


Is that available for every country root server?

As far as I can tell, there is no rule requiring this wiki to be kept up to date (it's not run by ICANN, though they sponsor it), but I've had good luck with it. The wiki is updated fairly frequently: https://icannwiki.org/Special:RecentChanges . I wasn't able to find a list that proves it covers every TLD but there are about 9x as many articles as TLDs, so I think it's likely. Someone with better MediaWiki chops could probably figure it out. I think that information is there I just don't know how to access it.

ETA: This category lists 314 ccTLDs.

https://icannwiki.org/Category:CcTLD

There are 316 ccTLDs. So; it's either missing 2, or they are documented but not in the right category.

If you're looking for an authoritative source I think you should check out the PSL, but it doesn't have the right metadata to answer your question. You'd need to supplement it somehow.

https://publicsuffix.org/


We can talk about C's demise after the last COBOL application is retired.

One of the reasons why Rust is taking over userland is that it's getting more and more difficult to find people willing to maintain a C code base—especially an old one—while there's no shortage of kids willing and eager to hack in Rust.

C will end up in exactly the same place as COBOL: there will be applications that depend on code written in it for decades to come, but they will be maintained by very well-paid grognards simply because those are the only people who know how, and are willing (for a steep price), to maintain them.


Maybe. I think C will continue to have relevance in certain niches like embedded development, and that efforts like Fil-C will quietly carry the torch for a long time. C will also continue to have an important role in bootstrapping.

I generally I don't like the "Rust is killing C" meme because a.) I don't believe it b.) C doesn't need to die for Rust to succeed and c.) it leads to language wars and hard feelings. Rust doesn't really do what C does; it's not a lingua franca among architectures. They compete in some niches and not others.


My law of headlines is, "don't take them too seriously, don't develop too many expectations about the article, skim the article (or the comments) to know what it is about and whether it is worth your time".

Razors should guide, not replace, your engagement with the subject matter.

We don't know it was the parents. Could've been a babysitter. Could've been a grandparent. New parents often have help.

> If this is in the breastmilk, ...

Note that you and GP are talking about different values of "this." GP is talking about codeine, you're talking about morphine. The difference between the two is at the crux of this article.


> GP is talking about codeine, you're talking about morphine. The difference between the two is at the crux of this article.

It appears that they didn't really read the article before commenting.

The entire point, the damning evidence is that the child that died had codeine in his stomach, which he absolutely couldn't get from breast milk.


https://en.wikipedia.org/wiki/Character_limit#On_Twitter

> In November 2017, Twitter increased its character limit from 140 to 280 characters. In 2023, Twitter boosted the character limit for Twitter Blue subscribers. In February, it was increased to 4000. In April, it was again increased to 10,000, and in June, to 25,000.


The character limit is just whatever the longest tweet Musk wants to send.

I remember 280, but jesus things clearly got out of control.

Not really. If the solution has less complexity than is inherent in the problem, it can't possibly work. If the solution has complexity equal to or greater than the complexity inherent in the problem, it may work. So if you see complex code handling many different edge cases, you can take that as an indicator the author understood the problem. That doesn't mean they do understand or that the solution does work; only that you have more confidence than you did initially.

It's a weak signal but the reasoning is sound.


Everything should be made as simple as possible, but not simpler.

Code has a minimum complexity to solve the problem


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: