• 0 Posts
  • 126 Comments
Joined 1 year ago
cake
Cake day: June 26th, 2023

help-circle




  • Yeah, there are different bluetooth audio profiles, one for high quality audio intended for media consumption, and one for bi-directional audio intended for telephony (and some others, but these are the relevant ones here). The “gotcha” is that in general, any attempt to consume the mic feed from a bluetooth headset will switch it to the telephony mode, so if you have them paired to a PC and an application is listening to the mic for any purpose you get stuck with much lower quality 64kbps PCM audio.







  • .NET (not .NET Framework) is cross platform and can be compiled into native binaries on a variety of platforms. There is however the wrinkle of not all the libraries within .NET being supported on all platforms. Most notably, everything involving a graphical UI is Windows only.

    The most well known cross platform .NET project you probably have heard about is Jellyfin.



  • It’s not really laziness. Storing as JSON solves or prevents a lot of problems you could run into with something bespoke and “optimally packed”, you just have the tradeoff of needing more storage for it. Even then, the increased storage can be largely mitigated with compression. JSON compresses very well.

    The problem is usually what they’re storing, not how they’re storing it. For example, The Witcher (first one) has ~20MB save files. These are mostly a bespoke packed binary format, but contain things like raw strings of descriptions in multiple localisations for items being carried, and complete descriptors of game quests. Things that should just be ID values that point to that data in the game files. It also leads with like… 13KB of zero-padding for some reason.






  • Depends on what your goal is. Strictly speaking cc by sa is more permissive than putting no copyright notice at all, since copyright is automatic, and the cc licenses grant various permissions not contained in standard copyright. It’s just a fancy legalistic way of saying “please credit me if you use this, continue to share in a similar fashion, but not for any commercial purpose”.

    So if you want people to share your work, cc by sa makes sense.


  • As someone in the dev team for a “business app”, we probably know about most or all of them, but they’re just not important enough for anyone in management to prioritize them as part of a sprint. It’s also possible no one has given us reproducible steps to make them happen, so we just straight up don’t know what to fix. Usually the former though.