Just install and enjoy!
The truth is impartial. It just is.
That just made me laugh.
I was allowed to experience something similar in my Manjaro time there. And when later, when I was already at EOS, I asked there the somewhat provocative question, how it can be that in the stable version of M. more problems occur than in the base of Arch, which they call Testing, I was banned. Just do not tet the sacred cow on the tail …
Which obviously works only in theory.
This is not bashing when people share their experiences here. The fact that many of the experiences are rather negative is not their problem.
Good heavens! It’s way past time for a change! How on Earth did you manage so long?
Welcome to the forum!
You know me, Rick. I always aim to please.
What kind of work do you want to get done? EOS is fine, its Linux. The installation process is straight forward as you can choose which DE to install along with other software. There is not a lot of 'bloat on your first installation. Just update the system every few weeks and you should be fine. You already know LInux/UInix.
I have EOS on a few intel duo cores wit 3 to 4 gig of memory and it runs fine. What slows it down and eats memory is the browser.
So,do it, what do you have to lose?!
I am still using Manjaro - since Q32016 - the first thing I did when I realized the branch model - was to change to unstable branch - I have been there since.
Most likely this is the root cause of me not having any serious issues with a non booting system - unless of course I tinkered a wee bit to much.
I use the manjaro-tools to build my own customized installs - there is no easy way to the same on Arch.
That is not provocative at all.
Manjaro stable causes more issues due to the general availablitiy of AUR in Manjaro Stable branch.
Many Manjaro users doesn’t realize the difference and think AUR is available - why shouldn’t I use it and they are correct - why shouldn’t they? Because a lot of them doesn’t know their system - doesn’t know the subtle interaction inside the theming targeting high level abstractions in the framework which may change on updates.
I sometimes get a big smirk on my face - hiding behind my hoodie - because I see a lot of the same issues here as I see at Manjaro - users venturing into the Arch platform and banging their heads against the issues we all have tried.
You can as easily break EOS as you can Manjaro - just apply some outdate theming to Gnome or Plasma especially SDDM - and you will get the same fun.
Or install virtualbox-ext-oracle from AUR when you are not using the latest virtualbox package - and I could go on.
You should have known that this should not be asked on the forum there.
I think Manjaro’s unstable/test branch has packages updated as often as Arch/EndeavourOS.
There is some truth in this as well, the only small difference is that EndeavorOS is much closer to Arch than Manjaro.
I think that is correct.
The only packages really setting Manjaro unstable apart from Endeavour OS is kernel and kernel modules.
The vast majority of packages are the same as Arch.
There is some packages which are excluded when synced Arch wither because are very specific to Arch, would create issues on Manjaro or Manjaro has created their own versions of them.
I agree with that. Since the kernel is an essential part of the system, why is it given less attention in Manjaro than in EndeavorOS? Manjaro is very stable and wants to be user-friendly, so it excludes some Arch-specific packages and replaces them with its own. In any case, as long as I mainly used Manjaro, despite the stability, I experienced more errors than when using the “unstable” EndeavorOS compared to Manjaro. I installed the same AUR packages for both, so there could be no difference between them.
Tell that to Debian users.
Problem is AUR packages follow Arch, Manjaro (stable) is few weeks late behind, sometimes updating AUR packages is a PITA with Manjaro unless you do it right after a big update (python stuff in particular).
Okay, yeah. That’s positively ancient. My laptop is 9 years old, but it at least has an i7. Any plans to upgrade?
What are the specs of your wifi chipset? Bandwidth?
Yes, to stay stable enough, Manjaro releases new packages every 21 days on average. This is a compromise, so some packages may have unfulfilled dependencies.
The thing is we don’t pay any attention to the kernel. Arch devs do
Network:
Device-1: Ralink RT5390R 802.11bgn PCIe Wireless Network Adapter
vendor: Hewlett-Packard driver: rt2800pci v: 2.3.0 bus-ID: 01:00.0
Device-2: Realtek RTL810xE PCI Express Fast Ethernet
vendor: Hewlett-Packard driver: r8169 v: kernel port: 2000 bus-ID: 08:00.0
Bandwidth is a bit higher than I could have bought ten years back. It’s what I could afford now, and not a computer with 64GB RAM and related specs.