And I also think criticism itself is good,but comments like Vibe coded or AI slop is no normal critisicm, these comments are just rude, But your comment was good critisicm, thanks for your feedback👍
Firstly I am posting in different communities and on different platforms, and yesI know the Issum with the github repo,I want to createca,whole New repo to fix it.
Thanks for your feedback,I didn't write the bootloader, I use limine,but I write all the features and the kernel by myself, and I am also firstly polishing this feature and making it ready for release(D.eSystem can also run and boot on real hardware). But thanks for your feedback, for 6.1.9 oder 6.2.0 I want to make a whole new github repo.
Nope,its not vibe coding and its also no spam,I am just posting every 3 Werks.
Thanks for your info, I don't need a license anymore ( I researched)
And I am not spamming, I am just posting new updates from D.eSystem. (I post every 2-3 weeks)
Firstly Its not stolen,Limine is a opensource bootloader which I am using for D.eSystem, I will not start from scratch because its not just a experiment. And with D.eSystem 6.2.x I will make a new repo
Hi,nice that you go in kernel dev,D.eSystem itself is not suporting apps or something from outside,but you can go on the github link,download the source code andadd own features to the kernel and you can compile D.eSystem:)
Ok,then im gona cleaning up,thanks
Hello,thanks for you feedback,I know the repo is the bigest problem with D.eSystem 6,I have planed to kepthe D.eSystem 6 repo like it is but to create a new repo for D.eSystem 7 when I am starting D.eSystem 7 in future.
I deleted these files on the main branch,and I am firstly trying to keep the repo,but I have planed to make a new one when I am making D.eSystem 7
What should I do in your opinion with the repo?
The tags from v6.0.9 to v6.1.5 currently all point to the same commit because I didnt push the actual development history to GitHub yet.
I was developing locally and only uploaded the source snapshots as release archives, which makes the tags look incorrect or “fictional”.
The ISOs are built from newer code, but that code hasn’t been pushed to the repo yet — that’s why the tags don’t match the releases. And the newer code is based off the older code.
You are right, the repo structure isnt in its final form yet. I originally uploaded the full source code as release archives instead of pushing each version as proper commits, which is why the tags currently point to the same snapshot.
I am reorganizing the repository so every version will have its own commit history, proper tags, and the full source directly in the repo instead of only in releases.
Im fixing the Git workflow so it follows standard conventions. Thanks for your feedback:)
The repo structure is still in progress. I originally uploaded the full source as release packages instead of pushing incremental commits, which is why the tags currently point to the same snapshot. Im reorganizing the repository so each version will have its own commit history and proper tagging.
The 6.1.5 release is built from the same code as the tag (nothing unpublished.)
And yes, Im the sole developer. I only use AI for explanations or debugging, not for generating code.
Im cleaning up the repo structure soon.
And I use AI just for learning,explanation and debuging
Thanks for your feedback:)
Because its in development
For bootloader Im using Limine,but I started with OS simulators.