I don't really like serif fonts, but the two that immediately come to mind are Noto Serif and IBM Plex Serif. Both are open source. I know Noto Serif is variable, but not sure about IBM Plex.

Both Plex variants are really wonderful fonts

1. It'll become open-source with 1.0, as the article mentions.

2. Just requires someone (or you) to write a kernel for your GPU, which is done in Mojo itself. I'd double check the supported GPUs or if someone else has already done it.

I understand. Until it is open source it's still a blocker for me though.

I watched a community video for the roadmap and it sounds like hardware is not the focus until sometime after 1.0 release. So I think I can assume it'll be a while (if ever) before I can even think about using it.

They may not themselves, but they'll happily sell your info or give it up to avoid losing money to someone who would.

I think there's a middle ground between trying to follow a path you set for yourself and thoughtlessly wandering by gut feeling: set a direction you want to go, not a destination.

You'll find that it doesn't require much thought at decision points to choose the options (in aggregate) that push you in that direction. As they say, it's about the journey, not the destination.

With that said, it's still difficult because you have to learn to forego long term expectations and/or acquire discipline not to just "stay put" lest you fall back into the habit of stressing over end goals or the comfort of a stress coping loop (anime, video games, etc), respectively.

In case I'm not the only ignorant one:

BME = black and minority ethnic

That's real-time rendering though, right? Is there anything preventing it from being pre-rendered in non-real-time first? Or does it have to be rendered in real-time?

I'm not familiar with any of this at all, so I'm genuinely curious.

If the context was to use in a VR/AR headset it has to be real-time. And I guess that use-case, and the related that you interactively want to walk around a scene are two of the main use-cases

I think the best way to consider it.. is as a 3-d cloud of individually addressable pixels. The size of the cloud is dimensions of real-time rendering.

The interesting bit is that it's feasible to render in realtime. We have plenty of ways to render a 3D scene if render time is not an issue.

I've been using Memmy[1,2], which is similar to Apollo.

1: https://github.com/Memmy-App/memmy

2: https://apps.apple.com/us/app/memmy-for-lemmy/id6450204299

No. They're just saying that if they're invisible, most people won't care. They're not saying anything about what should or shouldn't happen.

Why is it that no one comprehends the existence, let alone nature, of _implicit_ statements?

I just checked to see if GameFAQs was still active and thought that Tears of the Kingdom would be a good game to see if there were any active users still making guides.

There's only one...for horse upgrade recipes. I also didn't know that GameSpot acquired them.

I too mourn the lost era of GameFAQs.

I was an active member when GameSpot merged then took over (my account missed the LUE cutoff by less than a year, if you know you know). It was something the owner promised would never happen, and then he repeatedly said it would never go farther then it did. GameFAQers hated GameSpoters. Merging was the beginning of the end IMO, it hurt the community and that was the main thing they had.

> Does that mean it doesn't sync across the internet?

They currently host their own backup node, so it does sync across the internet, but you only get 1GB of storage (or 10GB if you were in the alpha) on their backup node. Once that's exceeded, additional files are only synced P2P.

They're planning on providing extra storage for a cost and soon anyone will be able to self-host their own backup node.

P2P sync over the internet on our roadmap. We plan to release it later this year. Our protocol already supports it, but we need to implement peer discovery.

Right; should have been more specific, thanks!

I meant to ask if the app syncs P2P over the internet, rather than just through their provided storage.

My solution is to have short-lived data so that they can't reach more than a few MBs of memory on my server, but if there's a straightforward way to do P2P across the globe, I'd very much prefer that option. Asking people to believe that I can't look at their (encrypted) data is fine, but preventing me from having their data at all is ideal.

Given what you pointed out, I definitely figure they're not doing WWW P2P syncing, but you'd be surprised the technical stuff you can figure out by just asking someone who spent way too long building it. They're usually happy to tell you all kinds of interesting details (especially when it comes to 'interesting' bugs/workarounds/hacks)!