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

help-circle









  • I’ve always liked the distinction between needing your job to survive and being okay if it disappeared for at least a few months

    If you have enough to mean you can take your time to look for a good job if you ever lost your current one without having to change your lifestyle, that’s the minimum bound of “enough” IMO. Anything else involves compromise, so therefore is not “enough” by definition.

    I’d say the idealised “enough” is when you can do whatever you decide to do without having to worry if you can afford it.

    Both of these depend on the kind of lifestyle people lead and how much more they would do if they didn’t have to think about money. For some people that idealised “enough” is unachievable, because they’ve decided what they want to do is make more money.

    People that end up chasing money for the sake of having more money will often do so in spite of any moral compass. And FWIW I don’t think there are a high percentage people out there that make “enough” by either of my definitions and that opens up all the exploitation that forces people into shitty jobs and situations they wouldn’t otherwise do



  • Ah fair play, I didn’t realise unrar was from the same guy, cheers for the extra context.

    So I guess we go back to what else it could be:

    • The licence could still be an issue as it’s not FOSS and parts of android are, so I guess that could prevent its inclusion if it’s incompatible with existing licences
    • The licence could also be an issue in terms of wanting feature parity with zip support, which would include creation of archives.
    • As I mentioned before, the percentage of users who are interacting with non-zip archives locally on their devices is a pretty small percentage. It may be on the backlog, but it’s not going to be far from the bottom in priority.
    • How many of the use cases are not served by the third party app ecosystem sufficiently that it would benefit inclusion in the actual OS and the extra maintenance that would entail
    • RAR is an outdated format and in decline at this point, there are better options to add before getting to it
    • Let’s also address the elephant in the room regarding the last point—I don’t think I’ve seen RARs used regularly outside of piracy in quite some time. If that’s the main use case, Google is not going to be bothered about supporting it.

    There’s probably other reasons I’ve not thought of, but just a couple of the above are enough to explain it IMO




  • I think a big part of it for RAR specifically is that it’s a proprietary format that would technically require Google to license it, and for the tiny percentage of users that would benefit, they don’t bother.

    A seemingly random but relevant example is the Japanese travel card situation with Pixel phones—every pixel on the planet has the necessary hardware to support Japanese travel cards since the pixel 6, however only pixel phones bought in Japan can use the feature (locked by the OS) because it would mean Google would have to pay a per-device cost worldwide.

    This is kinda a similar situation I’d bet, they’ve proven they would rather not include the feature than pay for licensing