Readit NewsYeah it must be a meme.
And there certainly doesn't exist any where the entirety of the world population can be given access to these things.
If I really need an old library, it's generally not hard to install that in a temporary prefix and set the relevant PATH variables for it, though I do wish this was easier sometimes. It gets better as more projects just use pkg-config.
That all said, Meson[1] solves all of these issues in a way that keeps both developers and distributions/users happy. But as is with all things C, getting everyone and especially windows users to adopt it is gonna take a good while.
Interviews go both ways
As an interviewer you want to avoid being confrontational with your candidates. It's not helpful if they're good candidates, it's not helpful if they're bad-faith candidates like this one (they might be looking for some slip up on your side which makes the interview "illegal" and cause for them to sue your company), it's not helpful if they're simply not fit for the job (but in good-faith) as you don't want to make them feel bad they're not fit for the job.
If you already understood that they are not giving satisfactory answers, or like in this case they're just reading off the chatgpt answers, best to just keep gathering more proof to your decision not to hire them (by asking them more questions which can highlight your reasons) and finish the interview with the good ol' "we'll let you know."
(the UX around this is the shortcoming of all current DVCS..)
It's not like other people are mentioning in the thread that "some contributions would not get added" - but rather the fact that he often has really long periods of absence: just take a look at the contributions on his profile https://github.com/Unknwon
And of course, I'm not putting the blame on him - all of us need breaks from time to time - but during these periods where he can't work on the project, the project is essentially brought to a halt, seeing as there is no one else in the community of contributors who is able to merge pull requests - even if they are critical.
Single-developer projects are always risky. What if the dev just decides to stop developing it? Or there's a massive vulnerability, and they're on vacation with no internet?
maybe the point of publishing the work on a new browser like this is to get the word out, get folks to fool around with it and explore the changes, and hopefully perhaps assemble a small community capable of seeing through a vision of making a faster chromium, rather than getting folks blindly using it as their daily browser straight away?
if the project does take off, by the time it is actually good to be used as a daily driver it will be void of any furry art, trust me.
the beauty of open source is that if the original developer stops developing or goes on holiday for a year you can pick up the torch. mature projects are eventually smooth-sailing and can be used out of the box, but any project goes through many years of not being so pleasant to use (most of the time, the reason's very simple: nobody's getting paid to work on it, so be grateful you have the software in the first place!)