I’d interpret that as a local social network app, not map/navigation.

But if both sides are your enemies, they’re both your friends. But if they’re your friends, they aren’t the enemies of your enemies anymore, which would make them your enemies once again. But then they are your friends again. But then

Though naming it by the following year instead of the release year is clearly a marketing move.

Oh, you should have mentioned that - or do you think that fsck is Memtest? It is not.

Hm, unfortunately nothing obvious. And your last boot ended with a crash?

Nevertheless you could try running a Memtest (this can take a while) - it will check whether any of your RAM modules are faulty: https://www.memtest.org/

That’s unfortunately a bit cut off. Could you run this again with the following command? sudo journalctl -xeb -1 --no-pager

Sure, though the immutable design makes it very safe to touch these things.

OP, do this - it’s the best way to figure out what’s happening. It could be any number of issues, e.g. faulty RAM. With the output of the command above people can tell you what to test for.

That’s your prerogative, but it honestly doesn’t make sense. Typescript adds almost no functionality to JS (and the few pieces it adds are now considered mistakes that shouldn’t be used anymore). It only focuses on adding typing information, and in the future you’ll be able to run TS that doesn’t use those few added features as JS (see the proposal).

You can also add the TS types as comments in your JS code, which IMO shows that it’s not a different language.

Not really, considering Typescript only adds static types to JS. It’s not a different language, it’s an extension.

I wouldn’t use raw JS for anything new, yes. Typescript however is an excellent language.

Sure, but at this point it’s your own fault if you don’t use Typescript to keep these issues from happening.

There is operator overloading happening - the + operator has a different meaning depending on the types involved. Your issue however seems to be with the type coercion, not the operator overloading.

It should not happen no matter why it does happen under the hood.

If you don’t want it to happen either use a different language, or ensure you don’t run into this case (e.g. by using Typescript). It’s an unfortunate fact that this does happen, and it will never be removed due to backwards compatibility.

Sure, but then your issue is with type coercion, not operator overloading.

It should just randomly pick any “1”. Add a bit of spice, you know

That’s the case in many languages, pretty much in all that don’t have a separate string concatenation operator.

Sorry, but that’s absolutely wrong - the complexity of articles can vary wildly. Many are easily understandable, while many others are not understandable without a lot of prerequisite knowledge in the domain (e.g. mathematics stuff).

If the reader is interested in the content, they aren’t going to skip it.

But they aren’t interested in the content because of the complexity. You may wish that humans work like you describe, but we literally see that they don’t.

What you can do is provide a simplified summary to make people interested, so they’re willing to engage with the more complex language to get deeper knowledge around the topic.

For example, look at all the iPad kids who can’t use a computer for shit. Kids who grew up with computers HAD to learn the more complex interface of computers to be able to do the cool things they wanted to do on the computer.

You’re underestimating how many people before the iPad generation also can’t use computers because they never developed an interest to engage with the complexity.

[…] then how are those readers going to improve their poor reading skills?

By becoming interested in improving their poor reading skills. You won’t make people become interested in that by having everything available only in complex language, it’s just going to make them skip over your content. Otherwise there shouldn’t be people with poor reading skills, since complex language is already everywhere in life.

I don’t know, plastic feels fairly unnatural