Thanks for the feedback. I understand your point, but D.eSystem is not intended to be just a UEFI application.

D.eSystem uses Limine as its bootloader and loads my own kernel, D.Kernel. The kernel already handles things such as keyboard input, video output, hardware interfaces and a FAT32 filesystem, and I’m gradually building more OS infrastructure around it.

It’s definitely still a small and early-stage operating system, and I know there is a lot more to implement, for example proper memory management, processes, scheduling, system calls and usermode applications.

The reason Im adding filesystem and UI features is that Im developing the system incrementally rather than trying to implement everything at once.

I appreciate the tips from your previous comments, though. I definitely keep them in mind as I work on the kernel.

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

Yes,its build on the same source code like D.eSystem. I am the real developer,but I am still organizing this repo,I had planded to pack every source code on the main page but I packed it in the releases,I was already thinking about removing these commits.

Yep yure right,but I am already planing to bring legacy support back and just limite these special updates which are coming to UEFI.

Ok

In future I will add al the .iso files to this one repo and Iwill also add the source code with .ZIP files

I added the source code in a ZIP file

Yep,I fixed it

I used AI mostly for non code tasks like talking about the project and sometimes when I got stuck I used AI for debuging

It exits because I want to write a OS,and I also have a big roadmap,D.e will foucus on real us8ng on real hardware. And in future its also meant for daily tasks

I planed a Linux compatibility for D.eSystem X (10) or higher and wifi and networkdrivers for D.eSystem 7 ,now this is still in early alpha development,and it have no installer or file system,but I planed this for the future,if ypu want you can try itin a VM or Booting on real hardware.

And btw,the name means D.electronics-evelution-System

The 5 before that were simulations and OS prototypes,here is D.eSystem 5+ 8better version of 5) :https://github.com/D-electronics-scratch/D.eSystem-5- D.eSystem 4 was written in Python : https://github.com/D-electronics-scratch/D.eSystem-4 D.eSystem 3: https://www.programiz.com/online-compiler/16VmXW6XRomqk D.eSystem 2: https://scratch.mit.edu/projects/1280152791 D.eSystem 1: https://scratch.mit.edu/projects/1273773180 .

D.eSystem 6 was coded by myself,I used AI mostly for non code tasks like talking about D.eSystem,or talking about the roadmap, and sometimes I used AI for debuging.