Yeah, that is my understanding, too. Otherwise you’d only want to generate them on the database host, as even with NTP there will be small differences. This would kind of defeat the purpose of UUIDs.
If you’re saying that even without NTP, just by manually setting the time, things will be fine. I mean, maybe. But I’ve seen it far too many times already that some host shows up with 1970-01-01…
For others wondering what’s wrong with UUIDv4:
UUID versions that are not time ordered, such as UUIDv4, have poor database-index locality. This means that new values created in succession are not close to each other in the index; thus, they require inserts to be performed at random locations. The resulting negative performance effects on the common structures used for this (B-tree and its variants) can be dramatic.
I guess, this means with these new UUIDs, ideally you only create UUIDs on systems that are hooked up to NTP, though I guess, it won’t really be worse than UUIDv4 either way.
It’s certainly simpler than Forza et al, but there’s an open-source racing simulator, called Speed Dreams: https://www.speed-dreams.net/
If you watch the “Latest Release” video, there’s some engine sounds in that.
They seem to have a bunch of samples for how different car models’ engines sound: https://sourceforge.net/p/speed-dreams/code/HEAD/tree/tags/2.3.0/data/data/sound/
And then they modulate that in code, based on the car’s speed, gear, turbo etc.:
https://sourceforge.net/p/speed-dreams/code/HEAD/tree/tags/2.3.0/src/modules/sound/snddefault/CarSoundData.cpp#l171
They also do that for gear changes, tyre sounds, collisions and backfires.
From what I know about audio, I would expect AAA games to still use the same approach of recordings+modulations.
While it is possible to fully synthesize an engine sound, it doesn’t help you much with making it sound right in all different situations.
With that name, I hope the guy is also a fan of Minetest: https://wiki.minetest.net/Mese_Block
🙃
We’ve been using Leptos at work, which is a similar framework (and probably shares half the stack with Dioxus).
And yeah, it’s really good. My favorite thing about using Rust for the UI is algebraic data types.
So, in Rust when you call a function which can fail, there isn’t an exception being thrown, but rather you get a Result-type as return value.
This Result can either contain an Ok with the actual return value inside. Or it can contain an Err with an error message inside.
So, in your UI code, you just hand this Result all the way to your display code and there you either display the value or you display the error.
No more uninitialized variables, no more separate booleans to indicate that the variable is uninitialized, no more unreadable multi-line ternaries.
It just becomes so much simpler to load something from the backend and display it, which is kind of important in frontend code.
It’s not a dual-language platform, though. You write the backend and the frontend in Rust. The frontend code is compiled to WASM to serve it to the browser.
Interesting strategy after they already advertised their most recent game, Assassin’s Creed Mirage, as going back to the roots…
I actually even made my own bullshit-Spotify. As in, I’ve got a server running on a single-board computer which reads my music folder and serves a small music player as a webpage.
I didn’t want to install a music player client on my work laptop, but still wanted to listen to my own songs there.
This looks like one of the color blindness filters got activated. Here on Plasma 6, it’s a Desktop Effect in the System Settings. Not quite sure, if that was also already the case in Plasma 5, but if you just type “blind” into the search bar of the System Settings, then it should show up and you can disable it.
Hmm, you must have misread something. It translates to “mouth bags” or more specifically “mouth-of-an-animal bags”.
What the others wrote is already pretty good. An interesting observation I made in this regard: If you take a white noise sample and cut it really short, it sounds quite a bit like a snare drum.
That’s kind of the level of randomness you can expect from various unpitched percussion instruments. They don’t just have one tone, or the tone from multiple octaves layered on top of each other, like pitched instruments typically have.
Rather they’re all over the place, with many tones layered on top of each other, and those tones change rapidly, too. So, it kind of has many pitches and therefore not really any particular one either.
The dish in question: https://en.wikipedia.org/wiki/Maultasche
Agile tries to solve this differently.
First and foremost, it puts you into tight-knit communication with your team and the customers, so just ask if anyone remembers why it is like that.
If no one does, then Agile enables to basically fuck around and find out.
Which is to say, change it to how you think it’s supposed to be and see if anything breaks / anyone complains. If that happens, Agile allows you to react quickly, i.e. to change it back and quickly release a fixed version.
But yeah, as the others said, if your team feels like documents work better for them, then do Agile and documents. That’s why retrospectives are an integral part of Agile, because it’s not a perfect plan how to work together. You’ll know best what works in your context.
Google isn’t exactly excited about the concept of local files. They would prefer you to keep everything in their online services.
If you need support for these, then installing a separate file manager app is your best bet.
I’m using this one:
https://f-droid.org/packages/me.zhanghai.android.files/
(No idea, though, if it supports unpacking RAR archives.)
I still haven’t released anything which is not under the AGPLv3 license, which is even more aggressive than the GPL, primarily because I know that it’s prohibited to use AGPL-licensed software/libraries at Google.
I’m also hoping that because my stuff is on Codeberg, not GitHub, that its license hasn’t been laundered yet by some criminal AI company, but I don’t actually believe so. Certainly makes me more reluctant to publish my code.
I also switched from cursive to print for legibility.
I always found cursive terrible to read. Letters are more likely to look the same and it’s harder to tell where one letter stops and the next starts. I also read print all day, so I’m just more used to reading it.
Basically anything that has to do with:
It’s a roguelike in a post-apocalyptic setting with survival elements.
I’m using Simon Tatham’s Puzzles for nonograms.
It’s basically this webpage in app form: https://www.chiark.greenend.org.uk/~sgtatham/puzzles/js/pattern.html
It doesn’t result in a pixel art picture when you solve it, if you care for that, but the solutions do have contiguous regions.