The worst thing is: you can’t even put an int in a json file. Only doubles. For most people that is fine, since a double can function as a 32 bit int. But not when you are using 64 bit identifiers or timestamps.

It is only logical that an algorithm trained on the ways of a Vulcan, is precise and accurate in it operation and communication. Vastly more fascinating are the result when you ask it to behave like a human.

The problem with C++ is not the lack of safety features. It’s the ever lasting backwards compatibility that is keeping it both alive and down at the same time.

Having to support 50 year old code, is going to limit any restriction you place. But it is usually the restrictions that make a language good.

Example: You can write perfectly good modern C++ code without any pointers. But pointers are so ingrained into the language, that it is impossible to remove them.

Google is not a mobile phone network provider. SMS routing is not really their cup of tea. It is an industry with lots of established players, lota of local issues, and little to gain for Google. If it where up to Google, everyone would be using their app instead of SMS.

I don’t understand why someone would want to rent their car. Maintenance is not that hard, and companies always make you pay way more for their subscription models. By owning the car, you can pick who does maintenance. Meaning there can be competition, so prices/quality remains good.

For some, this subscription model is great. But do you agree, that is it a bad thing if they force it on us?

Should a dedicated search not use/index ActivityPub instead of the html interface?

If so, instances can simply defederate from search engine instances. So the point you are trying to make still holds.

1. Threads federates
2. Threads hosts 99% of all content and all users.
3. Threads releases and update that allows a new feature. Example: they add buyable threads gold, that you can reward to a post or comment.
4. The rest of the fediverse can’t implement this feature, and is inherently left behind in terms of features.
5. Threads releases an update that breaks federation. 99% of the users do not notice.
6. It takes Threads 3 months to fix the issue.
7. Go back to step 5.

Every non-Threads participant will have less features, and is constantly struggling to keep up with the changes and bugs of Threads. Result: the fediverse cannot grow. Only the most stubborn anti-Meta users will accept the objectively worse experience, just to avoid using Threads. But the average user will just use Threads, instead of joining Mastodon, Kbin, Lemmy, or any of the many other fediverse instances that Threads can federate with.

Disabling the tpm requirement is just a registry hack in win 10, or a selectable option when creating an install usb with rufus.

I think they will make a simple calculation; What is going to cost more: The bad PR of nolonger updating 240 million pc’s, or accepting that a small portion of your users does not have tpm?

They haven’t stopped advanced users from installing win11 on older hardware so far. So no loss there. I also doubt they lose enterprise money if they allow win10 to upgrade regardless, as tpm is now well entrenched as the default on new hardware.

This info needs to be more widespread.

New users will look at lemmy.world before they create an account. They will choose to join after seeing threads posts and comments on the front page. The default settings will keep them looking at threads untill they figure out they can block it. But when they do, they realise that 90% of all posts and comments came from threads, and they just disabled most of the content.

I would be ok with an opt-in mechanism, where the default settings and the anonymous settings disable threads content, but you can unblock them.