maybe a niche use case but i've found it's perfect to store & query random trivia/gameshow questions based on filters for my personal clones of things like Family Feud and Jeopardy

well, i also have to type "rhombus language" to get relevant results for the rhombus language

i think (especially on HN) "X kills Y" usually means X owned/controlled Y and are ending support or whatever. e.g. "Google kills Glass" (for more, see killedbygoogle.com) or "Microsoft kills Skype" (for more, see killedbymicrosoft.info)

inaccurate, i don't have to go three screens deep into a modal to choose only necessary cookies

The best one now is “Read for free” (give me all the trackers) or join a subscription and you can opt out. Pretty much every news / media site now

That one is honest at least, makes you aware that you're the product.

I respect it, even though courts keep ruling that it's illegal (because it's not freely given consent if you are giving something in return for it)

If this were true, it would be great, but in my experience, paying for a subscription just emboldens companies to collect more data

look at Atkinson Hyperlegible? commissioned by the Braille foundation for low-vision readers which means it's very readable

Huh, I'm positive this was one of the first I considered (or perhaps it was a different dyslexia font) but I can't find the reason why I would have preferred PT Sans over this. Each has some pros and cons: PT Sans has same-width digits; Hyperlegible has a nicer-looking Q (imo); PT Sans has a normal-looking zero (not struck); Hyperlegible has a normal-looking 'fi' combination (no ligature that merges the two characters into a new one); Hyperlegible has a 6 distinct from an inverted 9; PT Sans needs a bit less horizontal space. The font specifically designed for accessibility should be the easy winner if all else is equal anyway

They apparently released Hyperlegible Next in 2025 which, flipping between tabs on Google Fonts (since the original website doesn't show the fonts), is nearly identical but has five new weight settings (nobody should imo ever use thin fonts though, it noticeably harms readability for me and my sight is only the tiniest bit below normal vision, but ok it's an option) and improved kerning (the original font had extremely little space between 'll', for example)

The 2025 version sadly doesn't ship with my version of TexLive, but the original (from 2020) already does so that makes it easy to use as well! Cool stuff, thanks for the tip :)

never underestimate the monetary inefficiency of the military industrial complex

And useless, prolonged wars are good for business.

already posted at https://news.ycombinator.com/item?id=49162653 which is itself a dupe but that was the first one posted today

i'm assuming this is written with LLMs given the writing on that page and the nature of the other "products" on that website. i would not call that hand-written, as the page does in the second paragraph

I did use LLM for the landing page since I don't have much time on it. The browser however not that much. I did use claude and my own cwcode to help developing this, but a lot of times the zig code had to be written by hand. Hope this answered your question.

this admittedly makes it even a harder sell to have so little (any?) source code available on github, gitlab, codeberg, whatever.

what's the deal with that? why is Google Drive zips your main distribution method, with no source available?

and finally: are you going to change this?

spotify embed, probably?

the given complicated version's complexity actually just comes from the fact that it's a "more correct" way to write a hello world program, as it manually acquires the stdout File object and acknowledges that printing to stdout can fail. the complexity has nothing to do with stdout vs stderr, you could just use `.stderr()` instead of `.stdout()` (same "friction", it's even the same number of characters). `std.debug.print` is only meant for debugging/development as it gets stderr for you and discards the errors that could happen when writing to stderr.

I meant that the convenient interface only works for stderr. So you aren't accidentally sending debug messages to stdout and if you want to send bytes to stdout you have to do so intentionally and use the right interface.