Choosing names like `App`, `ok` or `get` in a language without namespaces is a bold choice.

JSON 5 is pretty good. It just needs to make the top-level brace and all commas optional, and add proper support for multi-line strings (writing '/n/' at the end of every line doesn't count).

Allowing only valid JavaScript identifiers to be unescaped keys is also a bit quirky (You have to quote reserved keywords).

But they will never change any of that because it would break JavaScript compatibility.

I think the problems with big network were diminishing gradients, which is why we now use the ReLU activation function, and training stability, which were solved with residual connections.

Overfitting is the problem of having too little training data for your network size.

There's a German Wikipedia page: https://de.m.wikipedia.org/wiki/Coinhive

It does work on mobile,but the instructions are cut off.

And it doesn't play like normal solitaire. You can move any card, no matter what's on top of it. That makes it much easier.

I find json5 much better than json, but it has still many of the same annoyances.

- instead of trailing commas, how about making them completely optional? It's not like they are needed in the first place.

- curly braces for top-level objects could be optional too.

- For a data exchange format, there should really be a standard size for numbers, like i32 for integers and f64 for floats.

- parsing an object with duplicate keys is still undefined behavior.

At the very least, division by zero should not be undefined for floats.

Shouldn't it be `round(x/5)*5` ?

Depends, are you working in cents or whole euros/dollars?

In all use-cases I encountered, working with integer cents is much cleaner than decimals

JSON??

I don't want to programm anything without comments.

I guess you can easily convert from use yaml or json5, but all the examples are still in json.

Or if you write it by hand at all, use RCL, then you can also abstract away the repetitive parts: https://github.com/ruuda/rcl/blob/master/examples/vega.rcl

JSONC seems solved your issue

I think JSON is just used as an intermediate representation which is normally generated by a library in a more general purpose language.

AFAIK a steam ban in this case just means that you can't buy stuff or activate keys anymore. You should still be able to play previously purchased games.

So from then on you will need to have TWO accounts? Or what are you supposed to do, considering most games are played using Steam?

You’re supposed to not get banned I think.

Getting banned by an impenetrable, omniscient entity is exactly the dystopian Panopticon future (well, present) people want to avoid.

Follow the rules then. Their appeals process is fast and human.

Oh man, how did I not realize that tyranny is actually great to live under if you just follow the rules, thanks!