Technically it’s not browser tolerance but spec tolerance. It’s built into the html5 spec to tolerate different tags closing and other things invalid in xml.

This was an important design that grew out of one of the largest failings of xhtml that such failures would make the entire page unrenderable.

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

That was kinda my point. If qt breaks them again and arch updates and links the new QT are they going to come after them too? The position OBS took on this originally seemed like an open source disaster. It sounds like they moderated to something reasonable and that’s great.

This whole thing has been kinda wild. Every Linux distro bundles obs linked against their own libraries. Because fedora did it in a flatpak it was suddenly a problem?

I get developers being frustrated by buggy downstream builds flooding their queue with useless reports. They ain’t got time for it and can’t do anything about it. But this is open source software and obs had a bad take on distributing it IMHO.

Glad fedora was able to talk it out with them.

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

Interested in finding out more about fcast now though.

It’s actually even simpler. The whole building has wired feeds of the floor. So you can work from your office in the building or nearby, watch everything, and only come to the floor to vote.

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

Yeah that’s a better description.

Also of note this is part of the evacuation system for hurricanes. All lanes are outbown in an evacuation.

But it also kinda hides some of the crappyness. it was supposed to be on top of a giant underground flood diversion system which is a huge problem for Houston as you may have heard. Also the center was supposed to be for a commuter rail but we couldn’t get the bond passed so that might happen someday…

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!";