IANAL, but they should be fine since they aren't decrypting / breaking DRM they same way Yuzu was. They are a much cleaner codebase, much more similar to mGBA and Dolphin.
meteokr
joined 1 year ago
There's also Bitmagnet, it you'd like a local tracker for the Arr stack.
Bash being on the same level as actually fake code is a pretty hot take to me. What are your opinions on Python, or Ruby, or any other interpreted language? You could very well use them as your login shell, just like Bash if you wanted. In your eyes, if Bash *isn't * a programming language at all, how do you describe a programming language? Languages that express code are just the same as languages that write stories, and whether you do it in German or Vietnamese makes no difference on what story you can write.
When you describe a language as constricted what do you mean? Bash can do anything Python or Rust can do, each of them is just specialized to being better at specific aspects for human convenience in writing code. There is no inherit limitation on what can be done by the language you use to express it.
Pseudo code is literally fake code. Scripting is an actual type of code. Scripted languages while not strictly defined, usually refers to languages you don't compile before running them. Bash is considered a scripting language because you don't ship a binary compiled executable, but rather ship a file that is human readable and converted into machine code when it is run. Scripting languages are compared to compiled languages, like C or Rust. Where the file you run is already compiled, and executed directly.
What do you mean by this?
i’m referring to the aspect of a scripting language being generally constricted.
Any Turing complete system, or this case language, can do anything any other one can, depending on the level of suffering you are willing to endure to make it happen. Anything JS can do, Rust can do. Anything Rust can do, Bash can do. The differences between languages is the assumptions they make, and performance characteristics as a result of those assumptions. Functionality is not practically different from one another, though some absolutely make it easier for humans to do.
The best solution to that situation is just a more vigorous application of XGH.
You missed the point of my example entirely. How can those commits exist, and those people exist in that instance if they don't have accounts? I was refuting your statement that a frontend needs an account. By mirroring an existing repo, as an example, you could verify that my claim is correct. Git as platform is already decentralized and doesn't require accounts. You could email someone your git diff's and it will function the same.
You need a frontend
Yes, but the requirement of said frontend are very small.
and a frontend needs an account.
Not required at all actually. For example, mirror a github repo in gitea. You'll see all the commits, their messages, and who made them. Yet that gitea instance isn't accessible publicly. None of those people have an account, and none of them can login even if they could access the instance. A commit is just attached to a name, that is user configurable, and a lot less data minable than a "real" account.
Vegans for OpenTofu brought a smile to my face immediately, I shall hopefully remember to use this when it comes up.
Whitespace is not visible. It is the absence of something that is visible. Whitespace should be used for the comfort of the reader, not to determine scope. Are you proposing that a " " character is more visible than "{}"? The fact I must quote it to make what I am discussing even apparent speaks for itself. I'm not arguing that indentation is bad, far from it. In fact, the flexibility of using indentation purely for readability, makes code more readable.
If you run it in podman, podman can export into a kubernete file, but its been a long time since I've tried it though. podman kube generate $CONTAINERNAME
is podman-compose really dead? Their github page looks active at a glance. The tooling is so similar, I use podman for local testing, and deploy to docker, but I've also done the reverse. As long as your not using really exotic parameters its really just a drop in replacement, I've even used GPU passthrough for AI project no problem in both docker and podman. At the end of the day, they're just slightly different frontends for the same backend.
As far as docker support, its often as simple as just providing a Dockerfile, which is basically the same thing as your build scripts. These days I've often used the Dockerfile INSTEAD of the readme to find help compiling some projects.
I don't believe Yuzu went to court, but that was the accusation Nintendo was suing them over. Ryujinx wasn't sued, so Nintendo either didn't believe they had done the same, or didn't care. We didn't get to have a discovery process for the case to find out for sure, so we don't know.