• 0 Posts
  • 761 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle

  • As others have said, macOS does not “just work” anymore.

    I am primary tech support for a few “normy” users including my mother and wife. My wife, the more technical and capable of the two, uses macOS. My mother uses Windows. My wife requires substantially more tech support. Worse, the issues are often complete mysteries to me like “why is everything so slow” and it turning out that some OS level process is consuming huge amounts of memory and / or CPU. Web searches reveal lots of people with similar issues but no real insight into what to do about it or why it is happening. I have moved OS versions just to solve this kind of crap on Mac. Another problem is software not working on older versions of the OS.

    I am no Windows lover but, once I show my mother how to do something, I never hear from her. Every once in a while I stop by to marvel at how many updates need to be applied but that is about it. She is in the Windows 10 that I installed for her many years ago now. It just works.


  • While I understand the sentiment, we have to understand that Open Source developers work on projects that motivate them.

    So, we can have a single example of each of these but they do necessarily get any more devs. In fact, if you take economic theory ( competition for example ), it is likely they attract less attention individually than they do competing as part of an ecosystem.

    It would certainly help on the user acceptance and commercial software side where choice is an impediment. But, if we are just talking resources, limiting the number of projects only works if you pay people to work on them.

    Why was each of these projects started ( eg. window managers )? The answer is simple. It is because the founding developer did not like any of the existing options.


  • That is honestly a decent analogy. So, on what rides is it ok if something goes wrong and a young family member is killed? Rust says, it is never ok so we won’t let you do it.

    To use your analogy though, the issue is the driver feeling quite confident in their skills and rating the risk as low. Then a tire blows on a corner. Or somebody else runs a red light. Or, there is just that one day when an otherwise good driver makes a mistake. History tells us, the risk is higher than the overconfident “good” drivers think it is.

    In particular, history shows that 70% of the real world injuries and fatalities come from passengers without seat belts. So, instead of each driver deciding if it is safe, we as a society decide that seat belt use is mandatory because it will prevent those 70% of injuries and fatalities ( without worrying about which individual drivers are responsible )

    Rust is the seat belt law that demonstrably saves lives regardless of how safe each individual driver thinks they are. It is a hard transition with many critics but the generation that grows up with seat belts will never go back. Eventually, we will all realize just how crazy it was that they were not always used.





  • So, somebody that was generating no revenue for Red Hat is not generating revenue for Red Het? Sounds like a real catastrophe for them.

    Also, if I had to guess, I would say that Azure Linux is based on CentOS Stream. So, whatever “halo” they had before is mostly still in place.

    Most importantly though, LinkedIn is owned by Microsoft as is Azure Linux. So I am not sure what kid of bellwether this is.

    Are they most using Azure Linux? Or Azure? If Azure, no headline. If they are not using Azure, why not? That would be the headline here.


  • Perhaps the fact that Google is keen on Rust internally is part of what Ted Tso does not like about it ( he works for Google ).

    Many outside the Rust community see the enthusiasm for Rust as overblown. Perhaps they think that pushing back on Rust to create a brake on this momentum is restoring the balance or something.

    One thing I have noticed, when devs push back on inferior languages, they are able to cite all kinds of technical reasons for doing so. When they cannot come up with reasons, perhaps that is evidence that the language is pretty good.

    Ted’s rant basically says “we have more code so we matter more and that will be true for a long time”. I agree with the assessment that this kind of blatant tribalism is “non-technical nonsense”.



  • The “fork” is the real version of Mono and Microsoft is not giving it up.

    The repository managed by “The Mono Project” still targets .NET Framework. Microsoft does not care about the official version of that. Why would they want to manage an Open Source replica of it.

    In some ways though, this is good. Nobody should be seeing the Mono Project as a viable cross-platform development framework at this point. It is nothing more than a support layer for running legacy software that was originally Windows only. That makes it a good fit for Wine.

    If you want what Mono used to be, a cross-platform application framework, you can just use the actual .NET from Microsoft. It includes the Mono runtime for targeting mobile platforms and Microsoft continues to actively develop it. They are not passing control of that to anybody.



  • Ladybird was originally started as a browser for SerenityOS, a POSIX operating system. Well into the project, they decided to make it cross-platform but that still meant POSIX ( Linux and macOS ). As interest ( and sponsorships ) came in from outside SerenityOS, focus moved more and more to the browser and away from SerenityOS.

    Just recently, Ladybird decided to split from SerenityOS, allow more outside code, and in fact has dropped SerenityOS as a supported OS.

    The project is fairly pragmatic. I am sure they will add Windows support as the core browser engine matures.








  • The problem with this question is that most NVIDIA owners will have experience based on a very different stack than you will experience.

    NVIDIA and Wayland have had very big problems that have only recently been resolved. If you are using a very up-to-date distribution then you will have a great experience ( see other comments here about EndeavourOS for example ). If you have a distribution that does not have the latest, there will probably be issues.

    AMD has been the clear go-to choice for Linux for years. It is still a safe bet. The safest bet based on history. That said, AMD does have issues as well and with the NVIDIA issues now resolved it is not as clear cut. NVIDIA may actually be the better choice.