Sounds pretty great to me honestly… Might spin up vm this weekend and give it a shot!
Thought let’s be honest, I’ve grown kinda lazy in my old age and compiling kernels is kinda a pain if you don’t need to so I dont know if I’ll actually use it for anything
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.
I was being sarcastic because really it doesn’t have a tool with explicit features, just a workaround using a couple features together.
For a new user it’s very difficult to do a pretty basic task.
It does! And it’s so easy to use.
It’s so obvious I can’t imagine why anyone would be confused.
Canada can just become the 51st state and solve that /s
It’s so semantic it almost reads like a sentence!
And who needs simplicity when you can teach people about advanced shell techniques like command substitution?
Perfection.
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.
Well it’s a new systemd release so probably.
I really appreciate this change. Prior to it was always a struggle to deploy servers successfully. You’d reboot and your database would be on the wrong interface and you could even remote in because the management interface was suddenly on a firewalled external only network. Ask me how I know.
With virtualization and containers this just got more complicated. I would constantly have to rewrite kvm entire configs because I’d drop a new nic in the machine. A nightmare.
Sure, it’s gibberish for the desktop user but you can just use the UI and ignore the internal name. Not even sure the last time I saw it on my laptop. So no big deal.
Yeah they probably mean easy. And probably easy for me, or what I already know.
That said, one of the complaints I commonly hear about Gnome is that it’s simplified to the point of being hard to use. So again, simplification is probably not what they mean.