• 3 Posts
  • 14 Comments
Joined 2 年前
cake
Cake day: 2023年6月12日

help-circle
  • Didn’t know it only applied to UWP apps on Windows. That does seem like a pretty big problem then.

    I don’t still have a Mac readily available to test with but afaik it is any application that uses Apple’s packaging format. It could also be that it needs to be in the “Applications” folder, but I’m almost certain it isn’t an App Store exclusive feature.


  • Zangoose@lemmy.worldtoTechnology@lemmy.worldIs Matrix cooked?
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    12 天前

    I mentioned Linux specifically because something like this is the hardest to set up on Linux. I (wrongly) assumed that since you were complaining about it not existing, you were on a platform where setting these permissions up isn’t straightforward. App-specific file-acess permissions are on MacOS out of the box as a configurable setting for all applications (in the system settings menu), and I’m pretty sure Windows 10/11 has something similar in its settings menu as well.

    Edit: Also, if we’re being pedantic, this is also a setting on both Android and iOS, with Android displaying the option to change access pretty much every time you pick out a file.



  • Zangoose@lemmy.worldtoTechnology@lemmy.worldMatrix is cooked
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    13 天前

    I think the problem is that the Matrix Foundation (non-profit org) is being slowly cannibalized by Element (for-profit, VC-funded) which ends up making their costs and profit expectations a lot higher.

    Right now this is only impacting the matrix.org homeserver. However, this could eventually end up impacting protocol-level design choices that harm other instances as well. Sure, you could fork the protocol and clients, but now we’re talking about taking up the work that an entire organization had previously been doing. Not impossible if an existing organization like the FSF or Linux Foundation started backing something, but not a great place to be in either.

    Edit: grammar









  • Exactly this. I’d rather use TypeScript than regular JS, but I enjoy using almost any other statically-typed language more (except maybe C++) because TS has the potential to be just as bad as JS for codebases where it isn’t being used correctly (this is true for other languages as well but it’s usually a lot more obvious).

    Not that it isn’t possible to have good typescript code, but rather that code becomes a lot harder to maintain because of problems that could’ve been prevented at a language level (truthy/falsey logic, ‘any’ type being allowed by default rather than ‘unknown,’ etc)


  • In theory I’m a fan of the inferred but static typing systems that most modern languages use (kotlin, rust, TS, etc.) where most local variable types can be inferred and only return types/object fields/parameters need explicit types.

    I just despise typescript because it feels more like someone put a bandaid over JavaScript and all of its oddities instead of making a properly fleshed out language, and allowing the option for an ‘any’ type to be used freely by default emphasizes that.