The speech to text is basically perfect, the problem is YouTubeās choice to have to presented in the awful way they do. If they just looked like regular subtitles, Iād leave them on.
Donāt you? I always watch movies and play games with subtitles as well. Granted, English isnāt my native language. I would not do that in my native language.
You missed my joke, but thatās okay, Iāll explain it, I guess. OP said that they donāt use uBlock and that people who use it are āvirginsā (no offense taken). I made a dig on them, as to how theyāre watching videos in Firefoxās reading mode - by reading the subtitles?
Honestly, with this response although I think he didnāt deserve all of that from Linus, he did deserve quite a bit of it. So condescending and smug to application developers that actually make the user experience of Linux a good thing.
Okay, I agree that this is a really dickish way to respond to a dev, and I can see Torvaldās message being as much an olive branch to app devs as it was a thorough humbling of the maintainer. Still wouldnāt call it professional, butā¦ I get it.
Seeing the rest of the thread really contextualizes Linusā anger.
Only seeing the message from Linus makes him look like a dick. But when you see that heās responding to someone deflecting blame and being a shithead to the guy trying to report a problem and provide a suggested fix, the aggressive response seems more justifiable.
Yes. I did not include patch from first person in screenshot because I thought it would make it too boring to read. But it kinda adds even more to context.
Replying to āI get this regression with KDE on this system caused by this commit and here how I fixed itā with ālol, pulseaudio sucks, opensuse sucksā of course will make Linus angry and he will reply not only āno uā, but also āand hereās whyā.
Yo I didnāt know reader view existed what. Thatās amazing thank you.
However, Iāve never encountered any problems with unmodified ublock, worked perfectly out of the box for me. On the rare case that I come across a website that wants me to disable my adblocker I simply do not care enough about whatever is on that website to do so.
(Edit)
Alright so I tried it on a few websites and got a ācannot complete requestā page as well as āAdditional information about this problem or error is currently unavailable.ā Pressing try again did not help
Jesus Christ, telling someone to kill themselves is so beyond just professional considerations ā it is basic human decency to refrain from saying such things. I hope he continues to work on his behavior and finds a more productive way to interact with human beings.
Treat your volunteers well, or why should they continue volunteering?
Kernel maintainers have plenty of other opportunities.
I donāt know if they are volunteering or being paid. The other person said they are being paid.
Either way, no one deserves being talked down to like that, even if they made a mistake. Itās a matter of respect and self-respect. And as a skilled person like a kernel developer, it should be trivially easy to find other work in a more appropriate environment.
That being said, maybe Iām missing something. Torvalds has been known to be like that for a long time (although that seems to be over now). And still, Linux has been developed over decades. So apparently, skilled people flocked around Torvalds, or maybe rather his project. Not entirely sure why, but Iām taking it as a hint I might be missing something.
Generally speaking: not these days, and not for a long long time. Mauro, for instance, worked for Red Hat at the time. Itās of course possible to be unpaid and work for Linux, but I believe itās much more likely that one is employed by a big tech corpo and they maintain the kernel as part of their work.
If you have a common folder that you clone projects to (like OPās ~/coding), then that checkbox lets you trust that whole folder easily when this pop up comes up.
I have a coding folder āreposā. Itās on a remote machine though and I get this every time I connect to my code folder using a new remote host. So annoying!
One does not simply break userspace. Youāll receive more than just angry bug reports. There are restless maintainers who will not sleep. And the great corporations are ever watchful.
Yeah I kind of realised that the instructions assumed I had already upgraded, will try to keep track of new updates better in the future. So for sake of completion hereās how I solved it in the end:
Ran into conflicts: file /usr/lib64/libopenh264.so.2.3.1 conflicts between attempted installs of openh264-2.3.1-2.fc38.x86_64 and noopenh264-0.1.0~openh264_2.3.1-2.fc38.x86_64
Solved it with exclusion: sudo dnf -v system-upgrade download --releasever=38 --allowerasing --exclude=openh264.x86_64
Fonts and glitches are gone, got some broken deps instead. So if anyone got a suggestion for that instead let me know. Otherwise Iāll do as it suggest ābest --allowerasingā and see what else breaks:
<span style="color:#323232;">Problem: The operation would result in removing the following protected packages: plasma-desktop
</span><span style="color:#323232;">================================================================================
</span><span style="color:#323232;"> Package Arch Version Repository Size
</span><span style="color:#323232;">================================================================================
</span><span style="color:#323232;">Skipping packages with conflicts:
</span><span style="color:#323232;">(add '--best --allowerasing' to command line to force their upgrade):
</span><span style="color:#323232;"> kde-settings noarch 38.2-5.fc38 nobara-baseos-38 33 k
</span><span style="color:#323232;"> libkworkspace5 x86_64 5.27.8-1.fc38 nobara-baseos-38 115 k
</span><span style="color:#323232;"> libkworkspace5 x86_64 5.27.9.1-3.fc38 nobara-baseos-38 115 k
</span><span style="color:#323232;"> plasma-workspace-common x86_64 5.27.8-1.fc38 nobara-baseos-38 41 k
</span><span style="color:#323232;"> plasma-workspace-common x86_64 5.27.9.1-3.fc38 nobara-baseos-38 40 k
</span><span style="color:#323232;"> plasma-workspace-libs x86_64 5.27.8-1.fc38 nobara-baseos-38 2.2 M
</span><span style="color:#323232;"> plasma-workspace-libs x86_64 5.27.9.1-3.fc38 nobara-baseos-38 2.2 M
</span><span style="color:#323232;"> plasma-workspace-wayland
</span><span style="color:#323232;"> x86_64 5.27.8-1.fc38 nobara-baseos-38 70 k
</span><span style="color:#323232;"> plasma-workspace-wayland
</span><span style="color:#323232;"> x86_64 5.27.9.1-3.fc38 nobara-baseos-38 70 k
</span><span style="color:#323232;">Skipping packages with broken dependencies:
</span><span style="color:#323232;"> kde-settings-plasma noarch 38.2-5.fc38 nobara-baseos-38 13 k
</span><span style="color:#323232;"> plasma-lookandfeel-fedora
</span><span style="color:#323232;"> noarch 5.27.8-1.fc38 nobara-baseos-38 403 k
</span><span style="color:#323232;"> plasma-workspace i686 5.27.8-1.fc38 nobara-baseos-multilib-38 15 M
</span><span style="color:#323232;"> plasma-workspace x86_64 5.27.8-1.fc38 nobara-baseos-38 15 M
</span><span style="color:#323232;"> plasma-workspace i686 5.27.9.1-2.fc38 nobara-baseos-multilib-38 15 M
</span><span style="color:#323232;"> plasma-workspace i686 5.27.9.1-3.fc38 nobara-baseos-multilib-38 15 M
</span><span style="color:#323232;"> plasma-workspace x86_64 5.27.9.1-3.fc38 nobara-baseos-38 15 M
</span><span style="color:#323232;"> plasma-workspace-x11 x86_64 5.27.9.1-3.fc38 nobara-baseos-38 68 k
</span><span style="color:#323232;"> sddm-breeze noarch 5.27.9.1-3.fc38 nobara-baseos-38 440 k
</span><span style="color:#323232;">
</span><span style="color:#323232;">Transaction Summary
</span><span style="color:#323232;">================================================================================
</span><span style="color:#323232;">Skip 18 Packages
</span>
Yeah I forgot to mention that Iāll not be using dnf manually but rely on nobara-sync. But I must stress that I already did that before this issue, BUT I followed advice on nobaras own website where the solution was to use dnfand I still ended up with this problem. The real issue was still my own though, I should have upgraded to Nobara 38 before trying the workarounds, since 37 isnāt supported any more.
It un-fucked itself thankfully, I havenāt done anything to resolve that issue. But when I ran the update today it went well with several new packages. Which means Nobara or Fedora pushed some changes to packages in the repos.
Every time youāre excluding something youāre excluding updating a package, while updating all the others. Then if the new packages depend on the newer version of the package you didnāt upgrade by excluding it, things break. Thatās whatās happened here. Every time you use exclude to upgrade something youāre essentially breaking your system worse. Thatās what the other person means by āpartial upgradingā
And now that message says itās going to completely remove your desktop environment so youāre gonna have no desktop, just a cli shell.
At this point the easiest thing would probably be to back up your home directory and whatever else you want to keep and just reinstall the system. Any other process to try and fix it is going to require more trouble and time than it would take to just reinstall unfortunately. There may not even be a way to successfully unbreak your system.
Linus doesnāt love that, he literally got therapy to not be like that. Maybe thereās a lesson there for you.
In fact, in a more recent talk he mentioned being horrified at the sort of people who liked how he spoke and the way they assumed he shared their political opinions as a significant motivator.
I just love people that donāt beat around the bush and are straight to the point. We have enough snowflakes and bullshitters in this world IMO. Everyoneās so sensitive all the time, likeā¦ grow up and own your mistakes. And a wake up call guy like Linus is exactly what people need.
But, having one definitely raises alarams about the seriousness of the issueā¦ and this was a serious issue, not breaking user space is why weāre still using Linux. If it broke something on every update, Iām sure we would have opted for something else a long time agoā¦ so would every server on this earth, as well as Google for Android.
If you think it is acceptable to lash out at someone youāre mean and if you canāt find ways to communicate clearly without lashing out youāre a bad communicator.
Linux/open source has a massive problem with finding maintainers and contributors for critical projects and a significant contributor is just how awful the communication culture of programmers is.
Nope, actually Iām fairly calm. I only lash out when others do it at me first, but I own up (not lash out) if I was to blame. And the guy did own up, and thatās great IMO, he admitted he was wrong. Bravo š.
Kernel devs are like mini-gods, so I can understand them being with their nose up in the clouds a bitā¦ and they completely deserve that, theyāre the driving force behind what we use every day, for free I might add. But, since Linus started the whole thing, itās his show, heās running it. If he doesnāt like whatās being done, and especially if itās bullshit code, yes, I completely understand him lashing outā¦ I might not do it that way, but I feel that there is nothing wrong with that either.
lemmy.one
Top