Fair. I’d be fired if I were a vexillologist.
Ofc. I thought it’d be fun.
Huh, TIL. Ok. I told the fn model to not include a rainbow. My prompt-fu needs work fr.
I figured I’d try to generate one. This is about what I think it would look like.
I totally regret buying it. Didn’t realize it was multiplayer.
I’m sad that they had to monetize sky the way they did to keep the service up. It’s clearly what they wanted out of journey but couldn’t accomplish the first go. If you like journey, play sky, children of the light
Users paid, and no longer play.
Seems kinda theftish.
IANAL.
Perhaps a class action lawsuit could set that precedent.
Maybe they should have just done a dollar a month subscription that goes along with the game or give that as an option now to keep the server alive.
Even if it’s a couple bucks sure the most faithful adherence of the game would not really mind paying it. The biggest problem for me here is that they’re totally removing the consumer’s agency, their choice.
I agree with what someone else said in this thread that if the support goes away then the server’s code should go open source. By law.
I can’t recommend it enough. it’s a fantastic game . The story is haunting and it’s legitimately difficult to get the good ending.
Super Mario RPG can be wolluped in 20. If you go hard, I bet you can do it in 10.
Pretty fun and rather full of Easter eggs if you want to keep at it.
I understood the answer, not the meme. I guess I wasn’t clear. Sorry internet friend. Clearly GPT was lacking some nuance too, as evidenced by some discussion ITT.
Did I say that? It’s obvious that it’s a fairly nuanced as topics go, and GPT is not great at nuance. It doesn’t seem like it’s totally wrong though.
Anyhow I don’t rust, so it’s kinda irrelevant, just an interesting topic.
GPT is fairly useful but I definitely don’t trust it implicitly. Lol
A Rust procedural macro (proc macro) is a metaprogramming feature in Rust that allows you to define custom syntax extensions and code transformations. They operate on the abstract syntax tree (AST) of Rust code during compilation and can generate or modify code based on annotations or custom syntax.
Sandboxing a Rust proc macro refers to restricting the capabilities of the macro to improve security and prevent potentially harmful code execution. There are several reasons why someone might want to sandbox a proc macro:
Security: Untrusted code can be executed during the macro expansion process. To prevent malicious code execution or code that could access sensitive information, sandboxing techniques are employed.
Preventing unintended side effects: Some proc macros might inadvertently introduce side effects like file I/O or network requests. Sandboxing can limit these actions to ensure the macro only performs intended transformations.
Resource control: To manage system resources, a sandboxed proc macro can be configured to run within resource limits, preventing excessive memory or CPU usage.
Isolation: Sandboxing helps keep the macro’s execution isolated from the rest of the compilation process, reducing the risk of interfering with other parts of the code.
Sandboxing a Rust proc macro typically involves using crates like sandbox
or cap-std
to restrict the macro’s capabilities and limit its access to the system. This ensures that the macro operates within a controlled environment, enhancing the overall safety of code compilation and execution.
-GPT
I didn’t get it either.
Seems to me if your code will be this unpredictable, you should only run it on an air gapped machine
I’m happy to see that the first 2 lemmy instances I’ve joined are run by nice people. Sometimes it feels like there’s a shortage of nice, but not today.
Normally, I’d say it’s poor taste to speak ill of the dead. Normally.
That’s not what the motivation is here. The media are
mastersshareholders