seabass

It’d be fun to get to try all the words. Maybe finishing the whole game as fast as possible could be the goal, rather than hitting 30s per word?

This is so fun! It would be cool to reuse the replay functionality in order to see how the top scorers managed to get such good scores.

An app ui that can be modified by end users is a really cool idea. I hope to see that in more apps!

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.

Have to love their demo use case: React -> Solid migration

The video you linked is currently private

This is rad and made me smile

Heartily second that! It was cool to see a combination of DOM, SVG, and canvas visualization all in use for this post.

And the battery or SSD?

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.

A thousand and one paper cuts. I feel like this shortsighted decision making will cost Apple so much trust in the long run.

Feels short sighted. Every such change gets me closer to ditching the ecosystem altogether.

Wish this were built into the OS! Love the idea

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.

You can compare the writing style from the earlier articles like this from 2020, pre-GPT.

https://andreacanton.dev/posts/2020-02-19-git-mantras/

Strongly disagree. If you read enough of it the patterns in ai text are so familiar. Take this paragraph for example:

Here’s what surprised me: the practices that made my exit smooth weren’t “exit strategies.” They were professional habits I should have built years earlier—habits that made work better even when I was staying.

“It’s not x—it’s y.”, the dashes, the q&a style text from the parent comment, and overall cadence were too hard to look past.

So for a counterpoint about the complaints being tedious, I’d say they are nice to preempt the realization that I’m wasting time reading ai output.

Looks really cool! Love the artwork. Right now the video in the readme doesn’t render on github, though. I had to manually download the mp4 from your demo folder to view it.

I’d expect that the “shut up and do as I say” approach would add more combativeness to the ai, increasing the likelihood that it refuses. Instead, bringing your initial request into a new chat context that hasn’t already been poisoned by a refusal would probably work.

I'm curious how you build something like this. I see file types in the network tab which, as a web dev, I've never worked with before. ktx2 and drc extensions, for example. I'm also seeing some wasm and threejs. Is there an engine that outputs these things or is it more of a manual process to bring everything together?

On the other hand, I'm so glad it didn't. I enjoyed a few minutes of exploration before realizing what I was meant to be doing.

Really beautiful! Love the artwork and the fact that this runs so well in the browser. Was surprised to realize it was multiplayer!

how easy is it to administer for clients outside of my network or possibly even outside my country?

You can run Jellyfin in any docker container. If you want to run it on a NAS in your home office and put it on the internet through ngrok or tailscale, you totally can. But you can host it pretty much wherever.

how good is the app support? I transcode all of my media to AAC and h264 for compatibility

The official clients are just ok. They'll support all the file types you'd expect, but they're fairly slow and not great at streaming 4K. I pay for a client (Infuse Pro) that addresses a lot of those pain points, but it's been relatively poor at auto-detecting tv show metadata, so I'm still in the market for an app I'm happy with. Ideally an open source one.

- what about for streaming music?

Technically works, but whether it's a good experience depends on the client you're using.

- what do you like the most about jellyfin

Easy to set up. Great plugins for finding subtitles/artwork/metadata. Open source with good docs. Works with lots of clients. Easy to create and share accounts, and has fun features like synced remote viewing parties.

- what do you miss most about Plex?

The ads. jk never used it.

The information I have on this could be outdated, so take this with a grain of salt, but it used to be the case that in hot code paths the presence of a try/catch would force a deoptimization whether or not you throw. The optimizing compiler in v8, for example, would specifically not run on any functions containing try/catch due to its inability to speculatively inline the optimized code. If you're feeling up to it, you can prove whether that is still the case with `d8 --allow-natives-syntax --trace-deopt ./your-script.js` and sprinkle in some `%OptimizeFunctionOnNextCall` in your code. I did a quick search for `try {` in the zod 4 source and didn't see anything, so I suspect that the performance issues surrounding try/catch are still at least somewhat around, unless they are simply avoiding try/catch for code cleanliness which could totally be the case. Regardless, I'd encourage you to look into whether plain old boolean return values in your validators would work for your project. Just include the `throw` part without all the `try/catch` and the code itself will likely be simpler, faster, and easy for the JIT to optimize. Good luck on those benchmarks.

I was surprised by the source including a bunch of try/catch, which results in deopts for that code path as far as I understand, given that the stated benefit over Zod and other validators was that this should be run in performance critical code. I’d be curious to see benchmarks that show whether this is faster than zod, valibot, and zod4 mini in hot code paths.