Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Hector doesn't like "the orange site" very much.

This thread about his anime girl persona is probably why:

Screenshot 2023-03-24 at 12-08-07 I did not expect the coding live streams of GPU engineering ...png

edit: attached linked screenshot too
 

Attachments

  • H-Uq.png
    H-Uq.png
    82.9 KB · Views: 225
Last edited:
Hector doesn't like "the orange site" very much.
:story: For once Hackernews is right. Hilarious that he's this pissed about people reacting negatively to his creepy and weird persona.
What a thin-skinned faggot Hector is. The one time that HN collectively isn't sucking him off for being a Linux superstar or whatever, and now they're "worse than 4chan".

Good to see that even most of the midwit HN denizens can tell that Lina is just Marcan with a voice changer hiding behind an anime girl though. I still don't understand how Hector thought he was pulling a fast one on anyone with that.
 
Hector thinks that if you want to change the resolution of an LCD screen you are an uneducated retard. Therefore Asahi linux will not support it.
(cant post a screenshot right now, so here's a quote)
It's wild how in 2023 some users still expect to be able to change the "resolution" on their LCD panel, as if it could magically change the number of physical pixels it has.
CRTs had variable resolution. LCDs don't, but emulated it with a built-in scaler so they could support the same input signal variety as CRTs. But modern display controllers can already scale their output. So when laptops came around, instead of putting scalers between the GPU and the panel like LCD monitors do, they just used the display controller scaler, to continue to expose a variety of resolutions to legacy software that expected that.
So now we're faking screen modes at the GPU/driver. Software asks the driver to set a very specific screen mode (not just resolution, also timings, analog signal details, etc). The driver/firmware completely ignores all that, takes only the resolution, configures the display controller to scale it up to some unrelated native mode, and goes with that. Likely with a million corner cases around refresh rates and timings being slightly wrong as a result.
Why do people set lower resolution modes on LCDs? Because they want to make things look bigger (and also terrible). But now we have UI scaling, which makes things look bigger and not terrible.
And for times when you actually want to scale, like when you're deliberately playing a game at a lower resolution for performance, the scaling features of display controllers are already exposed to software/compositors through modern KMS APIs directly, without having to use pretend display modes that don't exist.
And now in 2023, I'm having a conversation with KWin developers about how no, you can't just add pretend fake lower resolution screen modes and assume the driver supports them because "every other driver" (read: AMD/Intel/Nvidia drivers with a history of legacy on x86, and nothing else) supports it.
Apparently that feature of faking modes in KWin got added because GNOME added it, because users expected it and it was seen as a regression from Xorg. Users expect legacy nonsense, one DE adds it, the others have to copy it because otherwise people complain, and we keep on carrying legacy nonsense forever. Currently, Asahi Linux users see a pile of fake resolution modes in System Settings that don't work because our driver rightly rejects them as unsupported.
Looks like we found the right gate to hide that stuff on drivers that don't do virtual mode scaling, so hopefully that will go away pretty soon. And I will keep telling our users that if they want to make things bigger on their laptop screen, that's what the UI scale slider is for. Not fake blurry scaled resolutions.
https://social.treehouse.systems/@marcan/110087747118788010 (a)

That's some hard cope. Hector, just confess that you don't know how to implement video scaling on M1 hardware instead of sperging out that it should be done by compositors. Changing LCD resolution is something that macOS can do, so it is certainly possible on Apple hardware.

I have 4k monitors at work and the UI scaling there is absolute madness, with half of applications having huge title bars and tiny text (GNOME 3), and half of them opening in tiny windows that are 1.5" x 1.5" on screen because they don't support fucking UI scaling. And I'm not talking about some obscure programs, I'm talking about basic Linux GUI utilities like xarchiver or firefox.
 
I have 4k monitors at work and the UI scaling there is absolute madness, with half of applications having huge title bars and tiny text (GNOME 3), and half of them opening in tiny windows that are 1.5" x 1.5" on screen because they don't support fucking UI scaling. And I'm not talking about some obscure programs, I'm talking about basic Linux GUI utilities like xarchiver or firefox.
High dpi displays and fractional scaling are ass in all the Linux desktop environments. This is the use case where a normal resolution display is better depending on the size of the monitor.
 
High dpi displays and fractional scaling are ass in all the Linux desktop environments. This is the use case where a normal resolution display is better depending on the size of the monitor.
This is exactly how Hector will solve this, once his YellowDog Asahi Linux forces native resolution all these dekstop environments will be incentivized to fix their scaling. Think Different.
 
I really don't know why he bothers to keep up these lies.
First it was "Byuu totally neckroped himself, I called the police and they told me even though I wasn't blood related in any way! Trust me guise!" when there's no fucking evidence of him being dead.
Now it's "Guise Lina is totally not just me in a vtuber persona, ignore all the evidence saying so!"

Is this man just a pathological liar who concocts these weird ass stories to make himself feel better?
 
Midwit Drew appeared!

I'll save you a click:
>It’s time for Richard Stallman to go.
>We need more leaders of color, women, LGBTQ representation, and others besides.
It is official; Netcraft now confirms: the FSF is dying

One more crippling bombshell hit the already beleaguered FOSS community when Drew Devault confirmed that GPL market share has dropped yet again, now down to less than a fraction of 1 percent of all new npm packages. Coming close on the heels of a recent Rust Foundation survey which plainly states that the GPL has lost more market share, this news serves to reinforce what we've known all along. The FSF is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Twitter comprehensive popularity test.

You don't need to be a Kreskin to predict the FSF's future. The hand writing is on the wall: The FSF faces a bleak future. In fact there won't be any future at all for the FSF because the FSF is dying. Things are looking very bad for the FSF. As many of us are already aware, the GPL continues to lose market share. Red ink flows like a river of blood.

GCC is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant appearance of official LLVM support in Linux distros only serves to underscore the point more clearly. There can no longer be any doubt: GCC is dying.

Let's keep to the facts and look at the numbers.

FSF leader Richard states that there are 7000 users of Parabola. How many users of Guix are there? Let's see. The number of Parabola versus Guix posts on Reddit is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 Guix users. GNU/Hurd posts on Reddit are about half of the volume of Guix posts. Therefore there are about 700 users of GNU/Hurd. A recent article put GNU/Linux at about 80 percent of the GNU market. Therefore there are (7000+1400+700)*4 = 36400 GNU/Linux users. This is consistent with the number of GNU/Linux Reddit posts.

Due to the troubles of shit code, abysmal performance and so on, GCC went out of business and was replaced by EGCS who wrote another troubled compiler. Now EGCS is also dead, its corpse turned over to yet another charnel house.

All major surveys show that the FSF has steadily declined in mind share. The FSF is very sick and its long term survival prospects are very dim. If the FSF is to survive at all it will be among programmer dilettante dabblers. The FSF continues to decay. Nothing short of diversity and inclusion could save the FSF from its fate at this point in time. For all practical purposes, the FSF is dead.

Fact: The FSF is dying
 
Back