Comments by "Zer0" (@ForeverZer0) on "Brodie Robertson" channel.

  1. "Yo dawg, I heard you like articles, so I wrote an article about your article" -Journalism in a nutshell
    115
  2. Zig isn't quite ready yet, but it already synergizes with C much better than Rust ever will in both language design and its community. A large portion (most?) Zig devs are also C devs, use C in their Zig projects, build C projects with Zig's build system, etc. There is mutual respect between both groups, not one group forcing their way into a project and making demands.
    47
  3. Just let the OS clean it up when we are done, amirite? I say we stop concerning ourselves with trivial matters like RAM, and just treat our applications like one big arena allocator managed by the OS. If we run out of RAM, we can always download some more, so win-win.
    31
  4. Oddly enough, switching between Linux and Mac is relatively easy, as they both adhere more strongly to UNIX principles, file hierarchy, the concept of package managers, etc. I would disagree with your comment about things changing too quickly, that is completely your choice. There are multiple iterations of each major desktop environment, but there is nothing so drastic between them which would make someone not know how to use them from one version to another. For people who like things to stay the same, there is Mate, which is based on Gnome 2, which was released in 2002, and is till going strong as a popular desktop. Windows 7 was released in 2009 and is well past its end-of-life and support cycle.
    25
  5. There is no such thing as a memory-leak safe language, and likely never will be. The misunderstanding comes from three things: 1. People who don't write systems languages and don't fully understand the difference 2: Rust zealots constantly boasting about how safe the language is and often implying such indirectly 3. People love to hate Rust because of #2
    20
  6. It should be noted that this is not exclusively an "Ubuntu" problem, as "needrestart" is not developed specifically for Ubuntu, nor maintained by Canonical. The package is also available on other distros via their package manager, Ubuntu Server just comes with it installed by default.
    20
  7. LowLevelLearning did a really good job explaining the exploit, as he usually does. It is actually an impressive exploit, kudos to the random guy who found it by digging into why his logins were taking longer.
    17
  8. False dichotomy. There are other tools like (i.e. Valgrind) that can be used to alleviate most memory issues without the need for Rust. We don't all need to drive around wearing helmets and 5-point harness with a roll-cage for a trip to the grocery store either. Being "more safe" isn't always practical, there is a balance that Rust developers seem incapable of acknowledging when making hyperbolic analogies like this. Memory safety is a obviously a good thing, and Rust does it well, but this is not the be-all-end-all to development like Rust users think it is, even for kernel/driver development.
    15
  9. I literally add custom "Conduct Yourself However You Want" CoC to my projects. It is pretty brief, but essentially just states that I am not your mother or your spiritual leader, and am not going to dictate how you act. If I don't want you interacting with my code, I will remove you, simple as. I don't need an excuse or exhaustive list of nebulous and subjective buzz-words to describe it. People really need to stop being so sensitive about everything and come back to reality.
    15
  10. I wish it was simply a matter of them being too old to understand, unfortunately time after time has taught us that it is more a matter of who is lobbying for them and writing the biggest "donation" check to their campaigns.
    14
  11. I am not against the inclusion of the protocol whatsoever, but there should always be someone who pushes back, even if only playing devil's advocate, and make the advocates make a case for it. Adding features just because someone, somewhere, might find them useful is how you end up with X11, where no living person knows the entire API.
    14
  12. Your point is well-taken, but let's not pretend that the stereotype doesn't exist for a reason. I don't think anyone is under the illusion that drama is exclusive to Rust, but is the the chief offender in the entire ecosystem. Wayland drama is usually people (such as Brodie) over-dramatizing what is going on, while Rust's drama often stems from over-emotional public temper tantrums by its most notable users.
    14
  13. The same can be said when comparing kitty, alacritty, and wezterm, etc. Ghostty is just another addition to this group of high-tier terminals. Reasonable people will disagree on which is best, and it is no one's duty to try and sell you on which one is good for you, the decision is yours alone. If you like it, then use it. If you prefer kitty, then use that, the feature-set for each is on-par.
    13
  14. People/groups with their mindset never do, they will go to their graves blaming their woes on everything but their own actions (or lack of), and will continue to double-down. If they loose half their user-base for banning people, they will simply ban members who bring that up as a topic of concern.
    12
  15.  @TheBlueThird  I completely agree that X11 will be around for (likely) decades longer, but at this point, Wayland has already displaced it for the "top-spot", and the major distros/DE's are shipping with it as the default session type. It won't be long before X11 support becomes a second-class focus for projects, and you will start seeing "this feature is not supported on X11" instead of vice-versa.
    12
  16. You will take the webp and you will like it.
    10
  17. Memory safety and memory leaks are unrelated to each other. Rust offers no more/less protection from memory leaks than any other language does. While it is an understandable misconception, novices and non-programmers seem to conflate the two concepts quite often.
    10
  18. There are numerous reasons "why" Windows is popular for desktops, but the most dominant reason is simple: new computers come with it. There is a few niche manufactures that offer Linux. and of course System76, but this is generally true, and will ensure that they always stay on top. Linux users simply expect to reinstall their OS when purchasing a new machine, and everyone else expects Windows and isn't using Linux anyways, regardless of how terrible it is.
    10
  19. ​ @isofruitfruit9357  Perhaps I am simply misunderstanding the term, but what was "racist" about what they said? I thought DEI was "diversity, equity, and inclusion"? Does that exclude a particular race?
    10
  20. I don't particularly have an opinion one way or another about password managers, but there is legitimate and logical reasoning to that argument. I would say is most fair to state that managers simply move the problem-space. Technically managers are adding a new attack vector, but are likewise helping to alleviate human-error. Comparing these two is apples/oranges in regards to which is more "secure", and will vary greatly from user to user.
    10
  21. Ironically the growth of AI garbage is helping GPU vendors support Linux more, as it has expanded the industry to be more than just game studios who choose DirectX because of the Microsoft money. Realistically Vulkan and DX12/D3D are comparable technologies, they are both abstractions over the same hardware instructions, but Vulkan being open-source and running natively on Linux platforms makes it more attractive to the expanding industry which relies heavily upon Linux. I doubt we are going to see a bunch of AAA game titles coming out with native Linux versions anytime soon, but this is one small step towards it.
    9
  22. I honestly think that for newcomers, it is more important to explain the difference in desktop environments, and worry less so about the distro it is running on. They will learn the differences and experiment on their own in time, but it is not beneficially to overload them with distro names that are all equally meaningless to them. They are going to base their initial experience based on what the DE is, not the nuances of package management, init systems, X11/Wayland, etc, etc., which are foreign concepts to a Windows user anyways. While I don't neither a DE nor a Debian(-based) distro, my typical approach is to have them look at screens for GNOME and Plasma, decide which they like better purely based on aethestics, and then choose a popular Debian(-based) distro that supports it. They can experiment and distro-hop all they want later, just get them up and running with something that isn't broken, and they enjoy the appearance of.
    9
  23. I choose not to create a a bot-net with my kitchen appliances.
    9
  24. I see what you did there lol
    9
  25. They wouldn't have removed it if were just under consideration, full stop. I can't even envision a scenario where they haven't already entered into legal agreements with buyers of the data. Businesses simply don't make these kind of changes based on "well maybe someday in the future if the opportunity arises", especially when it obviously is going to have a negative impact on public perception.
    8
  26. I feel guilty for not having yet invested any time in learning it, I have still being using OpenGL for my hobby games.
    8
  27. I embrace vaxry in both his project and how he treats others. Whatever he is, his way seems to be working better than what HR-inspired institutions like the FDO, OpenSUSE, etc. are currently doing.
    8
  28. ​ @tragivictoria  Literally not true, nor even make sense, unless you are mistakenly confusing FOSS for the the Free Software Foundation (FSF). Surely you aren't claiming that every person who pushes to a public repo is making some concerted political statement?
    8
  29. ​ @bigmistqke  If you "heard" it, does that not by definition make you one of 'le bad people" that it was intended for? Keep in mind that despite being only 13% of the population, 51% of YouTube viewers hear dog whistles where none exist.
    8
  30. "We are just asking for a little documentation" is the salesman's pitch. I assume every person in that room is smart enough to read between the lines, especially after the first ~10 minutes that preceded it were a presentation on how Rust makes everything better is and is superior to C, in a room full of C devs who are likely sick of hearing the same pitch over and over.
    7
  31.  @GSBarlev  It should be noted that a memory leak is mostly unrelated to "memory safety". You can create memory leaks in every language quite easily, including Rust. What you can't do in Rust (without effort) is access illegal and our-of-bounds memory.
    7
  32. ​ @PerilousBooklet  Non-Arch users think that using software within a month of its stable release by the upstream developer as "bleeding edge". I can't count how many times that I have encountered someone who is literally under the impression that Arch is running something akin to "nightly" builds for every package.
    7
  33. You will never regret your choice. I jumped to Linux during the Windows 7 era, and am affirmed in my decision with every new Windows "feature" that gets added. The initial growing pains and feeling foreign goes away, and eventually Windows will feel like the foreign system; you will wonder how you ever used something so clunky and unintuitive. Windows feels intuitive to Windows users only because it is the baseline that most first become familiar with, not because it actually is. I don't believe I have ever heard the story "long-term Linux user switching to Windows and loving it!"
    7
  34. This is GNU+Linux level of pedantry....
    7
  35. I abandoned GUI music players years ago. I wrote a custom MPD widget for waybar and use ncmcpp/mpc for the occasional management of playlists, but don't even remember why I ever used a full-blown graphical interface for music. I did used to use Guayadeque, but it was sadly discontinued.
    7
  36. @ "reported". lol, this is like poetry. What a wild world we live in where people get reported for using a percentage.
    7
  37. I don't even understand how they could nuke it mid-version if they even want to pretend GTK is semantically versioned.
    7
  38. Developers are rarely the ones that do this anyways, even more rarely for companies to do that. They just release a tarball and the package maintainers for the respective distro do that. This is a non-issue.
    6
  39. Perhaps I am missing what you are saying, but why do you need flatpak in order to backup a Wine prefix?
    6
  40. Don't assume there isn't drama in Microsoft, Apple, etc, they simply don't have a public mailing list. If you ever work anywhere, I am sure you can think of examples of inner-company drama, now pretend that it is posted online, that is the only difference.
    6
  41. Gee-Lib-See. This is how I pronounce it, what do others do? I won't change how I say it regardless, just curious.
    6
  42.  @UlcerousAxis  The comments section on YT regarding a video with a tangential political connection is not open-source code. No amount of cope or gaslighting is going to change my mind about this commonsense and self-evident truth.
    6
  43.  @cyberpunkspike  This isn't Google vs Mozilla, they are both bad, don't try to move the goalposts.
    5
  44. No such thing as hate speech. People can be rude and insulting to others, but it is silly to make a special scary category of rudeness just because they hit you in the feels harder.
    5
  45. Let us not forget when Manjaro pushed out a bugged version of their package manager that turned all their unwitting users into a combined DDOS attack against the AUR, making it unusable for nearly all Arch (-based) users.
    5
  46. As long as people continue to support it, even if only out of ignorance or lack of technical know-how to switch, there is little incentive for Microsoft to ever change their ways, if anything it only enforces these terrible practices. No one other than Microsoft have ever accused Microsoft of being an ethical company.
    5
  47. It only takes one or two people with that specific ideology to acquire a foothold somewhere in the company leadership. From there, they can wield self-proclaimed victimhood as a weapon to silence any opposition, and they get whatever they want by using the same old tropes and buzzwords like "safety" and "inclusion".
    5
  48. Meh, this particular one was a bit of stretch to make content IMO. I don't mean that as insult, I love the channel, but that is my thoughts on it. The issue isn't nearly as dramatic as this. Reverting a change the maintainers didn't desire to begin with, after years of the actual responsible party not fixing their problem, and it results in a very small number of Arch users playing a very small number of old games not working.... am I missing something? This is a subset of a subset of subset of Arch users. Comparing the LoC of the patch, which are build flags and not indicative of what it actually pulls in or wider implications, is a serious stretch....
    5
  49.  @boredstudent9468  Actually, not a Linux nor Arch problem. If an update, of any distro, is bricking your system and not others, it is obviously something unique to your configuration. Not learning what you did to cause it will ensure it happens again, and throwing your hands in the air and blaming the software ensures you will never learn it.
    5
  50. Same. I am truly glad to see a brand new DE enter the fray that isn't based on Qt or GTK toolkits, this is a very good thing, but I am content with Hyprland, and haven't seen a single thing that is compelling enough to warrant a change.
    5
  51. @ Despite being a very small portion of the population, name the group that is responsible for over 50% of a certain type of crime done against children. Care to take a guess? Which offends you more, the statistic, or the crime?
    5
  52. They each have their strengths/weaknesses, it is simply a matter of which one you are accustomed to. I spent most of my life using systems with floating windows, first Windows and then various Linux DE's, most of that being Plasma. Now that I have used tiling window managers exclusively for 4-5 years, my experience would be vice-versa to use a floating manager, I have not done anything worthy of envy other than use a tool that fits my personal workflow better.
    4
  53.  @No-mq5lw  The learning is the hobby. I don't release, nor even try to hard to finish any game, just like creating the engine, design, etc. I am terrible at artistic stuff, so it is a hopeless endeavor anyways xD
    4
  54.  @budgetarms  Your point is well-taken, but there is a difference between having a loyal following and causing drama everywhere you go. Zig has a cult-following, literally aims to be "better C", yet C and Zig communities have mutual respect for each other with little/no drama whatsoever. It is likely a vocal minority of Rust users who give it a bad name for others, but this minority seems to be its entire leadership, both in the foundation and the community. We unfortunately only ever see the worst-of-the-worst, as the "normal" users are simply minding their own business.
    4
  55.  @lorenzo42p  I understand, I do it for a living. If my failure case is not failing when it should be, it is a flawed failure case and not accounting for something. Not failing is still informative.
    4
  56. Probably the same thing it says when the entire Linux ecosystem and Linux itself is clearly technical people going out of their way to not use Windows. You forget that pretty much every single Linux user was once a Windows user, and had to go out of their way to remove, reinstall, and learn a new OS on their computer.
    4
  57. They are typically going to be one of: kitty, Alacritty, WezTerm, and now Ghostty. I like Alacritty, but the lack of literature support is a deal breaker, as I use a terminal-based editor for writing code, otherwise any one of those are great terminals.
    4
  58.  @shApYT  "sudo !!" ftw
    4
  59. The for-profit Mozilla Corporation thanks you for your previous donations to their Mozilla Foundation tax write-off.
    4
  60. I have a philosophical aversion to flatpaks, snaps, etc. I understand their purpose in theory, just never actually had the need for them in practice.
    4
  61. This can be done on other systems as well, but Plasma most definitely makes it easiest to do, even on the fly by just clicking the title-bar and opening the menu. It is a "first-class citizen setting" on Plasma, not buried in a configuration or require additional tools just to get the window class for matching, etc.
    4
  62. ​ @zizlog_sound  I agree, but to be fair, nearly all distros are just toy projects where someone wanted to make their own "default" configuration, selection of installed software, and branding. There are realistically only 4-5 relevant distros, which all others stem from, and they all exist without any consequence whatsoever to the ecosystem. Unless you are writing some uber-specific software (i.e. package management), there is no such thing as developing for a specific distro that other distros will not also benefit from.
    4
  63. I guess it does if you consider every normal discussions like this "drama". There doesn't even seem to be anyone in disagreement here, just a few people discussing possible amendments to a the wording of the guidelines to better cover edge-cases.
    4
  64.  @penguin86bitals  Exactly. I think this is a huge misconception that people who don't write code, but are somewhat familiar with technology, do not understand: memory safety has nothing to do with memory leaks, it merely means a program cannot access illegal/out-of-bounds/garbage memory by accident. They seem to equate "memory safety" with "prevents all memory bugs", which is patently false.
    3
  65.  @jfbeam  This confirms something that I had questioned, though I have never done any kernel/firmware development with Rust to know enough to make the claim. I don't even know how one would write "memory safe" code when interacting directly with hardware, though my experience is limited here.
    3
  66. I honestly never found any of the zsh plugins worth using. Most seem to be just huge collections of worthless aliases anyways. Aside from the P10k theme, I just have my own functions/scripts for the things I need.
    3
  67. When I have to use a floating window DE, Plasma is definitely my choice over GNOME, but I am way to wed to tiling WM's as a part of my workflow to use it at this point. Muscle memory for my hotkeys is hella hard to overcome, and trying to recreate it in a floating DE feels like a cheap replacement.
    3
  68. Yeah, that is surprising. I know many people (both personally and online, communities, etc) who have made the switch FROM vscode to superior terminal editors, but it is extremely rare to hear of someone switching FROM one of those to vscode.
    3
  69. I haven't personally had any problems with wine on Hyprland (...yet), but native Wayland support with wine is one of my top "wishlist" updates to get among all Linux software. I know there is the wine-wayland project, but it isn't without its caveats, and does not work with things like Lutris, etc AFAIK.
    3
  70. I exclusively use Linux, and hate Windows, so believe when I tell you that no one is going to hold it against you for using Photoshop for image manipulation. I think GIMP is a fantastic tool, but no one honest is going to try and imply that it is even close to being equivalent to Photoshop at the professional level. GIMP being free and running natively on Linux is its only advantage over Photoshop. Adobe owns the market and has the resources to make sure it stays ahead, so there is no shame for GIMP, the fact that they are even mentioned together is testament to GIMP's power, but it is not even a competition between the two for anything serious.
    3
  71. @ Perhaps it does, neither of us can argue with the results. I don't need to be his friend, that is not what open source code is about. "Does he write code" is literally the only important factor. I have better things to do than police the words that people say online, least of all the ones they write on their personal blogs. EDIT: Also just wanted to say that the project has over 400 contributors and nearly 2000 PRs merged. There is no reality where "just developing the project on his own" is even remotely accurate.
    3
  72.  @__Brandon__  Any language that interacts with IO is capable of a memory leak. There is nothing "broad" about it: there are zero exceptions. I would be happy to show you a memory leak in standard Haskell code if you can't find one with a basic search.
    3
  73.  @undefinedchannel9916  Skill issues. Jokes aside, their is nothing Arch-specific regarding trackpad, this sounds more like an issue with your desktop environment and/or configuration, which actually installs trackpad-related stuff as dependencies. With the exception of pacman, its related libraries, and a few utilities like arch-chroot, archlinux-java, etc , there is absolutely nothing in Arch that is unique to or maintained by the distro.
    3
  74. They exist. While I know there are more, Alpine Linux is probably the most popular one. I think other distros like Void Linux could be setup to be GNU-less also, but my experience with it is rather limited to say that definitively.
    3
  75.  @isofruitfruit9357  I still don't understand, and you did not answer the very basic question: is DEI exclusive to particular races? If yes, then DEI, by definition and on its face, is in-fact racist. If not, then there is nothing racist about what the previous person stated, and it is unclear why you would perceive it as such. There is nothing complicated about this that requires an essay, which I can only surmise is intended to obfuscate that which is self-evident.
    3
  76.  @WMan37  The drivers (i.e. dxvk and others) can be local with the game folder, that's what wine overrides are for. Many installers for games on Linux do exactly this. I understand that you are settled into your familiar way of doing it, but nothing you listed is somehow only possible with flatpak. Many others do it their familiar way that accomplishes exactly the same end-goal without flatpak. A binary driver sitting in your trash folder works just as well as one in /usr/lib, you just need to make sure your game/prefix knows how to find it. Neither is better/worse, and I am not recommending against your way, you should do it the way you choose to, but just informing you that you are not actually reliant upon it for the same result. If for some reason you couldn't use flatpaks, there are alternative and common ways of doing it you could explore.
    3
  77. ​ @kxuydhj  I agree, while I strongly dislike Snap for the technical aspects of it alone, my primary gripe is for philosophical reasons. Being pushed hard in an inorganic way by a corporation gives me strong Microsoft vibes that I personally choose to steer well clear of.
    3
  78.  @rjawiygvozd  I think it is hard to call it great, or even good, as the idea behind it is flawed from the start. It's main primary selling point is that it tests for longer and is supposedly more stable, but then it allows users to install from the AUR, which is intended for Arch and its packages that are already out of testing, causing actual instability that far exceeds anything an extra few weeks of a testing phase would accomplish. If we ignore this, you are left with what is essentially a re-branded Arch with a selection of software somebody else likes installed for you, and a GUI to downgrade the kernel, which is of course only going to cause instability. It is unironically far, far more unstable than a basic Arch install could ever be. I prefer vanilla Arch, but if I were to recommend a distro based on it, it would not be Manjaro, but something like CachyOS or Endeavor that actually do it well.
    3
  79. I highly doubt, 1.4 isn't even in repos of rolling-release distros yet, let alone become a hard dependency of software that uses it, which likely wouldn't even have adopted it yet either.
    3
  80. 16 series are still perfectly good cards, have no shame. As a fellow broke gamer, I have learned not to get caught up in chasing the latest and greatest, my lowly 1650 is still playing Cyberpunk on Linux at 70-80 FPS with a mixture of medium/high settings.
    3
  81. I am indiscriminate in where I place my blame, and apply it equally to the entire web-development industry, whether someone is a "developer" or "designer" makes no difference to me: all played their part in achieving the same end.
    3
  82.  @bigmistqke  Because you stated that dog-whistles are only heard by two groups, so you must belong to one of them since you heard it; It is testing your logic. If it is neither, then it would indicate you are just making things up as you go along.
    3
  83. ...he stated between bites of skin that he peeled off his foot during a lecture...
    3
  84. @ I seen your replies to other comments, and have come to the conclusion that you are either a Mozilla employee or extremely naive.
    2
  85. Ironically the original reason that led me to switching to Wayland was that wine was not running a game I wanted to play, but for unknown reasons it would work in Wayland (I assume using xwayland). I never did investigate the root cause, but I eventually ended up switching my primary machine to use a Wayland-only environment, a this situation caused me to give Wayland a second-look and realize that it was now viable for full-time, daily driving, even on my Nvidia card.
    2
  86. Doubt.
    2
  87. Why would anyone ever want to use either of them?
    2
  88. If there was ever an application that screamed to be rewritten in Rust, it is this one.
    2
  89. I am in the same boat. I can see the benefit with servers, but I just don't see any reason to bother with it for personal desktop environments.
    2
  90. Is this satire?
    2
  91. Exactly. The proper name of an application should not have these type of bizarre and arbitrary restrictions. Most sensible repo-type sites use a "display name" and separate "slug" for a unique identifier that is more restrictive in its naming convention. This is a pretty standard model that has worked forever, allowing the best of both worlds, not sure why they chose to turn it into this silly mess.
    2
  92. People/groups with their mindset never do, they will go to their graves blaming their woes on everything but their own actions (or lack of), and will continue to double-down. If they loose half their user-base for banning people, they will simply ban members who bring that up as a topic of concern.
    2
  93.  @enderteck  I assume the irritation is coming from the pretentious "You don't know after 12 years ? Lol" part of your comment, not the correction itself. The "I am just here for educational purposes" stance falls flat after that.
    2
  94. NVIDIA is the bigger GPU manufacturer that is sold in more machines, so it kinda makes sense. I personally have never even owned an AMD GPU. I have nothing against them (I have an AMD CPU), I just have always used NVIDIA, have been happy with the results, and never was unable to overcome any of the NVIDIA issues that everyone blows way out of proportion.
    2
  95.  @szaszm_  The irony is that this extended testing period will cause greater instability for AUR packages for Manjaro users. If an AUR package gets updated on account of a repo dependency being updated, that new repo update hasn't hit Manjaro yet, and the package would be broken in the interim.
    2
  96. Rust is a perfect language for kernel development, just not the Linux kernel.
    2
  97. Bait used to be believable. Low-quality.
    2
  98. Is it capable of making sycalls or interacting with the file-system (the answer is yes)? If so, it can leak memory. It is that simple.
    2
  99. I am also confused why Brodie thinks that "works on my system" is somehow not an appropriate (and helpful) response in this context. It indicates the proof-of-concept for the error is flawed and not accounting for some significant factor. If it was a full-proof example of the failure, then it would have failed.
    2
  100. ​ @RenderingUser  There is not a person alive who is familiar with the entire X11 API, and that is not being hyperbolic. It is literally over 50 million lines of code, filled with tons of legacy stuff that isn't even relevant anymore. Saying "just maintain xorg then" is like saying "just stop being poor", it is not some trivial task.
    2
  101. Betteridge's law of headlines.
    2
  102.  @Adowrath  I don't have any strong opinions about him, but based on the bit of content that I have seen, he is indeed a pinhead. The "tech tips" is just slop for non-technical people. It is entertainment content, not technical, and his target demographic is obviously people incapable of distinguishing the two. Good for him though, I wish him continued success, but let's not pretend he is anything other than what I said above. If you like entertainment, then watch it, but don't confuse it with anything technical.
    2
  103.  @Adowrath  They are not mutually exclusive, I never claimed they were, I simply stated they should not be confused in this context, as his channel content lacks technical merit. Calling him "pinhead" was obviously not some vicious personal attack, let's stay grounded in reality here. It was an offhand comment meant to convey what I said: there is nothing technical about LTT, it is entertainment for non-technical people. There is no philosophical or deeper meaning here, it is just how human communicate.
    2
  104. I think its funny how quickly it has become fashionable for people to smugly remark with the exact same "over-hyped" phrase, and then inform others of their preferred terminal. The Linux community never fails to illicit cringe...
    2
  105.  @JamesMowery  I use Arch on some of my machines. If you disagree, you are free to offer a counter or point out what I said that was not objectively correct, it would be better than the passive aggressive edge-lord reply.
    2
  106. @ You see things that are in the public space, and you don't see things that are private and behind closed doors. This should not be revelation. Public projects have their disagreements publicly, proprietary ones do not. Of course you are going to get the impression that public projects have more drama if you ignore this basic logic. Have you never worked anywhere, in any sector? Now imagine that every disagreement at work was posted publicly online and people made reaction videos about it.
    2
  107. I will never understand why the Wayland protocol forbids applications from even querying the global position of the window. If security is the argument, the negligible gain of it compared to it breaking a significant number of application and/or forcing hackish workarounds is not worth it. I wish they would just let go and add it to the protocol.
    2
  108. Take the neovim pill, it is outclassing vim by leaps and bounds at this point. Using Lua instead of a toy language makes for such a quality of life improvement.
    2
  109. I was already a permanent Linux user before Windows 10, but it was the last version that I dual-booted with (no longer needed for gaming), but it was a hot-mess IMHO. I am not someone who can't acknowledge that Windows does have a few features that are superior than their Linux counterpart(s), but Microsoft's focus seemed to be making everything that I already disliked about Windows even worse, and moving farther away from the few things I liked. I honestly don't even know the difference between 10 and the current version (11?), they seem the same to me aside from some default configuration to the taskbar.
    2
  110.  @bigmistqke  So which are you?
    2
  111. I honestly don't mind my shell (.bashrc, .zshrc, etc) and SSH taking a top-level spot. I have no explanation why I don't care about those ones, just the way it is. That said, I absolutely hate software that doesn't respect it and creates entries in my home directory. It gets even worse when you have ones that don't check alternative directories, and then compound that with not even making using a dot file/directory. I typically keep dot files visible, but when giving a quick scan, it at least helps when doing a quick scan for something.
    2
  112. I don't personally like the entire concept of build scripts needing licensed. There has to be some commonsense line where we don't bother licensing code. If I share a line or two of Bash with someone to help them accomplish something, should it now be licensed? Of course not, but the same logic stands. At some point we need to just use commonsense. I never even considered "licensing" my build files: they are essentially just instructions on how to use the licensed code.
    2
  113. Alpha releases are a double-edged sword, hence it is much more common to see betas and/or release-candidates open to the public,while alphas are preserved to a much smaller and exclusive group. You risk turning off a large number of people when you release software in such a broken state, and it takes time for them to ever come back, and some never will at all. I do software development for a living (20 years), and would never have released the that alpha out in its current state. It is one thing to have some bugs, and even crashes, but it is a very bad to have overall performance so lacking this far into development. I would be interested in trying it again, but I am not bothering with anymore alphas or betas, and will wait for 1.1.
    1
  114. I prefer vanilla Arch, but after looking into it, I think CachyOS should be considered the "Easier-Arch with GUI installer" distro people should be recommending. Manjaro does deserve credit for helping bring an Arch-like experience to Linux newcomers, but it simply isn't even filling a niche anymore.
    1
  115.  @GrzesiekJedenastka  "Do not currently" and "won't in the very near future" are extremely different things. The ToS doesn't even take effect until April. Check again at the beginning of May, it would be a safe bet to say you will be disappointed.
    1
  116.  @GrzesiekJedenastka  I am far more cynical, and always assume malice until otherwise proven to be incompetence. The often-repeated quote is completely backward, at least now as it applies in modernity.
    1
  117.  @polinskitom2277  Mozilla Foundation is managed by the Mozilla Corporation (a proprietary, for-profit company), and are not reliant upon donations. Don't be fooled by the corporate financial model that companies use to avoid taxes.
    1
  118. ​ @lightyisreal  Last I checked, code doesn't care who typed it (as long as it isn't a woman).
    1
  119. No Arch user cares about a GUI installer, real life is not reddit memes. The issue is the how it would inflate the size of the ISO for little to no reason. There is no graphical framework included as part of the installation media, and to include GUI installer over the existing TUI one would also require the inclusion of all its many dependencies. The end result would be a less-advanced Calamares installer with colors instead of a more useful TUI with white text on black background. The existing TUI installer is super simple, there is no difference in skill level required to use it over a GUI other than using arrow keys instead of a mouse.
    1
  120. "What is the use-case?" is extremely disingenuous, and low-hanging fruit. Did you ask the same when Alacritty was released? At that time, other terminals like kitty were are already out, and had a larger feature set (still does). The same can be said for pretty much every piece of software in existence. I have yet to ever see this question asked in a genuine way, it is only ever used when someone wants to disparage a piece of software that they personally prefer an alternative to.
    1
  121. 3. People using Snap
    1
  122.  @Seacat17  Don't mean to rain on your parade, but Firefox doesn't support JPEG XL either.
    1
  123.  @Seacat17  "explicitly enabling experimental features in the firefox nightly build" != supported
    1
  124.  @Seacat17  It has been "on the way" in firefox for over a year, with no signs of being any closer than where it started. There are tons of features that stay experimental and are never merged. Both browsers have hundreds of examples of such a thing. I could have said "its in experimental branch" 3 years ago when talking about Chromium, yet here we are. The point is, that doesn't mean much.
    1
  125. @ I am not against JXL, I also want it to be supported, and was disappointed when Chromium removed it from the experimental branch ~1.5 years later, back before Firefox even added it in theirs. All we can do is hope that Firefox doesn't do the same.
    1
  126. There really wouldn't be anything to "implement", it would simply be a matter of exposing what already exists to the public API. We can safely assume that demand for such functionality is not very high, so it is probably currently best that priorities are being kept on more important things. Not sure why you assume "will never come", save perhaps it made for a more interesting video title and an excuse to share some little-known feature of X11 xD
    1
  127. It would improve multiplayer support, not really compatibility. Most games that use anti-cheat work fine single-player, but are blocked from ever being able to join an online server. I vaguely remember an article (somewhat recently) where there were talks of moving away from kernel-level anti-cheat on Windows, though I can't say if this was anything more than talk, or ever actually coming to fruition.
    1
  128. @ The internet is full of people we disagree with or perceive as rude. "Calling them out" isn't go to make it any better, and only ever makes it worse. This is simply human ego, tell someone not to say something that they want to say, and they will simply say it more out of spite to show you cannot control them. Chastising people online in an effort to conform their worldview to yours is never not cringe. Just ignore/block and move on with your life, random text online can't actually hurt anyone unless they choose to allow it.
    1
  129.  @rigierish3807  I totally agree, I have never understood the argument that "too many distros" is somehow harmful to Linux software development. I have been writing code for ~20 years, over 10 of them exclusively on Linux, and have never once developed for a particular distro, this doesn't even make sense unless you are literally creating a package manager or some other extremely niche application that is only intended for that distro. Package maintainers for each respective distro are the ones that create the packages for each distro, which is essentially just script to copy files to the proper location, run a compile script, etc. My compilation flags target CPU architectures and operating systems, not individual Linux distros.
    1
  130. I spent decades hating Vim and thinking people were crazy for choosing to use such an inferior and un-intuitive editor. Somewhat recently I took a second look at it (specifically Neovim), and spent a few days forcing myself to get familiar with motions, learning how to personalize it, and configuring with LSPs, etc., There is no going back to something like VS Code now. My editor is perfectly configured to something that works optimally for me. I would recommend that anyone learn Vim motions, even if you dislike Vim itself. They certainty don't seem very intuitive at first, especially with most modern software hacing left-hand-centric common hotkeys that use modifers keys, with right-hand combinations being less common due to mouse use. Spend a couple days forcing yourself to use them while working on a project,, and you won't regret it. I can now move around and edit a document faster than a mouse/touchpad by orders of magnitude, one only needs to learn the muscle-memory of the keys.
    1
  131.  @MusTheFan  Well done sir, made me laugh. o/
    1
  132.  @Poldovico  I don't believe there is anything bad faith about what they are doing, it is understandable, but they are over-complicating a solved problem that a plethora of other similar platforms do not have a problem with. This feels like a bureaucracy problem, where they felt they needed to cover every single possible edge-case and left out any room for a commonsense factor. If there is a human eye approving each anyways, let these be guidelines, and not strict rules, as the strict adherence often doesn't even make sense or even appropriate in many scenarios.
    1
  133.  @Poldovico  Yes, commonsense, that long-forgotten ethos people used to operate under prior to feeling compelled to create rules for every micro-facet of life.
    1
  134. A "layout" is a far more meaningful and accurate term, and does not use one that already has semantic meaning within the context of window managers/desktop environments. It takes some cope to try and make the argument that "this is akthually tiling". I understand that KDE does not intend nor designed it to be "tiling" as that word is understood, so calling it as such simply means it is not the most appropriate term for it.
    1
  135. 10:30 ghostty +list-keybinds Surely you are smart enough to figure this out. I honestly don't believe you didn't know, and am just going to assume you are dramatizing it for the sake of content.
    1
  136.  @rj7250a  There is a little difference in DirectX (<12) and OpenGL. If you learn one, learning the other can be done in an afternoon. They are abstractions over the same hardware instructions. John Carmack talking about old legacy OpenGL that has been deprecated for over a decade is hardly relevant. OpenGL 1.1 and OpenGL +3.0 are completely different APIs with practically nothing in common, where the former was what Carmack would have been referring to.
    1
  137.  @millsjonah  I technically could have the same problem TBH, but I personally only use wine for playing a few games now and then, all of which are full screen at launch. Now I am curious to test it with some windowed apps.
    1
  138.  @zezba9000  Which is why I don't recommend a tiling WM to someone coming from Windows/Mac and new to Linux, even though it my personal preference. I recommend they use Gnome/Plasma n order to get an experience that is most akin to what they are already used to. Everyone was new to Linux at some point, it is only natural to try and apply what you already know to something new. The differences will need learned, and the point is to make that experience as frictionless as possible.
    1
  139. Praise Kek
    1
  140.  @stupidburp  Yep, same reason we will never have cures for cancer, diabetes, etc, and only an ever stream of "new and improved" treatments. I use rolling-release distro for over a decade, so don't even remember what it was like to have different versions of my OS.
    1
  141. It will be ignored like every other existing solution to this same problem. People developing apps simply choose to use their own way of providing configuration, and don't use anything existing. I don't even use a DE, and the struggle is still real with terminal applications. Things like .xprofile and and .xresources have existed for decades, yet are ignored by all but a few applications. This means even getting uniform colors in a terminal requires changing a color palette in 10 different places, with slightly different name/value conventions and syntax.
    1
  142. SSH is your friend for remotely helping parents/grandparents, though not very helpful if something like network management gets broken...
    1
  143. Although I don't use any of their products anymore (neovim btw), JetBrains is another good one.
    1
  144. There are only Rust Zealots and people who don't care about Rust. This is true in a comparison about Rust and any language.
    1
  145.  @jonathaningram8157  I have a laptop with a very modest GTX1650 and play Cyberpunk at about 70-80 FPS on a mix of mid-high settings. Cyberpunk is not one of the few games that has problems on Linux, the modding community is even very supporting of Linux. DLSS works perfectly well on Linux, not sure why you even assume that, as both AMD and NVIDIA offer Linux drivers for their hardware. This isn't 2010 anymore, the performance difference between native Windows and Linux gaming is negligible. It occasionally takes a little extra tinkering on Linux, but even that is becoming very rare, and i don't even use Proton.
    1
  146. Arch was my first distro, and still using it over ~8 years later, even after venturing out and doing a brief distro-hop phase after first going to Linux, but came back to Arch. I have been writing code for 20 years, so was not afraid of the CLI, which I think is a the biggest hurdle for new users, who think a terminal is some mysterious black box that only hackers use.
    1
  147. I will need to find a new app to alias "btw" to...
    1
  148. I dunno, I tried to switch daily-driving a standard DE after using tiling window managers for a couple years, and I just can't stick with it. I was trying to use "Activities" and some of those apps you mentioned, and it was just never the same. I even spent the time to configure all the hotkeys to my personal scheme, but once you embrace using a tiler for your normal workflow, it is extremely difficult to go back to anything else. I legitimately like Plasma, used it for years, but tiling window managers have ruined me for floating style.
    1
  149. @ There are many cases of that, but also many cases not, evident by the comments to this very video. The truth that Rust also helps prevent memory-leaks more-so than some other languages gets way oversold. It is often portrayed as something uber-rare and/or explicit. Couple that to your run-of-the-mill JS bootcamp dev whose understanding of these differences may already be lacking or nonexistent, and they just hear "practically impossible unless you are trying to", which is far from reality. It isn't that any Rust dev is walking around saying Rust is memory-leak proof, they just over-exaggerate the guardrails against them compared to any language other than C. Most languages have guardrails against them to varying degrees, so comparing it to one of the few who has none is rarely a helpful discussion, and leads to misunderstandings for someone uses neither.
    1
  150.  @__christopher__  Of course not, but the memory the host OS/kernel uses for them does. When the kernel gives you back file descriptor as an integer, there is obviously more to it than just an integer: the descriptor is just a handle, and the kernel doesn't know when your application is actually done using it or if you just accidentally forgot to close it. In either case, there is memory allocated is not being freed. Your language isn't opening a file, the kernel is upon your language asking it to. As safe as your language is, it relies upon a kernel that it is not. Even if we pretend we have a "safe kernel" , it is not going to be able to distinguish between a logical error and something purposeful in your application.
    1
  151.  @no_name4796  The answer to "why" becomes obvious when you recall that the "non-profit" Mozilla Foundation is merely a shell organization run by the for-profit Mozilla Corp. Make no mistake, Mozilla is just as much about profit as Google.
    1
  152. I am probably wrong, but I had assumed that airbags used mechanical inertia switches. Using software for such a thing seems like over-engineering.
    1
  153. I used to have one from the Windows '95 era, but through it away. I deeply regret it now.
    1
  154. They didn't, they just got pedantic about the terms as they apply in this exact moment time, with no promise or backtracking about anything going forward. The point is to try and maintain the users they have whom have a low-IQs or don't really pay attention. They hope to fool peoples' perceptions with "Mozilla explained that they don't sell data", and continue using it, completely unaware that statement will cease to be accurate come April when it goes into effect. Only a fool would believe they went through their entire repo removing any reference to not selling data just for fun, they obviously have explicit plans to do so in the near future. I would be astonished if they didn't already have contracts signed with the buyers.
    1
  155. @ It has yet to reach version 1.0, of course there is going to be breaking changes with every development release, that is literally the purpose in this phase of development.
    1
  156.  @RenderingUser  Well, feel free to join the cause and help maintain X11 then. If you unable or unwilling to do so, then it seems odd to proclaim that others should do it at your behest. There are legitimate reasons that developers are moving towards Wayland and away from X11. There is no conspiracy against a project that has been pivotal to the Linux desktop, it is merely showing its age at this point, and becoming more and more difficult for anyone to maintain. If you have some silver-bullet solution beyond "I prefer X11 over Wayland", then I strongly encourage you to contribute, otherwise it all falls on dead ears. Sooner is better than later, as this problem has only been getting worse over the last decade. Coming in at the 11th hour is better than never at all, I look forward to seeing your solutions to these problems, and the continued success of X11.
    1
  157. Anyone who feels comforted by this article is just coping.
    1
  158.  @kreuner11  Anytime you see a irrelevant/nonsense comment, look at the profile pic, and If it is some scantily clad woman, then it is guaranteed to be a bot.
    1
  159.  @paulie-g  I lol'ed :D But totally agree: this is simply RMS being salty about the common nomenclature people adopted being "Linux" and not "GNU". I have yet to ever hear anyone not agree GNU was pivotal in the success of Linux. It is 100% just ego, not for any practical reason, or some conspiracy of users trying to snub him by not using the term "GNU/Linux". Should Linux also start adding the names of every piece of firmware into its name to ensure the hardware vendors get street-cred for its success?
    1
  160.  @Tynach  Because there is literally nothing complicated about any of this, and insinuating that it is so is classic deflection from an inconvenient truth that is self-evident. DEI discriminates based on race. This is the definition of what racism is, regardless of whatever recently-altered dictionary one chooses to cite. It is laughable. and absurdity of the highest order for someone who criticizes this to be the one accused of being racist. Insinuating that the issue is just too complex for small-minded people to comprehend to avoid facing the obvious flaws is a losing argument.
    1
  161.  @linuxguy1199  This. If anyone were able to come up with such an example, it would be amusing to also see how much of that code is relying upon "unsafe", which is technically "all of it" since the arbitrary lines we use to distinguish the layers of abstraction of voltage running through a chip are simply human conventions for understanding and taxonomy.
    1
  162. @ They aren't mutually exclusive, they just happen to be in this case, which I explained in detail across multiple paragraphs. I don't know how I can reduce this concept to simpler terms for you to understand. I never implied you said "pinhead", I have no clue why you would even claim that. You may want to re-read my previous replies.
    1
  163. ​ @renner0395  I still don't really understand, as you were referring to "clearly technical people", not "normal" people. Choosing not to take action can hardly be described as "going out of their way". These "normal" people aren't going to be downloading and installing drivers from GitHub to ensure their Windows 7 keeps working beyond its end-of-life cycle either. Let's not shift goal-posts here...
    1
  164. I understand the purpose behind immutable distros and can appreciate their use-cases, and perhaps it is my ignorance, but I simply don't see why I would ever want this for my daily-driver desktop for personal use. Is there any benefit to it whatsoever in that context?
    1
  165. My theory is that he is entitled and has an inflated idea of how important both he and his contribution to the kernel is.
    1
  166.  @turtleidiot3324  This is my experience, too. Running Wayland/Hyprland/NVIDIA and haven't had any problems. There was a few extra environment variables to set, a kernel parameter or two to apply, and switching to nvidia's DKMS package, but I have been completely stable since making the switch, and I even use it for my game development.
    1
  167. If you think Red Hat "owns" that code, you may want to review the terms of the GPL.
    1
  168.  @Daktyl198  Any and all code that gets contributed to the mainline kernel becomes part of that project, eternally and irrevocably licensed to the LF. I couldn't care less what their own fork is doing, those aren't contributions to the mainline kernel. It is literally and explicitly stated in plain English as part of the license, there are no "take backs", and they have no say on what happens with those contributions. They can be modified and distributed at-will by the LF according to the terms of the GPL.
    1
  169.  @Daktyl198  Ah , I see, that is fair. I misunderstood and incorrectly assumed you were talking about kernel contributions, as Red Hat is also the top commercial contributor also.
    1
  170. It is trivial to make any system do automatic updates, but this 100% needs to remain disabled by default. I personally think it is a horrific idea to have automatic updates, but I am not against offering the ability for people who want to use their Linux system the Microsoft way. As long as it doesn't hurt my experience, they are free to use theirs however they wish.
    1
  171. I wouldn't even want Linux "pre-installed" on my system. It only takes me a few minutes to do, and I want it done my way. This is literally the reason I want Linux on my machine. Ideally it would be nice to purchase an "out of the box" machine with no OS installed on it whatsoever so that my money isn't funding Microsoft.
    1
  172. I have been waiting so long for this, I really hope it ends up working well, specifically with downstream GE and Proton builds. Wine is literally the only application I have installed on my system that requires X11.
    1
  173. Light themes are awful, saying otherwise is pure cope. When I see someone using a light theme, I assume they are either not technically proficient enough to know how to change it, or they are psychopaths who likely have bodies in their basement. There are absolutely no exceptions.
    1
  174. I have been waiting so long for this, I really hope it ends up working well, specifically with downstream GE and Proton builds. Wine is literally the only application I have installed on my system that requires X11.
    1
  175. mpv is definitely the best choice for video, though I use mpd paired with ncmpcpp as a client for audio. It is another solid choice in the same spirit as cmus.
    1
  176. I just don't understand why they feel compelled to insinuate they are some "competitor" of FFmpeg. FFmpeg is (in)famously a complicated application, marketing yourself as a wrapper that makes development with it smoother is already enough for their target enterprise customer.
    1
  177.  @bobdouglass8010  Yeah, while it can feel clunky using a tiling WM for the first time, there is no going back once you get used to it. I have been using a tiler for ~4 years now, and recently was booted into Plasma, which used to be my preferred environment, and it feels just as clunky using it now as it did when I first switched to i3 years ago (though I am also using Hyprland now),
    1
  178. His delivery is obviously inflammatory, and it undermines his message by kicking the hornet's nest of something people are very tribal over, but most, if not all of, his points are actually very valid. I am currently using Hyprland, but plan on giving Cosmic a try in a few years when it matures and realizes its goals. Like many others, I found the alpha release to be very underwhelming, but am going to withhold any judgment until its first stable release. I predict that Cosmic is going to be the Cyberpunk 2077 of Linux desktops: fail to live up to the hype initially, but eventually blossom into something wonderful. My personal suspicion is that the public release of the alpha was a marketing decision, and not a developer one.
    1
  179.  @Thorned_Rose  I agree, though it is par for the course: raggin on Arch is trendy for some really bizarre reason that I never figured out. I assume it is based on the memes about Arch users being gatekeepers, and people who actually took it serious. it doesn't help that Brodie helps proliferate the idea that Arch doesn't do testing and refers to it as a beta-testing distro. It is scary how many non-Arch users, possible even the majority, that actually believe that Arch does no testing and it just pushes out updates the second the upstream comes out with a new stable release.
    1
  180. This was also during the era when Ubuntu was making huge strides in making Linux easily accessible, with simple GUI-installer, Unity desktop, live ISOs, etc, which are now pretty standard for every distro. I don't personally care for the modern Ubuntu, but they did make some advancements in making Linux more accessible to Windows and bringing the name "Linux" into the public consciousness. Prior to that, normies had never even heard of Linux.
    1
  181.  @edelzocker8169  Out here asking the real questions.
    1
  182. 15:25 Nonsense argument. This analogy is false and misleading on its face to even casual programmers who are even somewhat familiar with the topic. Replace "seat belts" with "roll-cage, 5 point harness, body armor, ballistic helmet rated for high-velocity rounds, and of course kneepads" and it might be getting somewhat closer to an honest cost/benefit analysis. Should we mandate helmets when driving cars? They would be safer, no? Dishonest and bad-faith arguments like this play a huge role in the negative reaction Rust often gets. This exact same tactic is used in politics, and no one likes politicians for a reason.
    1
  183.  @rjawiygvozd  I personally don't see the relevance of whether a delay is "random" or "curated", it is a distinction without a difference in the context of introducing instability with AUR packages. The wrong dependency version is still the wrong version, whether it is because some arbitrary time limit has not yet been reached, or because a skill group of fine artisans are honing their craft as software testers and cannot be rushed. Dismissing this as the fault of a user for using "crazy nonsense" packages based on your limited anecdotal experience doesn't make less stable for the countless times it has, and will to continue to happen. The irony I mentioned is that a practice intended to provide stability over Arch has resulted in it being more unstable than Arch. You allude to these "manual interventions" and how it saves its users from this common problem, and I would direct you attention to the Arch news site where they are listed. In all of 2024, there was a single manual intervention required, a basic chown command. How many AUR packages do you think broke exclusively for Manjaro users in the same amount of time? Tens? Hundreds? Thousands? If even only for a week or so, I am confident it was an aggravation, the point being that one does not have to concern themselves with using "crazy nonsense" packages, they are free to use mesa-git if they want without fear of their distro breaking it beyond its already inherent instability.
    1
  184. It is a great language to learn, but does have a higher difficulty than most other languages, I would liken it to when you learn C++ for the first time. It has gone the way of C++ and used the "kitchen sink" approach to its design-by-committee philosophy, It is very worthwhile to learn, but it is held down by the drama of its community, so I would recommend just staying clear of any "Rust groups". Just don't forget to tell literally everyone you meet or encounter on the internet that your application was written in Rust, and pretend that they care.
    1
  185. Rust is a cult of emotionally unstable people who throw temper tantrums online. You have probably seen them in other public sectors, they often have brightly colored hair dye, demand you use strange pronouns, and lie to you about their gender, and demand that you also lie about it or they will deplatform you.
    1
  186. That is a long time for a beta, by any standard. I say this as someone who has been a developer professionally for 20+ years. Your point is well-taken, but this isn't a good example of it. The issue with Cosmic is that the release of an open alpha was arguably a bad decision, and they should have waited for a beta version before unveiling en masse to the general public. I suspect this was a decision made by the PR department, not the dev team.
    1
  187.  @boredstudent9468  ...and obviously some part of it was freshly not setup correctly. There is no "default" install, you obviously selected options on how it should install, so not sure what relevance "fresh" is in this context. It didn't install itself in a vacuum without your input. If it is bricking, it is likely some issue with your partitioning and/or boot-loader setup, Could even be UEFI/BIOS or GPT/MBR mismatches, but you didn't mention what specific update is causing it to happen, so no way to say. You also claimed it was an update, but now indicating it is the installation process, and not an update. If you are using grub, try systemd-boot, it is more straightforward for a single OS system, and is less prone to mis-configuration with less moving parts. You can also just use the `archinstall` utility in the ISO, it will take care of avoiding many foot-guns.
    1
  188. I just noticed you said "archfi". Arch comes with an installer script, why are you using an unmaintained script that hasn't been updated in over 2 years?
    1
  189.  @boredstudent9468  The Arch iso has always been and still is the only supported way to install. You tried to use some unsupported (and apparently broken) method of doing it and ignored every warning to the contrary, and are now choosing to blame it on the distro itself 6 years later in YT comment. Luckily we did eventually get to the bottom of it.
    1
  190. We must secure the existence of our x86_64 PKGBUILDs and the future of the AUR.
    1
  191. I couldn't care less what people wish to use. I was one of those "don't see the point of the Wayland" people for years, but gave it another chance a while back, and ended up sticking with it, as it "fixed" an issue I was having with a particular game on X11. Having been with it for a while and now on Hyprland, I don't personally have any reason to switch back to X11. It isn't that I dislike X11 or anything, it did me good for many years, but Wayland is simply a better fit for me now. For my use-case, it has finally gotten to a place where it is stable and works well, but for those it doesn't, just use X11. I don't see the point of people taking such strong opinions in either camp, or trying to turn this into a flame-war. If I don't like a piece of software, I simply don't use it. I don't care how popular it is or "what everyone else is using". I am not an X11 or Wayland developer, I have no personal stake in either, and will never understand people getting in heated arguments over "which is better".
    1
  192. I experimented with the first alpha, but am going to wait until a stable release to do so again, well after the initial wave of hotfixes get patched, so probably around the 1.1 or 2.0 version. I can deal with most types of bug-ridden software when it is new and still ironing out the kinks, but a DE is not one of them, it gets frustrating too fast.
    1
  193.  @zizlog_sound  I was not very clear, I am saying that your point of thousands of distros as "not working together" has an incorrect premise. I personally don't see any use for all the distros either, but there is very little work going into one that can't be shared with all others. With the exception of package managers, nearly everything is universal and can be "shared". It may not be accurate to call it "working together", but it surely isn't "working against each other". A perfect example is Cosmic Desktop. It is being developed for PopOS, but the entire Linux ecosystem can use it and will benefit from it. This is the same with nearly all software. The differences between distros is remarkably small from a development point-of-view. No one develops "for Ubuntu" or "for Arch", they simply target Linux, and it works for all of them. Again, package management is the only notable exception to this. I very much agree that the huge number of distros isn't very useful, no argument here, but who am I to tell someone what hobby project they choose to develop?
    1
  194. I think you misunderstand what stable/beta releases are, Arch is no way shipping beta releases in its repos. It ships *stable* releases of software, after a testing phase briefer than most other distros. The releases are the stable versions from their respective developers. If JetBrains releases the new "PyCharm 8.0", it is a stable release, and Arch will get it in the repos sooner than Debian, but they are not pushing out "PyCharm 7.9.78-08-beta". If you want that, you have to install an "Early Access" package from the AUR. The developers of software are what define stable/beta, not Arch.
    1
  195. I wonder how long until they notice the happy merchant in the new logo....
    1
  196.  @bountyjedi  The problem is developers not respecting them when designing the software, not the spec itself. The spec is pretty clear on the environment variables, stating if they don't exist or are empty to use those defaults. (i.e. XDG_STATE_HOME should default to ~/.local/state if not defined). I assume it mostly oversight/ignorance that has led to it not be adopted, not belligerence to the spec itself. Having a known and well-defined place where files should be stored is a benefit to development, not a hindrance.
    1
  197. It would totally eliminate any context during communication with others from any area other than your own. If I said I ate breakfast at 2:00, how would you know if that was a "normal" time or not unless you I also had to include what "normal" time was in my area. This is one of the problems that timezones solved: no matter where you are in the world, time has common meaning that everyone understands without additional information.
    1
  198.  @iliqiliev  Sunrise varies depending on the time of year and geographical location. The last sunset in Utqiaġvik, Alaska was November 18. They won't see another sunrise until January 23.
    1
  199.  @iliqiliev  Because when I say "I ate breakfast at 7:00:, you know what it means without me having to explain the intricacies of how and when the sun rises/shines in my hometown.
    1
  200. DARPA doesn't fund anything whatsoever, the American taxpayer does.
    1
  201. Your overall point is well taken and generally true for the standard user, but it is possible, and live kernel patching is an actual thing. If you wanted to over-complicate your life, your could never restart and have the upgrades to your packages take effect, including the kernel, libc, systemd, etc, etc.
    1