• 2 Posts
  • 86 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle
  • devfuuu@lemmy.worldtoLinux@lemmy.worldArch Stability
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    8 days ago

    I had so many problems and had to constantly manage other distros before Arch that it was a lot of anxiety. Everytime new release of popular linux distro I knew it was gonna break if I tried to upgrade. Almost centrainly. For fear of that I had frankstein monster distro for work using lts version full of weird ppas with a more recent kernel and some more recent software that I need because everything was always old all the time. It was horrible to maintain and keep working.

    Arch is just simpler, easier and much more stable. It’s just pacman -Syu all the time, have fresh software, recent kernels for the hardware improvements which is extremely important for when you buy new laptop and overall never crashes. It’s just a matter of reading the news, sometimes change a config that got deprecated, or replace some software that got abandoned or now there’s better alternative, etc. Sometimes things get some regressions for some weeks until things are bug reported and fixed upstream and eventually reach the system, but that’s waiting some weeks or rarely months. There’s always alternative to get involved in helping fix the problems with bug reports and patches if needed, but that’s extremely rare and only if you really are desperate.

    Anyway, those problems were much worse on other “stable” distros, because if there’s something seriously wrong on the system you are only lucky to get fixes after a major release which may happen only once a year.

    If the system is really critical and cannot fail me during work week I delay updating to the weekend sometimes. Even if I need to it’s just a matter of evaluating the risk. You do pacman -syu and see what’s comming. If it’s just some apps updating then it’s ok to do it. If it’s core system stuff like kernel, systemd, dbus, graphics drivers, maybe I’ll avoid it.

    Overall it’s simpler and easier because there’s really only 1 or 2 things to keep in mind and all the rest just falls into place.

    Using archlinux for more than 15 years on personal machines and maybe 5+ years on work computers.



  • I wish people would stop craving and talking about a potential switch 2. It’s useless. For those who want to game now the switch works fine, is good hardware, has lots of games and new ones keep coming and it keeps selling new consoles. They could not release a new switch for the next 5 years and it wouldn’t matter at all.

    This is all about the nerds of the latest and hottest tech craving for something new. Most Nintendo players are not those type of people.

    And it’s obvious that whatever comes next will fully support and run the current the games the existing switch, if not they wouldn’t be releasing new games for it.

    So stay calm and keep playing.

    Useless noise, so annoying.



  • Doesn’t rcs depend on having mobile data or internet access on? If I understand it right it is strictly worse than sms.

    Many people just have data off most of the time and sending messages with the system app assumes things are delivered immediately and everyone easily receives them. If you forget your data is off or don’t have internet for a while then you end up assuming people received stuff when they didn’t.

    All phone isps have basically unlimited sms for free when data is paid in huge amounts of gold.

    Sms > Rcs








  • Yeah, it’s a new way that programs use to draw their stuff on the screens.

    In the middle usually are other stuff that abstract away that part from normal application development, so in general, most applications don’t need to care with the low level thing that is being used to draw their stuff, but there is always somethings that some apps will do to bypass or expect to work in a certain way, so sometimes changes and time are need to adjust those applications to play well with the new way of drawing.

    The core idea of why Wayland matters is that it is designed to take advantage of the hardware features and how hardware is designed in this century. On xorg, since it was designed around the architecture and expectations of what people thought things should work in the 70s, it was becoming really hard to add features related to how newer hardware worked. Things like multiple gpus, prime architectures, multiple surfaces/screens with multiple aspect ratios and dpis, varying refresh rates, taking advantage of hardware acceleration for graphics drawing, etc, were all really hard things to do because the code had multiple concepts not applicable to the modern age. So, essentially developers were already bypassing 99% of the internals of xorg architecture and hacking things in a very hard way. They basically decided/experimented with stripping apart all the things they didn’t need and didn’t matter and reduced it to the most basic and core thing that mattered: “how to push these pixels to that surface”.

    It ended up being a successful experiment, in that it showed it was possible to do.

    Now, in the current world, there are solutions that need to be implemented to bring some features up to speed since the wayland thing is so core and barebones. And this is a good thing. It allows developers and applications to think really hard about what they need to do and how they should do and how things should work across all toolkits and desktop environments. Obviously this takes time to make decisions and ensure everyone is onboard, experiment and reiterate on it until good solutions are found.

    This last point is what makes end users frustrated when trying wayland because some things are lacking or not ready yet. For the general use, users without really specific needs, they can already use wayland now, but for others they can’t because of their particular needs or specific hardware situation.

    If xorg is working for you, then there’s no need to worry. If it’s invisible to you then most likely you shouldn’t care, because the desktop environments are changing their sessions to use wayland by default and most users will not perceive any difference. If users see problems and then notice that it’s related to using wayland they can choose explicitly to use the xorg version since it will still work for a while.

    Hope I didn’t make it too complicated now.


  • So you wanna go from home to school. The whole distance/trip can be done on a bus or your moms car. That’s a means of transportation. But, now people are creating a train and soon you will have another means of transportation that you can go to school with, by train.

    That’s it, Wayland is another means of transportation (newer) than the older means of transportation that existed for a long time, x11 or xorg.

    The route is how can applications show stuff on a screen, what transport should they use.