luciole (he/him)

Doesn’t know the lyrics. Just goes meow meow meow.

  • 17 Posts
  • 371 Comments
Joined 2 years ago
cake
Cake day: June 6th, 2023

help-circle


  • I agree with you that failing to support multiple browsers is an old problem, but I think the cause has shifted.

    Back in the last century, supporting both browsers amounted to sniffing the browser and implementing the same feature twice. document.layers vs document.all for example.

    Nowadays I think the problem is different: we just don’t know what’s going on. The site is transpiled from TypeScript, written on top of React or Vue which drastically switches paradigm (bonus for Tailwind), packed with building tools, and the average dev has little understanding of what actually comes out. It’s a tall stack of leaky abstractions on top of the already tall one of the web. The dev is pretty sure it works on Chrome so they say it does work there, but it was not even a deliberate choice.














  • Whether it is being offered to the end users as free (as in freedom) software or as paid closed source has the usual implications. Ease of use, accessibility measures and support impacts inclusivity. Supported languages (natural and programming) will influence further who uses them or not. What constitutes the user base will determine what’s it’s used for and in turn will apply pressure to the editor to take a certain direction.

    Political impact is not always obvious and not every single grain of software will be infused with a powerful one. The point is that our choice is either to ignore it or to acknowledge it. We can’t opt out of the world; blind neutrality is as political as any other position.