Kage520

@Kage520@lemmy.world

• ⁨Comment⁩ on ⁨kingdom come⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  Medium is for burgers. Medium rare is where it’s at for steak.

• ⁨Comment⁩ on ⁨Say Hello to the World's Largest Hard Drive, a Massive 36TB Seagate⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  Especially VR files

• ⁨Comment⁩ on ⁨YouTube's Latest Update Shows That Online Monoculture Is Dead⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

  Facebook was fine at first. I remember excitedly hearing that my school was added to the list of approved schools to get a Facebook account.

  Not sure if problems started when it was expanded beyond just listed colleges, or if it was just the public stories or wall or whatever it’s called.

• ⁨Comment⁩ on ⁨Garmin adds AI and a subscription tier to its app⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

  You wouldn’t want to wear a dive watch if you never dive, so why put that feature set on everything? Probably similar thoughts for a lot of these models.

  That said, you are correct that they should streamline a little. It’s a ton of nonsense and very frustrating to hide features that are clearly being calculated (HRV) but hidden because you didn’t buy the right model.

  One glaring omission for me is the lack of database options in the app store. They have a TINY bit of hard drive dedicated for a third party app. I used to own a Samsung and wrote an app for my gym workouts. It was great, but I like Garmin watches better. But even if I use the available key value pair database on Garmin, it only gives me space for maybe 100 sets before I am out of memory. Useless if you want to track any kind of history for multiple workouts. Same for the disc golf app I made for Samsung. I could technically save enough to play, but my old app has room to let me know all my previous scores per hole at each place I was, etc.

  This isn’t a huge amount of space needed for these things. A few MB. But it’s walled away for some random reason. Really limits developers from making good stuff.