• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 12th, 2023

help-circle

  • Keep in mind that none of this applies to stuff for my job. If I’m working on a problem for my company the risk/reward profile is completely different.

    How I decide:

    • is it critical software?
    • can I switch off of it easily?
    • are there other options?
    • how good/bad are the other options?

    if it’s critical software I try to absolutely avoid anything that can be manipulated out of my control. That’s not always possible, or if it is, you have to make major concessions. An example is home automation software. Before I had learned these lessons I used samsung’s smartthings. ST enshittified almost immediately, because it was 1. built by samsung, 2. dependent on cloud services, 3. they removed capabilities from their API making the product worse than it was before. Home Assistant was coming on the scene right about then and I immediately switched. Home automation software is critical infrastructure, it should never be a cloud service (the point is literally local control, any company selling a cloud-only product for a local-only problem is a grift and will enshittify eventually). Switching off of Home Assistant is dead simple. None of my products in my house are HA products, they’re all their own brands, etc. The actions are all controlled by me, as long as a different system provides similar capability then the cost to switch has nothing to do with HA and only to do with the target system.

    Compare that with something like Github. I paid for Github before it was free, because the features were worth it to me. I lose nothing by using a cloud service for Git, because it’s a DVCS. All my data is local to begin with, and Github provides me with things like 1. a community, 2. an account to contribute to others, 3. a hosting location for a portfolio, 4. free static website hosting. The cost to migrate off of Github has nothing to do with Github’s product and only to do with the community that uses Github.

    You have to make this cost benefit analysis for everything in your life. Essentially, mine is completely based off of how much work it would be to move off of the product and if that work is worth it. Some things are worth it to self host, for example my jellyfin server is an absolute metric fuckton of work and costs a significant amount. But the alternative to that is paying for 15 different streaming services and still not having access to everything, and being screwed when those companies decide they’re not going to have a specific item anymore, or they’re going to charge for it, or they’re going to increase prices without improving the service. Some things are not worth it to self host, for example I pay for Obsidian because I wanted to use it and iOS sandbox doesn’t allow Obsidian to save to a dropbox folder. There are plenty of free alternatives, but I like Obsidian’s feature set and switching off it at a later point is easy, it’s all markdown files.




  • Gradle upgrades are dead simple… like yeah I get a bunch of the other criticisms of Gradle, but they mark things as deprecated two full major versions ahead and then slowly phase them out. Upgrades are a single command.

    I haven’t really encountered the issues others are having and I’m guessing a lot of them occurred before Gradle’s switch to kotlin.

    Edit: or the issues are actually from android build tool and not actually Gradle