Welcome to asus-fan-control discussions! #80
Replies: 1 comment
-
|
Hello, I will kick it off... ⚽ I am Dominik, the AFC author! 🌀 I started this project together with jack volume control for my ASUS ZenBook UX430UA device only (based on @afilipovich observation). Later, those two projects were split into ux430ua-fan-speed and ux430ua-jack-volume. The ux430ua-fan-speed was renamed to ux430ua-fan-control. At that point, I was maintaining multiple software repositories, mostly shell scripts with not many dependencies (if any). So I came up with an idea that eased the installation of that software for end-users and publishing for me as a developer. All in-sync with Git. It was a Git-based installation manager called gim written as a shell script as well. As soon as it was ready, ux430ua-fan-control started to use it and it was doing its job. Its big advantage was that it supported the standard "configure, make, make install" approach, so the number of compatible repositories was decent right from the launch. Once gim was stabilized in ux430ua-fan-control, something strange happened... 😲 Sergio Andrés Ñustes (maybe @infinito84 here on GitHub) tried the ux430ua-fan-control on a different laptop than the UX430UA and came up with the conclusion that it worked. That was a notable discovery since that ultimately led to add support for multiple laptop models and renaming the program as we know it today; asus-fan-control. Since then, many new devices have been discovered to be working using the original simple method... thank you all testers! ❤️ After some time, gim was seen as too complex for what it did and it was certain that it was hard to maintain. At that time, I had also learned a bit about POSIX Shell and its portability advantages. So I had decided to start from scratch yet based on the same idea – Git repository is a package, its URL is the package name. I had created GitPack, a very simple Git-based package manager, and started to use it in AFC as soon as possible. Here, I must thank @Darkyenus since he helped me with making gim work on macOS, and that have initiated my desire of creating portable scripts. 🍎 Then, @agura-lex appeared and said "Hey, Later, AFC has received (#20) a brand new simplified API. Also, the increasing popularity of AFC caused the need for an ACPI scout (probe, scan, reader, ...) to make troubleshooting easier. And hence afc-scout was created. To make AFC more familiar, @Greifent had created its wiki page (#32). He also created afc-gui (#37) and made using AFC from GUI possible! Thank you for that! ❤️ Last but not least, with the help of afc-scout, @AntonisKl came up with the assumption of controlling the second fan of his laptop with AFC. The assumption was confirmed and the mechanism of multi-fan control (#38) was incorporated into AFC. That was the next significant step forward for AFC. Thank you! 👍
As you can see above, AFC wouldn't be here without community contributions. Thank you to all AFC contributors! 👏 🎉 I personally have improved myself in many fields during the AFC development and using GitHub in general. It has been really enriching and I am looking forward to what will happen next. What will happen next? GitPack 1.0.0 will be released and then I will mainly focus on what I like the most – processor design. All that scripting is because I feel a strange commitment to make it really good since I/people may re/use it later (GitPack namely) and I think that I am almost gripping that level of quality now. Simple is good but sometimes hard to reach. 👌 Now it's your turn! 👇 |
Beta Was this translation helpful? Give feedback.
-
👋 Welcome!
We’re using discussions as a place to connect with other members of our community. We hope that you:
To get started, comment below with an introduction of yourself and tell us about what you do with this community.
Beta Was this translation helpful? Give feedback.
All reactions