serenity VS counter-strike

SerenityOS replicates that look and feel. It is also implemented in a dialect of C++ that adheres to some of the good parts of C++98: https://serenityos.org

One example of a useful technique

https://serenityos.org/ apparently only makes source code available. There are no binary images of the OS to install

I think Andreas said this functions like a little test -- if you're not willing to build it from source, then you probably wouldn't be a good contributor anyway.

---

Likewise, my shell project provides source tarballs only, right now - https://www.oilshell.org/release/0.21.0/

It is packaged in a number of places, which I appreciate. That means some other people are willing to do some work.

And they provide good feedback.

I would like it to be more widely available, but yeah I definitely see that you need to "gate" peanut gallery feedback a bit, because it takes up a lot of time.

Of course, it's a tricky balance, because you also want feedback from casual users, to make the project better.

Indeed, given the existence of `JS::NonnullGCPtr`, `JS::GcPtr` intentionally corresponds to a nullable pointer, so it seems dangerous to convert one to a reference without a null-check.

That said, a naive code search finds what *may* be more cases of this pattern:

https://github.com/search?q=repo%3ASerenityOS%2Fserenity+%2F...

Eg: https://github.com/SerenityOS/serenity/blob/a68b134e6dea5065... -> https://github.com/SerenityOS/serenity/blob/a68b134e6dea5065...

In some of those search results, it is fine because there is a preceding null-check, and obviously I know nothing about this code other than this naive search result, but perhaps it would be prudent to vet all of them.

It is a SerenityOS project. You can find the answer to that question in their primary project's FAQ[1].

1. https://github.com/SerenityOS/serenity/blob/master/Documenta...

https://github.com/SerenityOS/serenity

The best way to write proper exception free C++ is not to use the C++ Standard Library.

I initially confused it with Serenity OS prior to watching the video: https://github.com/SerenityOS/serenity

My contributions to SerenityOS[0] helped me get my current job. My team lead (who was also my interviewer) was interested in what I did since I listed some of it in my CV, and I showed him some PRs I made and explained what went into each of them. It was really exciting because I didn't have professional experience with low-level development, and basically got the job due to hobby programming.

[0]: https://github.com/SerenityOS/serenity/pulls?q=is%3Apr+autho...

Definitely not "literally impossible", just a great deal of work. https://github.com/SerenityOS/serenity/tree/master/Ladybird

In the last few days Valves own "Regional Standings" ranking system for the CSGO Pro scene has been talked about again, when Valve announced that future tournaments need to adhere to it for their team invitations. You can find the explanations and current (27th July) rankings here.

Invitations to all tournaments will use our ranking system (detailed here), or otherwise be determined by open qualifiers.

Valve's rulebook only mentions this control room for matches though, not for updating the pickems for the next stage.

isn't it based on the head to head rankings that they compile based on all of the matches between the teams? from https://github.com/ValveSoftware/csgo/tree/main/regional_standings

Major Rulebook from Valve: https://github.com/ValveSoftware/csgo/blob/main/major-supplemental-rulebook.md

Valve already have a published spec, it essentially says to block everything except for Valve's public IPs.

We've also seen strings relating to servers toggling sub-tick architecture, which may mean TOs and FACEIT/ESEA could continue operating at 128-tick with or without sub-tick if that is dictated by Valve in their Major Supplemental Rulebook when updated for the 2024 Major. Hopefully Valve updates the CS:GO Dedicated Server Wiki Page or links new info on the CS2 Wiki Page.