Oh no! Where's the JavaScript?
Your Web browser does not have JavaScript enabled or does not support JavaScript. Please enable JavaScript on your Web browser to properly view this Web site, or upgrade to a Web browser that does support JavaScript.

AROSA

Last updated on 33 minutes ago
D
danilosJunior Member
Posted 6 hours ago
Recently I mentioned AROSA and was asked a simple question:

"What is AROSA?"

The shortest answer is that AROSA is an effort to evolve AROS into a more integrated, capable and modern computing platform while preserving the qualities that originally made Amiga systems appealing: responsiveness, simplicity, efficiency and accessibility.

More specifically, AROSA is a platform that provides common services and capabilities that applications can share instead of implementing independently. Services such as content management, search, networking, graphics, identity, security, monitoring and application integration are provided by the platform and made available to applications through stable public contracts.

For users, this means applications can work together more naturally and share common functionality. For developers, it means less time solving infrastructure problems and more time focusing on the unique value of their applications.

AROSA is not a replacement for AROS. It is built on top of AROS and aims to extend it with a modern application platform that supports both traditional desktop computing and more advanced information-centric workflows.

The project combines ideas from desktop operating systems, application platforms and content management systems into a single coherent environment. It is designed to support everyday computing, software development, education, research, creative work and organizational use while remaining lightweight enough to run on modest hardware.

At the heart of AROSA is a simple philosophy:

Computing should be composable, understandable, discoverable, lightweight and empowering.

Applications should be able to build upon shared capabilities. Users should be able to understand and explore the system. Developers should be able to extend the platform without needing to reinvent fundamental services. The platform should encourage creation, experimentation and learning rather than hiding its capabilities behind unnecessary complexity.

AROSA remains under active development, but a substantial foundation already exists across service infrastructure, desktop applications, content management, networking, graphics, browser technologies, monitoring, administration and developer tooling.

This document describes the current state of the project, its architecture, its level of maturity, and the roadmap that lies ahead.
Edited by danilos on 22-11-2026 10:04, 6 hours ago
You do not have access to view attachments
T
terminillsMember
Posted 4 hours ago

danilos wrote:

@danilos - Recently I mentioned AROSA and was asked a simple question:

"What is AROSA?"

The shortest answer is that AROSA is an effort to evolve AROS into a more integrated, capable and modern computing platform while preserving the qualities that originally made Amiga systems appealing: responsiveness, simplicity, efficiency and accessibility.

More specifically, AROSA is a platform that provides common services and capabilities that applications can share instead of implementing independently. Services such as content management, search, networking, graphics, identity, security, monitoring and application integration are provided by the platform and made available to applications through stable public contracts.

For users, this means applications can work together more naturally and share common functionality. For developers, it means less time solving infrastructure problems and more time focusing on the unique value of their applications.

AROSA is not a replacement for AROS. It is built on top of AROS and aims to extend it with a modern application platform that supports both traditional desktop computing and more advanced information-centric workflows.

The project combines ideas from desktop operating systems, application platforms and content management systems into a single coherent environment. It is designed to support everyday computing, software development, education, research, creative work and organizational use while remaining lightweight enough to run on modest hardware.

At the heart of AROSA is a simple philosophy:

Computing should be composable, understandable, discoverable, lightweight and empowering.

Applications should be able to build upon shared capabilities. Users should be able to understand and explore the system. Developers should be able to extend the platform without needing to reinvent fundamental services. The platform should encourage creation, experimentation and learning rather than hiding its capabilities behind unnecessary complexity.

AROSA remains under active development, but a substantial foundation already exists across service infrastructure, desktop applications, content management, networking, graphics, browser technologies, monitoring, administration and developer tooling.

This document describes the current state of the project, its architecture, its level of maturity, and the roadmap that lies ahead.



Just a suggestion as there's nothing wrong with creating your own framework. However would it not make sense to use a name that fits the framework instead of just adding an A to the end of AROS? It could be comfusing to users as to what it actually is. The problem with many of these independant frameworks is by using the AROS name even altering it just slightly they look as if they're official and many users will take it as such.
D
danilosJunior Member
Posted 3 hours ago
Thanks for the suggestion. There are actually several reasons behind the name AROSA.

First, the platform was originally conceived and designed specifically for AROS, so the connection is intentional.

Second, I wanted to retain something of the Amiga tradition of friendly, memorable names. AROSA also carries, for me, a suggestion of renewal and rising again.

Finally, AROSA stands for **Application Runtime Operating Services Abstraction**, which describes an important characteristic of its architecture.

I understand the concern about possible confusion, but AROSA is an independent project built on top of AROS, not an official AROS component or a replacement for the operating system. I'll make that distinction clear in its presentation.
D
danilosJunior Member
Posted 3 hours ago
AROSA is not intended to replace any part of the existing AROS experience, including technologies such as Zune/MUI, nor is it simply another GUI framework. AROSA and Zune/MUI operate at different architectural levels and serve different purposes.

Zune/MUI provides a GUI programming model, whereas AROSA is a broader application platform built around shared services, providers, adapters, capability discovery and composition, application lifecycle management, security, content management and an integrated user environment.

One of AROSA's fundamental design principles is to separate platform capabilities from their presentation and interaction models.

For this reason, AROSA can support a Zune/MUI personality for developers and users who prefer that environment. In AROSA, a personality is more than a visual theme: it can define the user experience, interaction conventions, desktop organization, tools and workflows.

Existing Zune/MUI applications can coexist with AROSA, while developers can take advantage of additional platform services and capabilities where appropriate.

**The objective is not to replace or diminish the existing AROS experience, but to preserve it, complement it and extend its possibilities.** AROSA is designed to build upon established Amiga technologies while providing an extensible architectural foundation for a new generation of applications.
T
terminillsMember
Posted 2 hours ago
I should probably put this a different way... some of the long time maintainers of AROS take offense if it muddies the waters of the name. While your intentions might be pure that doesn't change how it gets viewed by people who are not you. You yourself are not even using the full name of your project which is where the waters get muddied. and again I understand it's much more than a theme but if someone from outside the community comes in and they see AROSA, AROS ABIv11 etc those are technically not part of AROS they are outside the scope of AROS itself. The new users have to figure out what's what. That is neither fair to the users nor a project that has been in existence since the mid 90's. There's no reason you cannot keep a nod to AROS nor AmigaOS without being so close to the main projects name is all.
D
danilosJunior Member
Posted 2 hours ago
I understand your concern, and I certainly respect the long history of AROS and the work of its maintainers. AROSA exists precisely because I value AROS and want to contribute something meaningful to its future.

However, I don't believe that having a name which acknowledges the platform it was designed for necessarily implies official affiliation.

AROSA stands for **Application Runtime Operating Services Abstraction**. The name was chosen deliberately, both for its architectural meaning and its connection to AROS and the Amiga tradition.

AROSA is an independent application platform built on top of AROS. It is not an AROS distribution, a replacement for AROS, or an official part of the AROS project. I have no intention of presenting it as such.

I agree that newcomers should understand the distinction, and I'm happy to make that explicit in the project's documentation and presentation.

I respect the concerns you've raised, but I remain comfortable with the name I've chosen. I would prefer to focus future discussion on the architecture, its implementation and what it might contribute to the AROS ecosystem.
cdimaurocdimauroMember
Posted 2 hours ago

terminills wrote:

@terminills - I should probably put this a different way... some of the long time maintainers of AROS take offense if it muddies the waters of the name.

Their problem? There are already several "distros" that embedded AROS in their name, and I don't see why this time should be different.

Quote

I understand it's much more than a theme but if someone from outside the community comes in and they see AROSA, AROS ABIv11 etc those are technically not part of AROS they are outside the scope of AROS itself.

What/who is "the community"? Who defines AROS? Who defines AROS' scope?

danilos is already part of the community. And AROS ABIv11 is... AROS, exactly as AROS v0 and v1 are AROS.

What's YOUR problem with that?
T
terminillsMember
Posted 33 minutes ago

cdimauro wrote:

@cdimauro -

terminills wrote:

@terminills - I should probably put this a different way... some of the long time maintainers of AROS take offense if it muddies the waters of the name.

Their problem? There are already several "distros" that embedded AROS in their name, and I don't see why this time should be different.

Quote

I understand it's much more than a theme but if someone from outside the community comes in and they see AROSA, AROS ABIv11 etc those are technically not part of AROS they are outside the scope of AROS itself.

What/who is "the community"? Who defines AROS? Who defines AROS' scope?

danilos is already part of the community. And AROS ABIv11 is... AROS, exactly as AROS v0 and v1 are AROS.

What's YOUR problem with that?


Being long winded and confidently wrong doesn’t change the fact you’re wrong.

Who determines AROS not you, not this site, it’s parent project does I don’t know why you have such a hard time understanding that. Or are you just being disingenuous?
You can view all discussion threads in this forum.
You cannot start a new discussion thread in this forum.
You cannot reply in this discussion thread.
You cannot start on a poll in this forum.
You cannot upload attachments in this forum.
You cannot download attachments in this forum.
Users who participated in discussion: terminills, cdimauro, danilos