• 9 Posts
  • 115 Comments
Joined 2 years ago
cake
Cake day: July 21st, 2023

help-circle
  • Well-cured wood can help. Guitars built with green wood will crack easily.

    Plywood guitars are tough - my resonator guitars are impervious to dryness, and they’re made of plywood basically.

    The other thing that might explain it is survivor’s bias - the guitars on the wall at the pub or in a mountain cabin either survive, or they crack and die. We see the ones that made it. Same thing with 200 year old parlor guitars - they are survivors.


  • Well if you subject your guitar to humidity fluctuations, it may well crack. Many do. My guild had a crack when I bought it, and when I moved to colorado it developed another. I have another guitar that has survived lots of changes in humidity and severe dryness without cracking. Maybe the wood was cured better, or I just got lucky.

    I keep my nice martin humidified to ~47% all the time. Maybe it would survive dryness, but I don’t want to take the chance. When they dry out it changes the way they play, being humidified properly helps keep the action consistent as well as protecting it against cracks.





  • plateaued since when? if you look at the second half of the graph, 2022 forward, it looks more steep to me.

    I take it ‘geometric mean’ is the geometric mean of ‘statcounter’ and ‘steam’? What’s the specific source of those latter two measures? For instance, when I look at linux usage on the statcounter website I get more like 1.5%, not 4%.




  • Depends. I made one in tauri and it was a good fit because I already had a web frontend and rust backend. I was able to reuse both of those with minor changes, now the same code builds the app and the web server/frontend.

    I’d probably go native if:

    • you’re only developing for android and don’t care about desktop/ios/etc…
    • UI performance is really important, like for a game
    • You want to minimize app size
    • You aren’t skilled at web front end development

    With tauri, if you need phone apis that aren’t in the toolkit already you’re going to jump through some hoops going from javascript to rust to kotlin and back again. Its a significant barrier, you’re handling serialization/deserialization of function arguments/results in 3 different languages.












  • I switched to nixos years ago. Its better now than it ever has been as far as available packages and etc. But it does present issues if you get off the beaten path - the “now you have two problems” issue. For instance:

    • if software is not packaged for nixos already, you won’t be able to follow the ‘build from source’ directions on its github page or etc. You have to make a nix package or at least development environment first. That can be tricky and you won’t have help from the software dev.
    • If software downloads exes that require libraries to be in a certain standard location, well, they won’t work. Android studio for instance, downloads compilers and so forth. There are workarounds, mostly, but it can take a while to discover and get working and I’m sure many people give up. Again, the android studio software and documentation will be no help at all.

    That said, more and more projects are supporting nix now, and nixpkgs has gotten really big. I think they support more packages than any other distro now.