NebiOS X: Explanation about Delays and Decision for Earlier-than-Planned Release

Hello. I'm Sarp M., the lead developer of the NebiOS project. I've decided to release a usable* version of NebiOS X to the public, a project I've been working on since November 2023 and previously shared with only a limited audience for development purposes.

The main reason for this decision is that despite setting consistent release dates, I've repeatedly faced interruptions leading to delays. In line with my transparency policy, I want to explain the factors causing these delays.

The first reason involves individuals who make false and irrational statements about my project, as well as toxic community members and fanboys of other operating systems. This issue will be familiar to at least one person, as it's one of the most common problems I've encountered. These individuals often resort to insulting both my project and me personally. These situations affect me deeply. Although I've somewhat learned to deal with such people, they still cause significant motivation drops.

The second reason relates to additional responsibilities placed upon me. I'd prefer not to get too personal, but my family relationships are quite challenging. To be brief, I've been arguing for years about why NebiOS should remain free and why it matters, with little progress in making them understand. In short, I feel great discomfort from being considered unimportant and not being able to be myself comfortably. Additionally, the "treatments" and "rehabilitation" they've subjected me to over the years have been harmful.

The third reason is trying to juggle multiple responsibilities simultaneously. Although I use "we" in NebiSoft announcements, I'm the only full-time worker on this project. For NebiOS X's UX design, this was the first time someone else joined as an assistant. There have been developers who came and went before this version, some whose job was just to test the system and report bugs. And there are some people who only talk rather than act... Regarding the tendency of many developers to gravitate toward projects lacking quality, security, and ecosystem standards (like Arch) due to toxic influence, and even becoming fanboys, I must say that these factors create serious obstacles in advancing my project.

Since the age of 13, I've been trying to deliver the "one operating system, all devices" vision through the Nebisa independent project, along with the quintuple promise of "Performance/Optimization + Unique user experience/design + Efficiency + Security + Quality." I'm committed to doing my best in this regard. Despite those who try to pull the project in different directions, reduce its uniqueness by making it more like other Linux distributions, and attempt to sabotage the project through brand smearing, I can't believe how far I've come in 5 years.

Finally, regarding the asterisk after "usable" in my statement: it's usable, but you'll need to handle some settings via command line or manual methods. Optimization might be poor, and you might experience crashes, but instead of pushing back the date, I decided to be completely transparent about these issues - unlike the most well-known example I can give, "Cyberpunk 2077's release," I've chosen to be entirely honest.

For those who want to contribute to the project, here's the roadmap:

1. GitLab Registration: First, you need to register on GitLab (instead of Microsoft-owned GitHub).

2. NebiSoft Membership Request: Contact me directly (see Contact section below) to request membership in the NebiSoft organization.

3. Contribution Areas: You can contribute in various areas such as implementing missing features, fixing bugs, improving documentation, or enhancing UX/UI.

4. Quality Standards: The following principles are important in our project:

- Optimization and minimal code (which also simplifies the problem-solving process)

- Choosing the right programming language for each task (NebiOS already uses multiple languages - mainly C, C++, and Python)

- Preferring more efficient alternatives to problematic languages like Java and Microsoft technologies

- Using mature and reliable technologies independent from the Microsoft ecosystem

I owe thanks to everyone who values this project, to those who voluntarily support me, to MuskArt who helped lay the foundations for the great UX design, to Gregor Czaykowski (Loading Artist) for permitting the use of his content, to the creators of the Wayfire project who helped transition NebiDE to Wayland, and to others too numerous to name.

Respectfully,

-Sarp M.

Contact:

For questions or support:

Community:

• Instagram: @nebi.software
• NebiChat/Matrix Room: #nebios:nebi.chat

Project Lead:

• Email: (ask from chat platforms)
• NebiChat/Matrix: @th3s4rp:nebi.chat
• Discord (rarely active): @coolazk124
• Known as: Sarp M. (0xffflyingbash)

Features:

• Wayland-based NebiDE redesigned while staying true to its roots
• Client (windows are called as clients in NebiOS) search-supported Client Swap has replaced alt+tab - users can still choose the classic quick switch style
• Redesigned screenshot tool - now merged with the screen recording tool
• Volume control OSD enhanced with music player integration based on context
• Privacy indicators and battery indicators for connected Bluetooth devices added to the top panel
• Utility panel upgraded with drawer-style grouping for displaying more content (each group has an icon that reveals content on hover)
• Control Center now more modern with consistent user experience
• Optional pure Android or Play Store-supported Android container (powered by Waydroid) [still in development]
• NebiSoft location services
• NebiVerse avatars to represent yourself in the system
• New Widget: Comic reader (currently having permission only from Loading Artist)
• Refreshed Bundle Store [in planning]
• Application/client automation system with performanced daemon integration [in planning]
• New driver installation screen and hardware health daemon [in planning]
• NTSYNC support (requires Linux 6.14 kernel)

Screenshots: