3,952 karma · joined March 30, 2022
multilingual dictionaries (WIP): https://yap.town/d/
My website: https://chadnauseam.com My public key: nauseam.eth my email: andre@popovit.ch my discord: https://discord.gg/mpgqfsH
Probably, but I doubt linux wants it either. People might think it's some official linux product.
Personally I like the default font. It looks weird to have my crappy doodles next to a normal computer font. The default one is very legible but has a style (and ligatures) that make it feel not too neat
It reminds me of how peer review is supposed to be blind, but certain authors like Simon Peyton Jones have such a distinctive voice that surely reviewers instantly know when a paper is by him. The models have been successfully made to talk in a particular way, and it's very clear once you becomes familiar with it. My guess is that most HN users are not familiar and I just sound like a crazy person to them
The author admitted it in another comment anyway https://news.ycombinator.com/item?id=47494833
1. you can see the frequency of each meaning of each word. For example, the french word "bois" commonly means "drink" and rarely means "wood": https://yap.town/d/french-to-english/bois/
2. Each meaning also comes with a huge number of example sentences, taken from "real" sources (movies mostly)
3. It also has definitions for common phrases and constructions. For example, "c'est" is technically two words in french, but you should just learn it as one unit, so it gets its own entry: https://yap.town/d/french-to-english/c-est/
You can also see a list of phrases for any language of interest: https://yap.town/d/french-to-english/top-1000-phrases/ . The phrases were discovered via the "unigram" tokenization algorithm (originally invented for training LLMs!)
Something remarkable about the phrases is that you can often understand the meaning of a sentence just from the meaning of each phrase in it. The concatenated phrases sometimes even form grammatical english. And of course, if the same phrase has multiple meanings, those are separated and have their own example sentences, just like the words do.
^[1]: And by "I", I mean I wrote code to ask an LLM to generate each dictionary entry.
> Ten years left to redesign lithium-ion batteries
> Reserves of cobalt and nickel used in electric-vehicle cells will not meet future demand. Refocus research to find new electrodes based on common elements such as iron and silicon, urge Kostiantyn Turcheniuk and colleagues.
I notice that the article was published in 2018. So I guess we only have to wait two more years to decide if it's right or not. Will we be out of cobalt and nickel by then? I'd be happy to take a bet with you, assuming you stand by the article you cited.
Is this problematic for WASM implementations? The WASM spec requires IEEE 754-2019 compliance with the exception of NaN bits. I guess that could be problematic if you're branching on NaN bits, or serializing, but ideally your code is mostly correct and you don't end up serializing NaN anyway.
Obama couldn't change that, so the ACA redesigned the system to work with it. Despite being called insurance, health insurance is no longer really viewed or designed to be any kind of insurance. Instead, it's supposed to be Netflix for healthcare. You pay a flat rate, and then get unlimited healthcare. Obviously, the issue with this is that if you don't need healthcare you can just not sign up for the subscription. So the ACA tried to solve this by requiring everyone to sign up. Once everyone is required to sign up, it's not right to discriminate against preexisting conditions. It may not be an especially good system, but it is coherent.
You see what you choose to focus on. I come across many people who are excited about the possibilities of AI-assisted coding, who are frustrated by its limitations, who share strategies for overcoming or avoiding those limitations, and s on. For a concrete and famous example, I would put Andrej Karpathy in this category. Where are you looking that you're not finding any of these people? linkedin?
I'm sure this is not a remotely new idea, but I'm having fun with it. I also like that I can see how common every form of every word is. I was surprised to learn that almost none of the most common words are nouns. And in my internal tools I can filter by movies released a certain date to track changes, which is neat.
I think cloud-first design is natural because webapps have nowhere good to store state. On Safari, which is the only browser that matters for many web developers, everything can be deleted at any time. So if you don't want to have a horrible user experience, you have to force your users to make an account and sync their stuff to the cloud. Then, the most natural thing to do is to just have the user's frontend update when the backend updates (think old-school fully-SSR'd apps). You can do much better than that with optimistic updates but it adds a lot of complexity. The gold standard is to go fully local-first, but to really do that right requires CRDTs in most cases, which are their own rabbit hole. (That's the approach I take in my apps because i'm a perfectionist, but I get why most people wouldn't think it's worth it)
With the files API, apps could actually replicate the microsoft word experience of drafting a file and saving it to your desktop and praying that your hard drive doesn't fail, but despite offering great benefits in terms of self-custody of data it was never a great user experience for most people.
Don't get me wrong, rust has plenty of "weird" features too, for example higher rank trait bounds have a ridiculous syntax and are going to be hard for most people to understand. But, almost no one will ever have to use a higher rank trait bound. I encounter such things much more rarely in rust than in almost any other mainstream language.