@Oktokolo It runs quite well on Cemu. Played through it on the Switch first and sometime after that on Cemu. Although you'll need potent hardware.

I... don't get it. Used the huddles a couple of times now, what's better about them?

Yeah, you have no window for the call. The call also doesn't appear in your history anymore. Which I dislike, as it was always useful information.

Other then that I don't see much difference.

https://lmddgtfy.net//...

That reminds of some young colleague that always uses the term "reverse engineering", whenever they just mean to read some decompiled code, to figure out how some undocumented feature works.

No. You're not "reversing" anything. You're just reading good damn source code.

@rutee07 He wasn't online anymore. I'm going to tell him tomorrow asap.

It's maybe better that way. I'm quite angry currently. I can argue my point better, when i'm calm and collected.

Fulfilling nr.3 will most certainly prevent you from achieving any other goal, that requires free time. ;)

Oh, the real horror is right here: https://github.com/felixrieseberg/...

@netikras True. But it's also the current LTS version.

That looks fun to build. :)
I would like to see the finished build.

Maybe the staff did it accidentally, while cleaning the place?

On the other side it is quite the endorphin rush when the you get your first working sample like e. g. the boot rom.

@SortOfTested Agreed. Had a junior cry big crocodile tears, as she had to actually read documentation for once. She was completely lost without the IDE autocompleting everything.

Try to implement an emulator.

Ohhh want as well. :o

@VaderNT How do you know who has which information, if there is no regular exchange of information in the team?

Where do you discuss important topics that concerns everyone?

Try to write an emulator.

Change the shebang to #!/usr/bin/env bash, if it happens to be the issue. This will make the script more portable.

@gitpush Yes, it's still useful. Personally I wouldn't read it from cover to cover. Maybe give yourself an overview of the more uncommon patterns and solidify your knowledge about the commonly used ones like command, strategy, flyweight and so on.

Afterwards it's mostly great as a reference.

That is the book written by the GoF and has become kind of a bible for OO at that point.

It's definitely worth a read, especially if you work with OO codebases. You will however find that it is not an entertaining read. It's overall more useful as a reference.

That filter is more dangerous then the creator anticipates. While written with somewhat good intent, it can easily be used to stop any discussion Twitter deems wrong or against their own believes.

I'm aware that Twitter is a private organization and can do whatever they want on their own platform. But at this point discussions there have so much influence, that this principle needs to be revisited.

Lastly, I don't think banning words will do anything to help his cause. People will simply post their banned language on another platform. Potentially grouping regular people together with more radical ones.

@SortOfTested I was going to argue with you, that Maven isn't so bad. But then I remember the pain that is multi module projects with inheritance. Also pom imports.

Thank you for the answers!

I talked things through with them the next day. They apologized and told me, that their actions were not meant to be maliciously. They acted before thinking.

Seriously? I'm not buying it. They are pretty young and inexperienced, but they aren't not that naive.

I will be cautious from now on.

Github should have never removed master, as it was just for virtue signaling.

What exactly is your problem with blame? Yes, it's negative, so what? Often this function is used to find out who wrote problematic code. And yes, they will get blamed for that.

The world isn't focused around your needs and shouldn't be. Work life can be hard at times. People should start adapt to their life and not the other way around.

This whole controversy is completely out of control. You see everywhere blind actionism like changing terms like black- and whitelist since they are now apparently racist.

I have never seen anyone use those words in a racist context. They steems from darkness being something shady, untrustworthy or simply bad. Therefore we have words like black market. But those don't stem from a race context.

Besides that, you're NOT fighting racism by banning words and symbols. Racism is an ideology. By banning words, you're just changing tokens. They will find new words and symbols to express their views.

The current actionism is hurting the cause more then anything, as even regular folks will at this point view those actions as meaningless. They will slowly get the feeling that they are just getting knocked around.

I dread where all of this will end.

This refers to the fact that you should not mistake e. g. RAID 1 for a backup solution. It will mirror your data to minimize data loss by hard drive failure, but will not mitigate others threats like ransomware or user error.

Having a dedicated RAID 1 for backups however should be fine. Just don't rely on the mirroring alone.

@melezorus34 There are no global classes in Java. You can only change the visibility of them.

So don't "lmgtfy" me, thank you very much. :)

@melezorus34 What is a "global class"?

@hjk101 No, my issue is not with reusing 500. Far from it. My issue lies with returning 200 while the called application e. g. raises an exception. In this situation the server should return 500, as this clearly indicates an server side error.

Instead in my particular example, it _always_ returned 200, while relaying on some custom error reporting technique that offers no benefit.

tl; dr;
The response code should reflect the outcome of the request.

@hjk101 No, it isn't fine. 500 is literally the code for "Something has gone wrong on the server side". This includes the applications running on it. There are other codes, if the request itself is malformed.

Giving back 200, if any server side error happens, is just wrong. Especially when you return the correct error code embedded in some JSON.

Reminds me of:
Code: 200
Body:
{ responseCode : "500", message: "Fatal error!"}

And I wish I made that one up entirely.