Ephera

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.

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.

Fading out? With my wind band, we’ve never done it.
You can have everyone play pianissimo and also reduce how many players play each voice, but unlike a digital fade, this does change the way it sounds.
It’s also difficult to stay in tune when playing at a low volume with a wind instrument, so it starts to sound horrible before it becomes inaudible.

@Kairos@lemmy.today mentioned mic+soundboard, but for a windband, the band itself would need to be out of earshot, which is rarely possible.

So, yeah, if we ever need/want to cut a song short, we make use of a marching band signal.
Basically, the person on bass drum does two double-hits, which are out of rhythm so you can hear them, and then another hit on the first beat of the next measure, which is when everyone stops playing.
That does not always sound great either, but better than nosediving the whole orchestra. 🙃

Excuse me, Windows is the cheap copy of KDE.

I always hated that. It always felt like they just admitted defeat. They could have made an excellent song, but settled for disappointment.

Now I’m doing music myself, and goddamn, I get it. You can have a cool song going, and then you try to end it and it just sounds like disappointment every time.

Make that two.

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.

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.)

What is this article talking about? That’s a UX change. It has nothing to do with privacy or Mozilla’s commitment to privacy.

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.

https://cataclysmdda.org/

It’s a roguelike in a post-apocalyptic setting with survival elements.

Quantum computers won’t displace traditional computers. There’s certain niche use-cases for which quantum computers can become wildly faster in the future. But for most calculations we do today, they’re just unreliable. So, they’ll mostly coexist.

There can also be circumstances where you have to offer people a natural-looking key for general consumption. You can’t put UUID’s on car plates for example.

Often times, the first section of the UUID is unique enough. With certain UI design choices, one can encourage users to normally work with that, while having the full UUID available in a detail view or from a copy-button.

Another strategy I quite like, is to have the UUID as the definitely-always-unique identifier, and then have a separate name, which either the users can enter or we generate something like random adjective+animal.

But yes, neither of those strategies would work for car plates.

Hmm, interesting idea, to ask the user to provide the overall intent by making them edit/write the plan, since the LLM can’t do intent.

But man, we’ve recently had a number of programming beginners join us in our relatively large codebase, and I’ve basically had to write such a plan, i.e. step-by-step instructions, for them many times.

It just means that I go through the whole codebase and have to think everything through, without doing it myself.
It often took similarly long do that, and formulate instructions, as it would have taken me to write the code myself. Because obviously we’re using a high-level programming language, so there’s not many detail problems which are easier to describe in a natural language.

It’s also incredibly difficult to provide correct instructions that way, since I don’t get to read the existing code while I write the code.
And reviewing their code to figure out what came from it, that binds even more time.

So, yeah, it really doesn’t sound like this LLM thing would save me time either…

In my team, 2 out 15 people come to the office regularly, because they prefer the separation of work from free time.

I can definitely see some benefits from being on-site. You do occasionally just run into people, who can tell you really useful things for your job. And it’s definitely harder to keep track of what my wider team is working on, since we’ve gone mostly remote.

But those benefits just as well evaporate when “on-site” becomes two or more locations. I’m not going to run into someone who’s in a different office in a different city.
If I have to actively work together with people from different locations, I will also be wearing headphones all day, not able to socialize with the people around me. That makes it rather pointless to go into the office.

And yeah, just the flexibility of being at home is really useful. I can take a break from work to load my washing machine. I can sleep until 5 minutes before my first meeting. Or I can walk to the store in the morning, when it’s still cool outside.
So yeah, personally, I certainly wouldn’t go back to a fully on-site job, unless it’s somehow the best job in the world in other ways.

While definitely true, then it still shouldn’t be required to come in at all times. Hopefully, you can automate tests to the point where you do not need to physically interact with real hardware every day. And then it should be up to you, whether you want to come in or not.

On my phone, I can’t set the volume high enough for things to be audible via the phone speaker, due to stupid OS limitations.

So, to mitigate that, I’ve pushed all the sliders in the equalizer to the top. It doesn’t sound any different, just louder.

That’s also what happens, if you don’t balance the numbers. It’s just overall slightly more or less loud. And the numbers for volume are completely arbitrary anyways, so no need to worry about it.