When I get bored with the conversation/tired of arguing I will simply tersely agree with you and then stop responding. I’m too old for this stuff.

  • 5 Posts
  • 36 Comments
Joined 9 months ago
cake
Cake day: March 8th, 2024

help-circle

  • I appreciate the information, and I’m willing to give it a shot again when I next need to do a distro switch or a new installation, but until now my experiences with Wayland have basically been a stream of broken things over several days as I try to reestablish my workflow in a new desktop environment. The time it all goes successfully is the time I’ll be sold.


  • Like I said, I use Linux in my classroom, and I heavily use global shortcut keys set via script for individual lessons, with fullscreen opening of applications that don’t have automatic support and shortcut key based window switching all without mouse input to create a seamless presentation for my students.

    Global shortcuts and wmctrl, which form the critical backbones of this system, simply don’t work in Wayland.

    And to suggest it’s just a perfect transition is wrong. I don’t use Steam Link, but if I did? Doesn’t work in Wayland. Everyone constantly bemoans that applications should be rewritten for Wayland, but one of Linux’s advantages is eternal backwards compatibility so software can actually be FINISHED.

    Wayland isn’t the kernel and it shouldn’t be held to the standard of the Linux kernel, but do you remember when Linus Torvalds publicly screamed at and berated a developer for a change to the kernel that broke a userspace application and then having the sheer GALL to suggest the application developer was at fault? Wayland evangelists could stand to be a little more understanding that people don’t like it when you break functional userspace applications, force developers to work on stuff that is FINISHED to get it working again, and then blame them for not getting on board with your changes. You know who does that? Google.

    Look, Wayland works for you and that’s fantastic. Use whatever you like. Linux is Linux and one of the most beautiful points of Linux is freedom of choice. What I take exception to is the people in this thread who are acting like anybody who isn’t on Wayland is crazy and insisting there’s no good reason to still be on X11 just because they personally don’t understand why someone would need features they need. Anyone expounding that “Wayland is a 1 to 1 replacement for X11 and superior in every way!” is either being intentionally disingenous or a cultist. You know who insists users are wrong for having their own use cases and workflow and wants them to change to their preferred system because THEY don’t think the other use cases matter? Microsoft.

    I’ll be happy to make the switch to Wayland… when I do a system install or update and it happens invisibly and I don’t suddenly have to wonder why all of my custom scripts no longer work.


  • It’s not that I have issues - it works just fine in the domain it’s designed for. It’s that the Wayland system does not provide feature parity with X11. I make extensive use of window manipulation using xdotool and wmctrl for my daily use case, and those are both unsupported on Wayland. It’s a fine system for users whose use case fit with its design. It is not a feature complete replacement for X11.


  • I’ll never make the claim that X11 is perfect, but my use case requires features that are either not built into Wayland yet or simply won’t be built into it in the future.

    I’m sure it’s a fine product, but asking me to change my workflow to use it is a non-starter. When it reaches feature complete support of X11 functionality, I’ll consider changing.







  • You’ve said that, but this doesn’t seem to be a copyright issue. As far as I know, Ryujinx used NONE of Nintendo’s proprietary material whatsoever. Please correct me if I’m wrong.

    What I’m seeing isn’t an IP issue at all - it’s simple strong-arming.

    The initial argument that started all of this chain was a statement that Nintendo was understandable in their legal action, and I took and STILL take issue with that.

    “They are absolutely within their rights to approach the developers of Ryujinx and threaten to sue them.”

    While this is TECHNICALLY true in the most literal sense of the word, it carries the implication that there is something justifiable at some level about the actions they’ve taken.

    My response is it’s correct in only the most pedantic sense, THIS is the element I find egregious for how much it understates just how disgusting Nintendo’s actions are. This is nothing more than a mafia shakedown with lawyers instead of grunts, and to play it down like that is improper.

    IP, copyright, shutting down streamers… all of this is a totally separate issue, and all of THAT activity is actually SUPPORTED by law.

    Shutting down Ryujinx is on a massively different level. It’s neither a copyright issue OR a legality issue. It’s a direct strong-arming contrary to established law, and THAT is what this thread is about. There are other articles to discuss IP and content creators, which are a completely different issue with different repercussions.


  • And Elon Musk was “legally in the clear” to sue a trade group into non-existence over the idea that companies deciding to boycott his site independently was collusion.

    I am objecting loudly and powerfully to “legally in the clear” being equated with “acceptable” or “within the spirit of the law.”

    Make no mistake. As far as we know, this is only legally in the clear because the developers are unable to fight it. That does NOT make Nintendo’s action correct. By LAW the developers are in the right, they simply cannot afford to defend themselves. If your claim is that it is technically legal to threaten to sue anybody you want, you are correct and also terrifyingly shortsighted. Inability of someone to defend their rights for financial reasons is a miscarriage of justice. Given the options of smugly pointing out the technical situation or ranting about the injustice, I’ll take the latter.

    Let’s put it another way… You’re absolutely right. Nintendo is LEGALLY in the right to bully someone into submission using the threat of a lawsuit they cannot afford with overwhelming money. The legal system can’t touch them.

    But that means the ONLY place where Nintendo will EVER face ANY kind of consequences is in the court of public opinion, so why on EARTH would your take on the situation be, “Oh well… nothing we can do.” It’s not much, but it’s the ONLY lever you have, and to relinquish it is fatalistic, shortsighted, and overall inconceivable as a strategy.



  • Perhaps. But I see a lot of hand rubbing and “oh welling” from people when this is a legitimate moment for anger at the precedence this sets. I understand the urge to make it make sense, but the fact is people either tacitly accepting this activity as reasonable or arguing about the red herring of whether the source code is still available to sit and rot with nobody touching it but shady scam artists, not only moves the bar on what what Nintendo and other companies see they can get away with, it has a chilling effect on future preservation efforts among the constantly shrinking pool of people skilled enough in low level development to do this kind of work.

    I guess my point is, I’m seeing very few voices that are sufficiently concerned or angry enough about this event considering the far reaching consequences it’s going to have.

    We shouldn’t in ANY way be normalizing this activity, and our reaction shouldn’t be “Of COURSE they did this.” Although I guess I shouldn’t be surprised after we just watched Boeing murder a half dozen of its whistleblowers and the most people did was make a few memes. We’re living in a literal dystopia, apparently.


  • You’re incorrect. Creating an emulator is not illegal. Nintendo has the legal right to threaten to sue someone, but if you are threatening to sue for something that is not a crime, and you know that, and you do it anyway in the hopes of bankrupting them before the case settles, that’s not a legal proceeding, it’s extortion. I can threaten to sue you for cooking pancakes in your house, and while it’s technically ALLOWED for me to do that, it’s clearly and obviously not a case I would win, but if the threat of making your life hell is prominent enough, you might get forced into backing down, which is exactly what’s happening here.

    They would absolutely NOT lose in court for creating an emulator. I cannot stress enough exactly how legal emulation is. It’s as legal as making your pancakes. The only way they would lose in court is if there is some EXTRA thing they’ve done that we don’t know about. If all they’ve done is create and distribute Ryujinx, there is absolutely NO way Nintendo would win a case in the US. This is settled law, and saying it isn’t doesn’t make it so, although it DOES embolden companies to bullshit developers with more bogus threats in the future.


  • They aren’t working within any rights. Emulator production is a legal right that Nintendo has neither the ability to bestow nor deny. It’s the founding legal rationale behind virtualization as a technology. This is the equivalent of someone holding a gun to your head and telling you to shut up - the forced relinquishing of your rights through threat of force, and it’s a little frightening to watch people suggest otherwise. This has played out in court and is settled law. Bleem! went BANKRUPT to secure a legal victory against SONY and establish that emulators are completely legal and there is no “gray area” about them, and you should be in less of a hurry to throw legal rights away because “Well, Nintendo said so…”


  • No, the OSI model is fine.

    I’m talking more about sandboxing an interpreted app that runs a container that runs another sandboxed interpreted app, both running their own instances of their interpreter with their own dependencies and accessible through a web interface that is accessible through yet another container running a web server that is running in Python with a virtual environment despite being the only Python app on the container, which is then connected to from another sandboxed tab on a sandboxed browser on your machine.

    But hey, at least it isn’t, god forbid, a MONOLITH. That would require someone to take the time to understand how the application works.


  • Their UX and UI are their bread and butter, but as someone who has done extensive web app development for use on Safari browsers, if I had a nickel for every time their browser just IGNORED a standard, broke one that previously worked, or added new “features” that broke a standard, passing the responsibility of building a workaround down to individual developers… I’d have a few dollars anyway. I don’t have much faith their code is all that good compared to average under the hood and the UI, and I think their reputation unjustly leads users to turn a blind eye or give them a pass when their stuff DOESN’T work or works BADLY. “They’re Apple… everyone else seems happy. I must be doing something wrong.”