Glancing over the website, I thought it’s an immutable OS, like Fedora Silverblue. I could imagine that it might be cool to use with Ansible and stuff. But for an average user? I can’t really see the advantages in respect to the work you have to put in.
Because it’s the latest Cool Nerd Thing™ like Arch before it, and Gentoo before that. Most of the people raving about it probably don’t have much use for its features.
The features themselves are very useful for basically any user. Whether they are worth the non-standardness and issues that come with it is another question.
I used NixOS for a couple of years. My experience is like this:
It is a rolling release (mostly)
You write a declarative configuration for your system, e.g., my config will say I want Neovim with certain plugins, and I can also include my Neovim configuration
It is stable, and when it breaks it is easy to go back
anyone with more experience?
I only played around with Btrfs, which was quite nice, but I settled for a ZFS for my simple Raid 1’s, as I really liked it under BSD. else I just stick with Ext4.
As mentioned in a child I definitely didn’t find it stable. It seemed to use masive amounts of CPU for unclear reasons and locked up a handful of times in my testing. When force-rebooting the filesystem was corrupted and seemed to continue to lose data after that point.
But that being said I think it may actually be good to merge it. It seems that there is lots of interest and the maintainers will be around to keep improving it. Getting it in the mainline (hopefully with some sort of “beta” label) will help it get the testing it needs. If the work is going to be done either way it seems best to be working in the main repo rather than keeping it separate and needing to continue handling migrations and merge conflicts. Look at BTRFS. It was known for data loss but now seems to be pretty stable with lots of eyes and lots of work.
But that being said I think it may actually be good to merge it. It seems that there is lots of interest and the maintainers will be around to keep improving it.
Yeah I think people shouldn’t hold it against bcachefs to have some issues in experimental stages and going mainline is a good way to catch obscure & rare bugs.
Look at BTRFS. It was known for data loss but now seems to be pretty stable with lots of eyes and lots of work.
IMHO it’s pretty unfair how people like to give new, complex, filesystems a ‘reputation’ immediately, when there are some issues. I hope not the same is done with bcachefs and it gets its fair shake. Occasional issues popping up now (like in your blog post), hopefully, will also allow some of its cult followers to touch grass and get a reality check (filesystem = difficult). IMHO Kent really should remove the obnoxious “The COW filesystem for Linux that won’t eat your data.”-sentence from his website as it encourages such nonconstructive attitudes. I’m sure he is aware that, at this point, btrfs is less likely to eat your data by many orders of magnitude compared to his draft filesystem (and that’s mainly because most of those data eating bugs have been found and fixed in btrfs, not because it’s somehow impossible to corrupt by design).
Manjaro was my intro to Linux, but now that I know more about it, I can’t recommend it in good conscience. Letting their SSL certs expire is something that happens (even though they could automate it), but telling their users to change their clocks so it works is a big no-no.
Worse than that is how they manage packages from upstream. Simply freezing them for two weeks is, in my opinion, the worst of both worlds. You don’t get timely security updates, but you still end up with the issues of being on the bleeding edge - just late. It also means that if you use the AUR (which is really one of the biggest perks of Arch-based systems), it’s possible that the necessary dependencies are out of date.
I think that if one wants “Arch with an installer” they should go with EndeavourOS, or try the archinstall script.
Sure. When it comes to updates, Manjaro is pretty much doing what every single other distro is doing. Updates that are buggy don’t get pushed to the stable branch until they’re fixed up, and security updates tend to get pushed through faster than feature updates. The time period that updates get held up by is not a fixed duration, it depends on the specific package and update and can be anywhere between a few days and a few weeks.
As a concrete example, with some major Plasma updates Manjaro has waited for three or even four point releases (4 / 8 weeks) before considering it stable enough vs the newest point release of the previous major release, and following point releases after that get pushed to stable much faster.
As another point, even Arch has a very similar process… Their policy on pushing updates is far more geared towards pushing updates quickly than towards not breaking things, but otherwise it’s pretty much the same.
Manjaro packages start their lives in the unstable branch. Once they are a deemed stable, they are moved to the testing branch, where more tests will be realized to ensure the package is ready to be submitted to the stable branch
That is exactly why I choose to use FOSS including Linux. As much as I want to standby this principle, I have come to a breaking point after dealing with its issues, issues we have all experienced. I believe it is hands down the best choice for server use, but for work and productivity, I need something more matured that is going to work out of the box. I am glad that the community here took this criticism well but I think it’s important to discuss and understand that there are still some strides to be made. But at the end of the day, I’m just some guy ranting and who knows, maybe I’ll be installing a Linux distro after a month of using Mac OS.
This summer I use Linux on my desktop for 25 years. What do you think the first years looked like? My first laptop took me 3 weeks to get it properly installed with Suse back in 1998. For the last 10 years installing and configuring whatever distro is a piece of cake. Ofcourse soms things are not as you want them to be: the good thing is you can change everything in FOSS, and if it does not excist you can create it. People complaining at Linux Desktop are realy complaining on their own limitations. Don’t complain! Not about yourself. Not about the Linux Desktop. Never ever give up! Make your list of whats not working for you. And than work and change until your list is history. Keep your head up strong. You’ll never walk alone!
Same story, same tips, but I started with SuSE Linux 4.3 in 1996. Just try stuff, read the error messages, read docs and ask. A lot of peaople who know stuff are happy to help out of altruism or the chance to show off. ;-)
Skeptical. Writing a graphical UI toolkit is a freight train of work. I’m positively curious about anything that’s not GTK but I’m not sure going with a new toolkit is the right decision. Qt is the mature kid on the block that’s been proven in more environments than I can count. Moreover it’s a complete application framework with a ton of convenience libraries needed for speedy development already included. I guess those can be supplanted in the form of separate Rust libs. Personally I’d have gone with Qt for such a project but I’d be happy to be proven wrong.
This is coming from personal experience/opinion, but after trying to create a simple app in GTK4 Rust bindings I was so confused because of how alien the programming style was compared to typical Rust programming. After trying Iced it was much simpler and made so much more sense, no silly decorators or anything, you can define the view and the update loop separately, and interactions are handled by messages using pattern matching. The inheritance based OOP doesn’t work well with Rust, and Iced has none of it, because it was made for Rust specifically.
I’m guessing QT bindings are similarly in a different style of programming and can’t imagine that meshing well with native Rust code. Iced has a lot of merits to it and having the opportunity to both help it develop and use a native Rust framework in a Rust project makes a lot of sense.
Maybe because he’s not “American” and comes from a country with regulations like the rest of the world, and people care when they vote to make things work.
And like most of the rest of the world, there are more than two political parties, and is not a drama show.
He has American citizenship and lives in America, he’s talking about America here. And I promise you that other countries, yes even those in the magical fantasy land of Europe, also have lots of political drama despite having more than two parties in the government (They tend to form alliances based on left/right and split into two blocks anyway).
I know, im from Europe.
The drama is not compared to USA, we don’t vote on celebrities.
In my country we even have a party for the animals and climate, so when USA still trying to vote for basic rights, we already ahead and vote for animal rights and more climate change.
Welcome. Sure, Linux Mint’s WebApp Manager or Peppermint OS’s Ice are here for you. But jokes aside, sadly, no. Lemmy does not have a native Linux application as of now. But you can make use of the fact that the browser UI is a PWA which can be installed like a regular app as well.
Proper PWA support isn’t in v0.17.3 (although mobile browsers will let you add it as an app). However, PWA support was merged into the main branch. I’m not sure which release it will be a part of though.
Ubuntu is the stepping stone from Mac/Windows to Linux. Like the tutorial level. It’s also one of the most “corporate” Linux OS vendors outside of RedHat. Of course it’s shitty lol.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.