On Thu, Jul 18, 2024 at 07:15:28PM +0100, cho...@jtan.com wrote: > Anon Loli writes: > > On Tue, Jul 16, 2024 at 11:04:17PM +0100, cho...@jtan.com wrote: > > > I think there is a fundamental misunderstanding here. > > > > > > Anon Loli writes: > > > > Hello list, after I compiled ... > > > > > > Once you have crossed this Rubicon you are a developer and On Your Own. > > > > That's mean! > > But it is the truth. Do I not correctly recall you writing that you > prefer to hear the truth, however blunt? I believe asshole was the > term you used. Is it a one-way phenomenon?
Your recall returns exit code 0.. I forgot that my mood can't be transfered automatically trough text, and that my joke won't be understood, because of course, this isn't real life, sorry.. > If you want to code get coding. If you want a working system that's > built by others others then put the compiler down and use what they > have produced. > > There is no middle ground. You break it, you get to keep both halves. When undoing 1 screw, I didn't expect the whole wheel to fall off (you can still drive with 3 wheels, but like not for long) > > I didn't change the source code related to Xenocara, I was just curious if > > Xenocara compiles with different Makefile or something.. it'd be nice if at > > least someone told me if it affects the mouse profile/driver somehow. > > Incorrect. If you had followed the build instructions as they are > written with the xenocara sources unchanged then xenocara would > have compiled. It didn't therefore you changed something. What do you mean it didn't compile? What did I say which would indicate that I got a error message while compiling Xenocara? > > I have a lot of experience when it comes to helping each other and "do to > > others as you want done to yourself"(or something like that phrase), which > > is > > When you are thrown in the deep end of a pool, you will learn to > swim or you will sink. Conveniently in this metaphor you don't also > drown, so consider it done unto you. You're welcome. > > Coincidentally you've (mis-)quoted from the book of Matthew. Chapter 7. Most people will sink if such continues, but if someone were to swim out, and for that spot to be known as a location where people get thrown to like learn swimming or something, someone could throw in a few life jackets or have someone be on ready, this example is so stupid, but still somewhat applicable, because either I don't understand you or you don't understand me, and of course now you'll say something like "you're the one who doesn't understand me", but what is there to understand, you seemingly just wanted to say that steel is forged with fire, without a care for that not everyone is steel, some people are still iron ;) > > > Use the source, Luke. > > > > But source big big big > > Then you have a lot of reading to do. > > The OpenBSD developers have also put a lot of work into their > exceptionally fine manuals. I suggest you read those too. Exceptionally fine manuals? Are you joking? You obviously don't know what a manual written by a perfectionist autist look like - literally perfection - and OpenBSD manuals are lacking in some places, and if my recall is correct, then I've already complained about manual pages, and not much has been done about it, as far as I know. Not sure if this is it, but it might have something to do with that SOME manual pages are for developers that are approximately the same skill-level as the author of them, so this is represents a huge problem, which is unless someone is extremely motivated, the skill-gap will never be bridged, people will not learn, OpenBSD will not gain more passionate people, and I suspect that everyone using OpenBSD is at a loss per-say Excellent example: So if say you buy a car, and you say have to connect it together, and the provided manual requires you to say have finished some related school or something like that, then most people are unlikely to ever fully build that car and since they won't ride in it, other people also won't get to see that type/model of car in the streets and thus won't buy one for themselves. Very similar thing happens with most things in our live, same goes for OpenBSD Now you might say something like: "So then help write better manual pages", but there are still parts of OpenBSD (manual pages) which I don't understand, partially because a significant amount of it expects you to know something which isn't mentioned directly (for example it doesn't say "you're expected to know/have read this this and this). > Appeals of "but it is le hard" to people who have openly published > every scrap of their work for anybody to learn from for over 50 > years are not likely to find much sympathy. > > Matthew Won't find much sympathy? I don't understand why.. just because they had to swim trough shit doesn't mean that everyone is, because even if OpenBSD isn't a commercial thing for profit doesn't mean you know what - above I gave enough examples, there's no sympathy needed, just logic, they can be the most selfish people in the world, but logic is still logic, even if they want to be selfish and evil people, others can help them make/fix stuff together, unless everyone from OpenBSD folks has achieveed perfect tranquility. I don't really deserve OpenBSD, I get that, but there is a reason as to why Theo De Raadt and other folks are still active on mailing lists and respond to topics like these, everything else should click and make sense now, I don't know how much clearer I can get, low critical thinking is required to understand what I wrote right now, and the only thing I can be wrong about here is that OpenBSD folks don't need new people (in general) who might even have greater potential than some of existing folks, to work on OpenBSD and related projects and I'd love to know why if that's the case. If that's not the case (I hope it's not), then I've already started my payback, and hope to somewhat give back to the OpenBSD
