it keeps saying "failed to load" for me. through the magic of the developer console, i can see that the api calls are working but the actual image requests are not. it seems that this is a case of an overzealous cloudflare turnstile setup since if i open the image links in a new tab and pass a challenge i can view them.
no, but the documentation for packed structs gives the list of allowed field types. it's also not documented that packed union fields must be valid packed struct fields but people may be able to assume that
zig does not allow arrays in packed structs/unions specifically for endianness reasons (there may be other reasons as well but endianness is what i know of)
the triple slash is only for doc comments, not normal code comments - those are still double slashes. also, why would you want to grep for escaped backslashes?
it's unclear to me whether they were actually told to lie or just told to survive / convince others. either way it is somewhat coerced but i think there is still a difference
the maintainers seem happy, especially now that CI is actually working how it's supposed to. but a non-rare complaint in the Zig discord is how slow Codeberg can be, and other things like the lack of codesearch hurt as well.
and when people talk about zig, they don't usually mention that zig used to have goto, casting syntax like `T(val)`, a rule that said you couldn't pass containers by value, language-level async, some truly awful syntax for what is now `try` and other operators, etc. both languages took time and work to realize that these features were not for them. very strange to deny that.
also, nitpick: they said zig has been around for ten years. this is, strictly, correct. the zig project has existed for ten years, just like how rust has existed for about 20, now. a project still exists if it is pre-1.0. nobody was talking about versions before you.
"technically" usually means something like "strictly", not "by a completely different metric". work takes time. zig has had a decade of work put into it.
`-ai` isn't actually a special case that removes the ai overview, it just adds a search filter which removes all results with the word "ai". afaik the ai overview is simply less likely to show up with a filtered search
`&udm=14` just sends you to the "web" tab of search, which does remove the AI summary, but you also lose the widgets that google puts at the top of search, if you like those (weather, calculator, games, etc). one of my friends recently found that you can add a short invalid filter parameter like `&tbs=1` and it'll give you the main search with no AI but with those widgets if they would normally appear. you do still get the "People also ask" section, but that's probably easily removed with an extension or user script
interestingly, MDN web docs claims at the top of the Web Serial page (https://developer.mozilla.org/en-US/docs/Web/API/Web_Serial_...) that Chrome does not support it, even though the support table at the bottom shows that it supports all of the features (Firefox doesn't) and has for longer than Firefox
well, it is in the "thoughts" section of the author's website. maybe it doesn't belong on HN, but the person who posted it is not the author, so take it up with them. anyway, i agree with most/all of the complaints but if a valuable point were to be made it is probably the funding point. why does this need money?