• 6 Posts
  • 79 Comments
Joined 2 years ago
cake
Cake day: August 10th, 2023

help-circle
  • Vertical tabs? PWAs don’t even have tabs. Why are you bringing this up?

    They are examples of extremely wanted features that the firefox community has been asked for a while, but have only been added now.

    he browser extension you mentioned is from a 3rd party (and I have tried in the past and gave up because it just didn’t work, which was a far cry from the easy to use PWA support Firefox once had).

    Worked on my machine ¯_(ツ)_/¯

    I disagree with the idea that Google’s money comes with strings attached that influence the development of Mozilla Firefox. Google props Firefox up in order to avoid being hit by anti trust laws. Trying to explicitly or implicitly use that money for to intentionally Firefox bad, would be extremely risky, as if the slightest bit of evidence was out, they would immediately be hit with an antitrust suit, and it would defeat the purpose of the money.

    Well, they are being hit with one right now, but it’s not about the Google-Mozilla relations, but instead Google’s dominance as a default search engine.

    The loss of PWA Site-Specific Browsers is an interesting coincidence — but that’s all it is, a coincidence. The fact that they are being readded as an official feature, but only after Firefox got a UI rewrite is evidence that there are other internal and unrelated factors at play.

    Google maintains their dominance by adding to web standards very quickly, making it difficult for other browser engines to keep up, and “accidentally” breaking youtube on other browsers, in addition to other shenanigans. No browser engine will have the resources to keep up with that, and they don’t have to keep firefox intentionally bad by denying power users features when the vast majority of users will find something that youtube doesn’t work on unusable.


  • only to be shutdown by corporate before it gets much steam.

    So I guess you just completely ignored the part where I mentioned how they are readding support for site-specific-browsers (the ability to install a PWA as an app) and also officially adding vertical tabs? If that’s your definition of “shutdown”, then I don’t know what to tell you.

    But I’m sure the fact that features that explicitly affect the UI being added only after a rewrite/refactor of firefox’s UI is completely coincidental.

    EDIT: To me, it’s clear that they didn’t want to add these features officially since all the work would get wasted and overwritten if the UI rewrite happened. But there was always unofficial support, like this browser extension, and for PWA’s with service workers, they would work offline as well (which was built into the browser itself).







  • Should be awful for gaming. It’s possible to run x86 things with emulation, sure, but performance (especially single-thread)

    Most modern software (games excluded), is dynamically compiled. This means that it’s not all one “bundle” that runs, but rather a binary that calls reusable pieces of code, “libraries” from the binary itself. Wine is dynamically compiled.

    What makes modern x86 to arm translators special, is that the x86 binary, like an x86 version of wine, can call upon the arm versions of the libraries it uses ­— like graphic drivers. It’s because of this that the people on r/emulationonandroid managed to play GTA 5 with 30 fps via the computer version. There definitely is overhead, but it’s not that much, and a beefy machine like this could absolutely handle it.

    https://moonpiedumplings.github.io/blog/scale-22/#exhibition-hall

    The Facebook/Meta table had a booth where they had an ARM macbook that was running steam and they were installing games on it.


  • ut I honestly doubt ARM can with the overhead of emulation

    Most modern software (games excluded), is dynamically compiled. This means that it’s not all one “bundle” that runs, but rather a binary that calls reusable pieces of code, “libraries” from the binary itself. Wine is dynamically compiled.

    What makes modern x86 to arm translators special, is that the x86 binary, like an x86 version of wine, can call upon the arm versions of the libraries it uses ­— like graphic drivers. It’s because of this that the people on r/emulationonandroid managed to play GTA 5 with 30 fps via the computer version. There definitely is overhead, but it’s not that much, and a beefy machine like this could absolutely handle it.

    https://moonpiedumplings.github.io/blog/scale-22/#exhibition-hall

    The Facebook/Meta table had a booth where they had an ARM macbook that was running steam and they were installing games on it.








  • Right, but you could have just made one yourself

    And then there would be a bus factor of one. It’s not just about making a helm chart for myself, it’s about having something that can be shared with the community, that doesn’t depend on any single person to be maintained and updated.

    It’s about having an organization that provides “packages” for Kubernetes, for people/orgs that don’t have the time, expertise, and energy to maintain them.

    I greatly respect Ananace, who is in the comments of this post, and mentioned their Helm charts. The work is excellent. But looking through the commits, it’s just one person, doing something that primarily consists of bumping version numbers. Contrast this to the Matrix ESS helm chart, where the commits consist of many more contributors, and also include feature additions to the helm chart.


  • Hello Ananace! :)

    I actually have seen your helm charts many, many times before when searching for matrix, synapse, or lemmy on Artifacthub.

    An official helm chart isn’t really a hard requirement to me, even if I were to use one and it were to stop getting maintained, I could continue on my own. But an official helm chart has big community benefits that are very important to me. Like, there becomes the option of paid support, which is a must have for many entities. Also, an official organization may support a wider variety of usecases than someone making helm charts for personal use.

    I also ended up chatting with one of the core devs of Synapse about ways to improve regular Python Synapse for use with Kubernetes back in the ending of January, so hopefully it’ll improve in that direction when time allows

    Do you know anything about the claims that they have rewritten synapse in rust?


  • Yes and no. There are many things that are much easier with Kubernetes, once you figure Kubernetes out.

    High availability is the most notable example — yes, it’s doable in docker, via something like swarm, but it’s more difficult. In comparison, the ideas of clustering and working with more than one server are central to the architecture of Kubernetes.

    Another thing is that long term deployments with Kubernetes can be more maintainable, since everything is just yaml files and version is just a number. If you store your config in code, then it’s easier to replicate it to another server, either internally, or if you share it for other people to use (Helm is somewhat like this).


  • This helm chart is not just matrix/synapse, but also element (web ui), and “matrix authentication service”, which adds SSO/OIDC support to a normal synapse instance, which is pretty neat. I haven’t seen any helm charts that include the full matrix stack, just separate synapse or element helm charts. And helm definitely makes deploying services to Kubernetes easier than other ways of deploying applications.

    The other reason why I like an official helm chart, is because I have seen unofficial one’s be stopped being maintained by the community member(s) maintaining them. With an official one, it will (probably) be maintained indefinitely.