Paywalled.

You need to update again.

This could be the Next.js motto.

You need to upgrade again, and no the docs aren’t finished (and they won’t be before the new new version).

My Umami stats box got "pwned" about 15 mins after the last CVE was published and I spent an hour or so cleaning up that mess and upgrading everything. Not looking forward to doing it again today.

The second example confuses me. The Person type has isCool: boolean, not an explicit true. How does using satisfies here pass coolPeopleOnly?

You can sorta think of `satisfies Foo` as "the type is exactly the literal value, but also make sure the value could be used in the place of a Foo"

Really interested in how you do this. When I as looking into building my own finance-related app, you have to pay a ton to get market data (stocks, crypto, ETFs, options) and connecting bank accounts if it's not for individual use (you still have to pay for individual use, but not significantly as much).

Adding new transports and documentation to my Typescript logging library (MIT licensed), LogLayer (https://loglayer.dev). Just added documentation for Bun and Deno support added some new logging library transports (LogTape), and finishing up Logflare and Betterstack transports so you can send logs to their logging APIs.

It's already happening. There are visual novel groups that take pateron sponsorship to run the script through machine translation. It's now done in giant batches. They're released for free and I am not able to speak of the quality as I've never tried them, but when I see reviews on steam for a VN that has been machine translated, it never results in a good review.

My first thought would be consistency in localization / typesetting. Groups have their own ways of localizing and typesetting content and most likely would not want to share their style guide when they lost out on something they recently translated to a lower bidder.

Isn't it the same issue when a localization team/member with its distinct style decides to get off the train and the next contractor can't replicate it ?

That appears to happen sometimes in the middle of Crunchyroll seasons. Suddenly the translations change. Spelling of names, other things. Jarring.

Yes

This surprisingly made this easy to remember for me.

Unfortunately, the merge sort instructions doesn't make sense to me, specifically step 3.

The key to step 3 (of the merge sort) is the little nx in the middle that tells you to repeat step 3 n times. Each time, you take a right or left branch based on if the new weight from the half plank is lighter or heavier than the current weight. You also have to understand that step 1 means you recursively merge sort each half before you merge the two sorted halves.

It's not a merge sort, it's just a partition. Mark every element greater than your pivot as "move right". Then step 4 marks every smaller element as "move left". Step 5 actually does that.

You don't really need to split that into 3 steps, though it looks a bit more like a real IKEA diagram with the extra steps.

Wrong diagram - “merge sort”.

I also had similar issues and wrote a guide on how to use LogLayer + pino to get server-side logs working properly.

https://loglayer.dev/example-integrations/nextjs.html

Overall, the logging experience in Next.js is terrible, and not being able to chain middleware, even more so.

Really love the idea! I tried going to the FAQ on mobile safari on iOS and can't scroll on the answer sections, so the text is cut off.