That’s a more recent flare up but DHH has been “ruffling feathers” for a while to put it politely. https://tomstu.art/the-dhh-problem

Yeah, I don’t think that’s what the screenshot shows though since there’s no content at all 😅

It doesn’t have to not include JavaScript, that would be quite difficult and unreasonable. Accessible sites are not about limiting functionality but providing the same functionality.

I haven’t gone fully down the rabbit hole on this but my understanding is even something like Nuxt if you follow best practices will deliver HTML that can be interacted with and serve individual pages.

That said, screen readers and other support shouldn’t require running without any JavaScript. Having used them to test sites that might be the smart approach but they actually have a lot of tools for announcing dynamic website changes that are built into ARIA properties at the HTML level so very flexible. There are of course also JavaScript APIs for announcing changes.

They just require additional effort and forethought to implement and can be buggy if you do really weird things.

Also the EU and technically a lot of US sites that provide services to or for the government have similar requirements. The latter is largely unenforced though unless you’re interacting with states that also have accessibility laws.

And honestly a ton of sites that should be covered by these requirements just don’t care or get rubber stamped as compliant. Because unless someone actually complains they don’t have a reason to care.

I kind of thought the EU requirements that have some actual penalties would change this indifference but other than some busy accessibility groups helping people that already care, I haven’t heard a lot about enforcement that would suggest it’s actually changed.

Canada can just become the 51st state and solve that /s

Don’t think half the comments understand what the Chromecast is…

Interested in finding out more about fcast now though.

And a lot of science libraries.

Source: married to a physicist.

I mean, Fortran isn’t even dead. It was updated last year. Weird but it’s still a used language.

https://wg5-fortran.org/f2023.html

Right?

Ha yeah “Sr dev” was never seen again, the team member stuck around for quite a few more years.

Once we had a “sr developer” join a project from a consulting group. The project wasn’t going well so me and another dev started helping with some tasks as well.

After a couple days of helping, trying to get his web application to work with data from an API he turns to us and says “oh, json is just a string.”

The other developer from our team stared at him for a few seconds, stood up, walked out of the room and told the project manager something along the lines of “if that guy ever comes back in the building I’ll quit”

So yeah, json is just a string… But if that’s the end of your knowledge you’re in for a bad day.

So using react will get you fired? I knew it!

I’m ashamed… It’s simply “bump deps”

Did I also touch some code and tests connected to dependency updates. Yes.

Did I document any of that? No.

Did I spend more time writing this comment the thinking about the commit. Most definitely.

Will I be bisecting to this commit after our next deploy and cursing at myself? Probably.

It sounds like a joke but as another senior dev, one of the big lessons I’ve learned is getting really good at capturing all the requests that come in and who approved them.

It’s a bit of cya, but mostly so I can say “I can change that but it’s not a bug. It’s what was requested for this to do last year. Here’s the discussion” It’s surprising how often that results in “Oh yeah, that was for x. Let’s not touch it.” Or “oh that’s not a quick fix, let me come back with more information” etc

Array(16).join(“wat” - 1) + " Batman!";