Pop!_OS (Linux)
Pop!_OS is an operating system developed by System76 for STEM and creative professionals who use their computer as a tool to discover and create. Unleash your potential on secure, reliable open source software. Based on your exceptional curiosity, we sense you have a lot of it.
Whether this is your first experience with Linux, or your latest adventure, all are welcome to discuss and ask questions about Pop!_OS and COSMIC. Keep the discussions friendly though, and remember to assume good intentions whenever you reply. We're all here because we have a shared love for Linux and open source software.
Support us by buying System76 hardware for you or your company! Or by donating on the Pop!_OS website through the "Support Pop" button. Pop!_OS and COSMIC are fully funded by System76 hardware sales. All systems are assembled in the USA. With your support, we'll work to push the Linux desktop forward with COSMIC.
Links
Guides
Hardware
Recommended
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- programming.dev
- fosstodon.org (Mastodon)
- [email protected]
Community Rules
Follow the Code of Conduct
All posts on pop_os must adhere to the Pop!_OS community Code of Conduct. https://github.com/pop-os/code-of-conduct
Be helpful
Posts to pop_os must be helpful. When responding to a user asking for help, do not provide tongue-in-cheek responses like "RTM" or links to LMGTFY. Linking to direct sources that answer the asker's question is fine, but it's advised to provide some explanation as to how you got to that source.
Critique should be constructive
We within the Pop!_OS community welcome helpful criticism or ideas on ways to improve. However, basic "It's bad" or other simple negative comments don't help anyone fix anything. When voicing a complaint about something, try to point out ways the complaint could be improved or worked around, so that we can make a better product for it.
This rule applies to both Pop!_OS and its projects as well as other products available from third-parties.
Don't post malicious "advice"
It can be funny to joke about malicious commands, however this is not the venue for it. Do not advise users to run commands which will lock up their systems, steal their data, or erase their drive. Examples of this include (but are not limited to) fork bombs, rm, etc.
Posts violating this rule will be removed, even if the post is clearly in jest. Repeated offences may lead to a ban. You may understand that the command isn't serious, but a new user might not.
No personal attacks
Posts making a personal attack on any user will not be tolerated.
No hate speech
Hate speech of any kind will not be tolerated. Any violations will be removed, and are grounds for a ban.
view the rest of the comments
I don't mind The Register, and overall I think the article was objective and informative. There's a couple things I think should be noted. Firstly, it mentioned Pop uses systemd-boot instead of GRUB and kind of inferred that was unusual. It might seem unusual when comparing it to the number of distributions still using GRUB, but if you consider things logically, using systemd-boot on a system that uses systemd it makes a lot more sense than using an old, bloated, unsecure chain-loader. Systemd-boot meets Freedesktop bootloader specifications for a bootloader with systemd. It's simple, fast and secure. You can use GRUB if you like, but it's probably only familiarity that keeps it around.
I don't think Pop's partition layout, use of encryption is "overly paranoid". It's timely and necessary!
And finally, I don't think the author completely comprehends what is possible with COSMIC desktop. I could understand their POV if COSMIC was actually like GNOME in that it is difficult to modify heavily without causing instability. Gnome modification also relies on third party software which GNOME often don't support. So saying "If you don't like GNOME, you won't like this" could be true if stock COSMIC wasn't able to be modified easily. However, COSMIC is supremely easy to modify and people who like KDE, Cinnamon or any other desktop will be surprised to learn that they will likely be able to use Pop!_OS with COSMIC and make it look like KDE, Cinnamon, Gnome or even Windows. It's only a matter of desktop configurations, most of which will be native in Settings, and with the difference being COSMIC will remain stable. I will also mention that Gnome have never had a native tiling solution.
COSMIC is not Gnome. It's not even a fork of Gnome. It doesn't even use GTK3. It's completely new, and when alpha2 is complete I'm sure many people will suddenly "get it". COSMIC is integrating many features that Gnome have been removing for years.
Register, I like you, but I think you missed some important considerations.
Yeah, the author normally rarely misses an opportunity to complain about KDE being too complex in his articles - and COSMIC aims to fall in that sweet spot between the extremes that are GNOME and KDE, while adding features like optional but native tiling.
The applet concept where applets live in their own process and communicate via Wayland protocols (behind a COSMIC API) is also less likely to break than GNOME plugins that are horribly injected into its bowels.
Given the toolkit, organized development and UX decisions being up-front designed with figma sketches, etc. that are reviewed before implemented, and having both paid developers and community contributors it has a lot of potential.
Even better. A COSMIC API was not necessary since Wayland protocols already exist for this (layer-shell and security-context).
Could you explain a little more on that? Just curious.
Wayland compositors use IPC over a UNIX socket to communicate with Wayland clients. To increase security and enable sandboxed applet support, COSMIC applets use the security-context protocol for their IPC connection to the compositor. To be an applet, COSMIC applications use the layer-shell protocol to behave as an applet. Neither of which were made for COSMIC. Some other Wayland compositors support these protocols. You can see which compositors support the protocols at the bottom of the wayland.app protocol pages.