• 4 Posts
  • 209 Comments
Joined 1 year ago
cake
Cake day: July 15th, 2023

help-circle





  • You can always keep Chromium installed for the odd site that doesn’t work in Firefox (my daily driver). I do web development and test in every browser and I almost never encounter sites or features that don’t work in FF. The only one I can recall is something in the Azure Portal, probably because Microsoft wants you using Edge.

    Typically, Safari is the laggard and any developer worth their salt would make sure their site works on iPad and iPhone. When a new web standard is released, usually Chromium supports it first but even then, not always. And web developers usually don’t use features that aren’t implemented across the board yet. I know I go to caniuse.com before I use something fresh out the oven.



  • And, yet, in that time, consumers paid more for telecommunication services and basically the main innovations they got were touchtone phones replacing rotary ones and higher bills. Bell Labs being a success story doesn’t mean Ma Bell shouldn’t have been broken up.

    If consumers are paying extra to a monopoly anyway, just fund university labs and non-university research agencies (which we do). We have dozens of equivalents to Bell Labs. There’s no reason to rely on monopolists for innovation.




  • Also, there’s easy tools to help you. I know VS Code has accessibility code linter extensions. I’m not as familiar with Xcode or others but I’d bet there’s something that at least treats it like a code warning if you do something that would make your web site gibberish to screen readers and the like.

    We’re pretty much all gonna be disabled at some point. Some of us will piss off the mafia and be sank to the bottom a shallow sea while in our prime. But ideally, we all live to have vision problems or some other need for accessibility to exist.