It's always so disappointing. This looks genuinely cool, soured by all the little ai artifacts that get hard to look past, like "the circle names what it rests on".
Iosevka is one of those fonts you can tell has had so much work put into it over the years. It is so customizable and works in a lot of contexts, although it’s a little narrow to code in for my taste. I’ve really liked Junicode (serif) for the same reason. Lots of customization options and care in the details.
Pretty close but they forgot the part where I have to install anti cheat, update my drivers and reboot, create an account and link my email, check my email for a code, accept ToS, compile shaders, and wait for more patches to install before playing.
> In plan mode (using CC, or OpenCode) I ask a model to build the foundational knowledge for X topic. I ask it to review the accuracy of the knowledge base it built in the previous step.
> What you get is a beautiful animation that is 100% accurate and free of hallucinations.
The circular cost indicator near the context usage indicator was also removed. It is so much easier to accidentally leave an expensive model enabled now and not realize it until you have blown through the included credits. And it is hard to imagine that that wasn’t the point of the change.
The way you use commits sounds like how I tend to use stacked PRs at work. Good commit hygiene is hard to enforce at a team level, but for whatever reason at the PR level people are happy to write good descriptions and keep the sets of changes tidy.
A few weeks ago Apple had a tiny (<10MB) update for media codecs ready to install on my MBP. I expanded the details for that software update and saw that if I had run it, it would also have downloaded and installed Tahoe. Apple is burning so much trust right now with these dark patterns.
Definitely going to give this a try. One thing I'm curious about--where are the servers? And if I want to choose hosting geographically close to me, how do I do that?
How much is “the public” making? The title of the post says millions. The title of the article says trillions. The second paragraph of the article says not trillions. Sheesh
I love squoosh! It’s been one of the few PWAs I have installed and actually use regularly.
Does anyone know if their optimization methods still best-in-class these days? It’s been good enough for all my practical needs, but I know it’s been around for a while and there may be better techniques for some file types now.
Ah I think I understand now. The return type of createBook is true | Book, which is likely a mistake, but happens to work because when you attempt to spread a boolean into an object it removes itself. But if you were to edit the example to have a stable return type of Book then it would no longer save memory, so perhaps that was intentional?
Love this! Just wanted to note that I think there’s a mistake on the flyweight pattern page’s example. You’re using getting a boolean with Set.has but treating it like a Book (as if you had used Set.get). I also don’t really understand how this saves memory if you’re spreading the result into a new object, but maybe someone here can enlighten me!
I’m surprised by how good it looks. This is really cool! I do feel like the Q and 4 characters need a little manual tweaking since the blur+threshold technique leaves some artifacts in the corners but those are such minor issues given how readable this font is overall. Love it.
It has a bunch of human imperfections, and I love that. The lowercase lists and inconsistent casing for similarly structured content throughout, the grammar mistakes, and overall structure. This article has a totally different feel compared to the newest ones. When you say it’s very similar, what are you picking up on? They feel like night and day from my perspective.