A random cat-loving, transgender catgirl on the fediverse :3

Github: Link to amycatgirl’s github profile

Revolt.chat: amycatgirl#9237

Mastodon: @amycatgirl@kutia.sernik.tech

  • 1 Post
  • 85 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle




  • As a web developer, I agree

    But ensuring full compatibility with all three major engines (those being gecko, blink and webkit) is unnecessarily hard, as they have their own subset of features

    For example: Webkit does not support extending built-in HTML elements using WebComponent, but Gecko and Blink do support this feature. Or Chrome being the only browser that fully supports the View Transitions API. Or webkit’s CSS vendor prefixes

    The list goes on and on.

    You could fix most of these issues by providing polyfills, but that increases the amount of files that you have to load in order to make a feature work on other browsers.

    If only there was some sort of standard… Oh wait, there is one, W3C. Idk what they are doing tho.





  • It’s not that they don’t work better in conjunction, it’s canonical’s lack of moderation in the snapcraft store.

    This could’ve avoided day one by adding a manual review process (like what they are temporarily doing right now)

    I don’t know how flathub handles new package submissions, but I think that they definitely need to have a process similar to what other distros have in place for native packages (heck, even Ubuntu’s own repos have a review process)