helloSystem
Replies: 1 comment 5 replies
-
|
Hello @patmaddox, thanks for your excellent questions.
The main difference is that helloSystem is explicitly made to be welcoming to switchers, especially from the Mac. This means that we are using, e.g., a global menu, the Command key for keyboard shortcuts, and application bundles. In terms of the underlying technology, both systems are based on FreeBSD. Whereas GhostBSD has been building their own binary packages, we are trying to use the official FreeBSD packages wherever possible in helloSystem.
Right now I would characterize helloSystem as "FreeBSD preconfigured as a desktop for mere mortals":
This one is mainly for project overarching topics and discussion. The actual code lives in other repositories in the helloSystem organization. The main entry point for building the helloSystem ISO is https://github.com/helloSystem/ISO/, specifically the What do you mean by "we may not always be interested in contributions that increase portability"? Portability to what?
The idea is to implement what we call our "Three-layer UX design philosophy for Simplicity and Power". I hope that the linked article can answer some of your questions.
Right now helloSystem can be run from the Live ISO, and can be "traditionally" installed to hard disk. The installed system can be updated with
The reason that configuration files are mentioned under unwelcome technologies is not to take away control from the (power) user. All configuration files that are there can of course be customized. Even if we go the route of immutable images there will of course be a mechanism to customize the system in any way you'd like. But for the components developed for helloSystem we try to make things "just work" without the user having to experiment with 1,001 settings (which would make it impossible to test each and every combination, and make things harder to support).
Thanks for your questions. A "good desktop environment" definitely means different things to different people, but you sould get a pretty solid understanding of what I consider good user experience by reading through my 6-part article series on #LinuxUsability. In fact, helloSystem was born out of a desire to not only complain about things, but to improve them. Let us know how you like helloSystem in case you give it a try. |
Beta Was this translation helpful? Give feedback.
-
|
Okay that is all very encouraging! The 3-layer philosophy makes a ton of sense. I'll definitely give it a try and let you know how it goes! |
Beta Was this translation helpful? Give feedback.
-
KDE Plasma, of course. Here's the switcher:
What's in your article is not the switcher. |
Beta Was this translation helpful? Give feedback.
-
Our target user experience is one tool that has all the available languages to choose from. Not a tool to first choose languages from and then yet another tool to switch between the selected languages. |
Beta Was this translation helpful? Give feedback.
-
|
Two thing, you should know that the France, which is also in the French area, uses AZERTY, but Luxembourg and Switzerland uses QWERTZ, and Canada uses QWERTY, but there is another one that is Chinese Traditional and Simplified , and Korean it's not on the list, there is no need to talk about the CJKTS input method, this is another matter. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Hi there, I'm a web application developer who has been working on Mac since the first OS X. I am moving more from Linux to FreeBSD for server platforms, and so I'm interested in using FreeBSD as a development environment as well. Some research has led me to helloSystem. I've read as much as I can of the docs, discussions, and wiki, and have a few questions.
How would you describe the differences between helloSystem and GhostBSD? I assume you became reasonably familiar with GhostBSD before starting on helloSystem. From what I can tell, a key difference is GhostBSD is a fork of FreeBSD. helloSystem is... a set of packages that run on FreeBSD? I can't quite tell. There are a lot of repos under the helloSystem org, and the one I would expect to be the main one (this one, hello), doesn't appear to have any source code in it. So I'm not sure what is the entry point for helloSystem.
What do you mean by "we may not always be interested in contributions that increase portability"? Portability to what?
Is this intended to provide the full power of FreeBSD under the hood, or be more locked down like MacOS? I ask for two reasons: 1. There's the design goal of being a read-only OS, like macOS. So I assume that means we don't update helloSystem with
freebsd-update? 2. One of the unwelcome technologies is configuration files - but I want to edit/etc/pf.conf. A big part of why I want to use FreeBSD is so I have that control. This read-only, no-config-files approach appears to be in conflict with "Without lockdown. Without Big Brother. The user in full control." So perhaps I'm missing something.Ultimately what I want is FreeBSD with a good desktop environment. So maybe that means using FreeBSD with one of the available desktop environments :) But my research led me here, so I'm trying to get more info. I have never done any sort of OS development, so please forgive my naive questions!
Beta Was this translation helpful? Give feedback.
All reactions