I feel this pain. Having to deal with an inheritantly sync database in an async app is painful. You need to make sure at no point the transaction is stopped, make sure to set the timeout to a reasonable time instead of an iPad kids’s attention span, and a whole deal of other things
Can’t wait for turso to be stable.
Actually mint ship free software by default! Although there’s nothing preventing you from downloading more (no please add non free software checkbox)
Nvidia drivers are actually opt-in (it’s actually nouveau by default), so for the average person that should be fine… Personally I need the proprietary drivers for blender so I 'm stuck with it.
Although I don’t see how going to debian would help with anything…
Mint veteran here. You aren’t safe. Nvidia will come for all of us.
Meme aside, they have been pretty stable lately. But 2023-2024 had some pretty iffy drivers for my laptop GPU.
Kernel is on the older side, but safe. You don’t really need to have the latest kernel all the time though. All those 1% performance improvements can wait.
Went Mint > Nobara > Mint. I totally understand your take. It was fun tinkering a bit on mint, but I wanted more by going to Nobara.
I had to reinstall it 3 times. There have been some breakage due to KDE updates and Nvidia drivers, and when you go back from a long day at work and you just want to do some chill gaming, coming back to a non functional setup is a pain, even more when you just wanted to update and it wasn’t your tinkering.
So yeah, not for me. I do still think both have their own place in the world
TBF, it’s not the first time the LTS base changes, and it wasn’t a disaster at all.
Despite, there’s the Debian and Linux mint repos, as well as the entirety of flatpak.
It will be fine.
The only point I can say is that editing text on the terminal isn’t as simple as a regular text field. And AFAIK the only way to write a query on a regular text editor would be to write it, save to file, run file…
TBH if it’s just for that I’d rather use nix packages. But flatpak’s sandboxed app are better for sus packages or proprietary-might-spy-everywhere packages.
I personally only use navidrome’s web UI for full random, or listenBrainz when I know what I want to play. LB’s Navidrome integration is brand new so there’s some instances where the played track isn’t the correct one, although it does help a lot if the track is properly tagged.
Although I don’t like using random really much. My collection is vast, and some albums are really just there to be played every 5 months. That’s why I prefer radio that actually recommends my most listened to tracks first, then lesser listened after a while of not listening to them
What!? And then next you’ll tell me they are not wombs either?! I don’t believe you
My latest setup is probably too complicated for what I need… But it works.
The music server is a Navidrome server
I play those files using ListenBrainz so that I have centralised public playlists and being able to play tracks rereleased in multiple albums.
To add files to Navidrome, I use a local copyparty for a webui, as well syncthing to have a subset of the library always locally available in case of the server crashing or internet outage
When I don’t have the mood for any particular playlist, I use Alistral to generate a radio based on my listening habits
Of course 99% of the files are tagged using MusicBrainz Picard
Best part, the whole stack is foss software! And self host able too. I just don’t self host listenBrainz as I prefer the public instance
I am guilty of this but for a different reason: setting up debugging for clis in rust is hard
I love the debugger. I use it all the time I can. But when debugging cli it’s a pain as you need to go back in the launch.json file, remake the argument list, then come back to run debug, find out why tf it doesn’t find cargo when it’s the PATH… again, then actually debug.
TBF, if your step by steps instructions works, it doesn’t matter how complicated the command is.
Oh come on! I at least type the beginning so that it filters the history
Rust made me have an habit of using snake_case… .rs
Knowledge of your passwords
Uh… What password?
I kinda hate the push towards passkeys. If you have two factor Auth, going to passkeys makes you go back to 1 factor, aka less secured.
There’s also more and more 2FA fatigue attacks going on, and they can affect passkeys too, and if you don’t have a 2FA that involves the user writing a code on the 2FA device, passkeys could be quite possibly worse than passwords
TBH I thought it was for refactoring type safety. Making sure that the type is understood and not ready to just change wildly accidentally.
I do love rust. But I do like making fun of it too.
Although I don’t see how rust is immature? Unless I missed the joke?
I don’t get it either. OP might be angry at compile time (Couldn’t be worse than rust)
Canonical should really wake up and stop thinking that rewriting in rust is a magical way to remove bugs.
Sure the rust rewrite will surely be easier to maintain and less error prone (Assuming the code is idiomatic), but you can’t rewrite software maturity.
They should put it behind a checkbox instead of shoving it down anyone’s throat. They are literally testing in prod