Someone else knows how to do a driver component for Linux Fedora KDE 44? i am looking to do one for this system that could replace out wayland with maybe probably either hyprland or i3 also i do use bash (bash scripting) which could be easier to do that instead of just trying on C, since bash is C but easier than said in utilizing that programming language also i could throw in some critters here and there like a grasshopper, a alakrusty alongside many others too, also a independenteable terminal of my own that does not have anything to do with the default one known as Konsole(?) maybe, i would have to do such changes to add in Linux Fedora KDE Plasma 45 and i will release it in 07/01/2027 if i could, and then i will come with either i3 or XWayland for the next update of KDE Plasma, how about this idea?
Sorry, could you please clarify what you mean by “driver”? Usually, it means a device driver that lives in the kernel:
Is this what you are writing? (if yes, those are the docs..)
Yes, i would like to implement a new kind of linux kernel as driver for linux fedora 45 KDE although it might be some kind of kafkaesque based kernel which is not user friendly towards beginners i however said previously that i like things that are hardly achieved and in a way that no other could achieve, by the way the most trivial things can be only achieved through hardwill and bulletproof workload so as for the most beginners, they won’t be knowing how to deal with it also i am planning to implement stuff like those trivial and most important features/programs i have mentioned before
OK, well, the docs I’ve linked to are the standard kernel documentation on how to write drivers. So, I’d start there.
The driver/kernel are to interact with the hardware. The apps/frameworks you’ve noted are different—and usually not related to the driver.
I am currently working on it and i decided to use the C programming language for it since it is easier than Rust, and given that i am able to find and fix out errors before releasing the new kernel update to the fedora dev team
Maybe try with something a little less ambitious? In the last few weeks you’re writing a new Operating system, porting some Japanese singing thing to Linux, “replacing”(?) Wayland with a driver(?) for hyprland/i3 and also writing your own terminal emulator.
Perhaps something a little more down to earth that can be produced in less than a thousand lines of code? I can’t help but feel that you’re aiming too high, too soon.
Maybe replicate an existing tool (grep for example or a CSV linter or a CSV to JSON converter in rust if you fancy fighting the borrow checker for a straight week) - the lessons you learn in designing, writing, debugging and finally publishing something like that will stand you in good stead for more ambitious projects (such as a terminal emulator) in the future.
I fear that if you start too far out of your comfort zone, you will become disillusioned at the lack of meaningful progress.
Fire up obsidian, create a vault for your project and start designing it, documenting it in markdown. I absolutely guarantee you’ll start thinking about “how to do this” and “how to track that” and “how can I make this efficient” and before long you’ll have a pretty well fleshed out project that you can start to code with a roadmap, a plan, most of the issues you’ve foreseen already mapped out and solved, and the code itself will be relatively trivial (ish!).
Release it, get some bug reports, fix them and so on. Learn to walk the entire process before you try to run straight at a Terminal emulator or a Wayland replacement.
Writing (good) software is hard - it takes a great deal of effort. Don’t smash your brains out with ambitious ideas that you realistically have little to no chance of completing.
Given my knowledge in kernel and C programming i can probably finish it in 5-10 years, and it might not be for linux fedora kde 45, instead could be for any of future versions of it
How about writing something that takes 5 to 10 days…
I think i can probably finish my kernel on at least 5-10 months of work if everything goes right as planned
I admire your confidence.
However, there is some code on a public repo, many will wonder if that confidence is somewhat misplaced.