It’s a shorthand for writing this:
variable = if (input != null) input else default
This is equivalent:
variable = input ?: default
It’s a shorthand for writing this:
variable = if (input != null) input else default
This is equivalent:
variable = input ?: default
It’s a shorthand for writing this:
variable = if (input != null) input else default
This is equivalent:
variable = input ?: default
The answers confusing it with the ternary operator are wrong.
Because it’s not one. Ternary operator is A ? B : C, Elvis operator is A ?: B. The same two characters are involved, but both the syntax and effect is different.
Since it’s end to end encrypted, Ente just sees some raw bytes, it has no way to tell if what you uploaded is an image or not. So in practice it supports whatever the client can display, so your browser for the web version.
Probably. Extrinsic vs intrinsic motivation.
I spend hours toiling at work, then I finish work and switch to my hobby project, on the same desk/peripherals (KVM switch), same IDE and same tech stack, and work on it full of energy and finding it fun.
I have no clue why this works for me.
Yeah, sounds about right. This isn’t a case of “Google maliciously takes down a Google Maps competitor” like people are saying.
Strategy? You are assuming there was any intent behind it. The reviewers in third world countries are probably spending 30 seconds per app and are bound to make mistakes. Which in this case was reverted.
No, it’s not. It’s part of React internals that you shouldn’t use because your app will break. It’s a warning for developers using React. It’s not a secret of any kind.
I would never use anything else for Java or Kotlin. Through the free and open source JetBrains IDE of course.
Two actually. The one from the before the suit change is also left there, and Catherine said he will wake up in a day or two. Maybe they can meet up actually.
What do you mean he wasn’t so lucky, after all he lived out his live in Toronto. That he did a brain scan at some point of his life doesn’t matter. Sucks for the robot who thought he was him.
I was just annoyed at the protagonist for expecting anything else. The exact same thing already happened 2 times to the protagonist (initial copy at beginning of the game, then move to the other suit). Plus it’s reinforced in the found notes for good measure. So by the ending, the player knows exactly what’s going to happen and so should the protagonist, but somehow he’s surprised.
Only if you copy and paste to the same disk. When copy pasting to a different disk, as any consciousness transfer would entail, it is very much actually copied and actually removed (from the index).
Because when projects do it everyone runs away, forks are made, and everyone hates the developers because it’s “not open source anymore”.
Yes I’m conflating them to illustrate my point. You are right in that it will increase the amount of people wanting to try it. My point is that these people won’t be able to get it running, if, for example, it involves Arch repos which are far beyond the reach of the average person. So the additional awareness might go nowhere.
You say Suyu will have stuff soon, and that there are alternatives. Yes that’s correct, which to me means “emulation is not dead yet, there are still alternatives”, which doesn’t seem like “the opposite effect” at all.
Well, for one thing, I never said it was a positive. I didn’t use that word, nor did I even imply it.
You are saying it’s going to have the opposite effect of what Nintendo wants (curtailing emulation), so your claim is that this is going to make emulation more widespread. Correct me if I misunderstood.
Look at LibreOffice.
I never disagreed that a fork can end up good. I said Yuzu shutting down won’t help emulation.
This statement literally proves my point. The binaries still exist in some repos, like the Arch extras repo.
Your claim was that this is “increased awareness to the average person”. How are you mixing “average person” and “Arch extras repo”? The average person uses Windows, Googles “yuzu” and doesn’t find anything clear. This was my point, it brought awareness to me and I saw myself that Yuzu is no longer accessible to the average person.
Please explain how Nintendo is worse off now if that’s really what you think. All your arguments boil down to “this means nothing in the long term, emulation is going to be fine”, which I agree with. I still don’t see how this is having “the opposite effect” though.
Yes the project can continue. The original developers, who were obviously best suited to continue it, are gone. I’m sure suyu can do a good job, but I just don’t see how you can call it a positive.
I don’t know who the suyu contributors are, but so far all the activity was renames and migrations to GitLab, not a single technical commit. Are any of them actually able to work on a Switch emulator? Maybe they are, I genuinely don’t know, but the activity on the project so far doesn’t indicate that.
You say the binaries and tutorials still exist. I wasn’t interested in Switch emulation before this, but wanted to try out of curiosity when this happened. I’m a developer myself, and it was difficult finding information. All the download sites and tutorials are dead, and sketchy alternate downloads cannot be trusted. How is the average person, as you say, supposed to download Yuzu now? I eventually got it running but it was far from easy and I had to view tutorials through archive.org. Again, not impossible, but far from the “opposite effect”. Access to Switch emulation for the average person was lowered.
That’s what everyone tells themselves because “haha Nintendo stupid”.
No it’s not going to have the opposite effect. Best case scenario a different team will take over the project and continue, which is not impossible, but far from a given. More awareness to an abandoned project? Yes, but the entire point is that Yuzu developers won’t add Switch 2 support, and that was assured.
It’s in Kotlin and some other languages. C# has it but there it’s actually
A ?? B
.