Drop the AI written story, take me straight to the "Explore Your Record" view. That's more interesting.

Fair. Just added a "skip to timeline →" button visible from the first second of the loading screen. Story is the hook for some users (see Imustaskforhelp's comment below) but shouldn't be forced. You can bypass immediately now.

If they managed to make 3 full movies out of The Hobbit, they'll surely be able to make a movie or 2 out of 6 chapters of LotR.

I'm sure plenty Americans are also laughing at this. No hypocrisy here.

There's a bunch of steps before prison that do not work.

Yeah, the steps to make the law apply to billionaires too. Systematically and all the time, before they rape teenagers. Like, punish then when they are defrauding first time.

There's even more steps to reworking the system that have been designed not to work...

And it's all a meta commentary on 915.

All they left was the stopwords.

Regarding runtime overhead, I'd assume you would still need an io implementation, it is just showing it to you explicitly instead of it being hidden behind the std lib.

For simple projects where you don't want to pass it around in function parameters, you can create a global object with one implementation and use it from everywhere.

You still have to pass arguments to library functions that need to allocate or do I/O ... but the alternative is worse. This is really a bogus issue ... no one is crying over having to pass a `this` pointer to every single call of a method in other languages. Context pointers are a requirement in any sizeable or multi-threaded program, and Zig gives the user full control over what the context object looks like.

Yeah thing is it's usually better to have allocator in particular defined as a parameter so that you can use the testing allocator in your tests to detect memory leaks, double frees, etc. And then you use more optimal allocators for release mode.

React Native is Javascript on top of the native toolkit of the platform. No HTML or CSS here.

What's the problem with the mascot? PostgreSQL has an elephant and MySQL a dolphin. Is the bug too detailed for database software?

Why would we want a literal BUG as a mascot?? /s

I wonder, does the important_value function get called and the value discarded or never called at all? Looks like a footgun if it has side-effects.

Not calling the function would be evidence of further derangement in the design.

Such a thing has been perpetrated in C. In C, you can repeat designated initializers. like

  foo f = { .a = x(), .a = y() }

The order in which the expressions are called is unspecified, just like function arguments (though the order of initialization /is/ specified; it follows initialization order).

The implementaton is allowed to realize that since .a is being initialized again by y(), the earlier initialization is discarded. And it is permitted not to emit a call to x().

That's just like permitting x() not to be called in x() * 0 because we know the answer is zero.

Only certain operators in C short-circuit. And they do so with a strict left-to-right evaluation discipline: like 0 && b will not evaluate b, but b && 0 will evaluate b.

The initializer expressions are not sequenced, yet they can be short-circuited-out in left-to-right order.

Consistency? What's that ...