Using multiple vehicles also increase maintenance. It totally makes sense to use the right tool. You might not want to learn how to use a screw driver instead of a hammer but both have their use.
React isn't 100kb when compressed (which is how 99% of websites deliver it to clients). IIRC it's 7.4kb when minified and 2.4k when minified+gzipped. That's smaller than typically "small" frameworks like htmx.
In fact, Backbone is 17.7kb minified+g zipped. So I guess other frameworks make less sense than react?
Most people do not understand any of the authorizations they give to apps and don't want to have to understand it. They will be interested in it only after they got burned.
They just want a thing that "works and do x, y and z" without having to worry about it.
I think the problem is that big corp got them used to easy security because nobody cared before but now that security is getting harder, big corp has no choice but to gave a sense of security they promised but cannot give anymore.
So you had to learn IPv6 the same way you learned IPv4. The question is: was it harder ?
It seems you wanted to know IPv6 without learning it because you thought it would be the same as IPv4.
And yes the Free boxes are hard to work with if you don't want to mess with vlan and still have TV services.
I think the main difference is that when I learned IPv4, pure-v4 was sufficient. Today, you can't run a pure-v6 network; you have to deal with both. The closest you can get is NAT64, which 1. doesn't always work, and 2. is still annoying to manage. (Which sucks, because doing just v6 would be nice)
I think this misses the point. An IPv4-only home network has a lot of benefits, simplifying whatever you to in it which relies on IP addresses which you'll have to handle manually in code and databases.
His scenario is really a PITA, where he's basically forced to migrate to IPv6 only because of IPTV. There might have been a solution by creating an IPv6-only VLAN just for the TV, while keeping the rest at legacy, but it's not really trivial.
IPTV with Deutsche Telekom is also a pain, because they feed it in a separate VLAN and the routers and switches need to handle IGMP messages properly (IGMP proxy, IGMP snooping).
On the contrary, I would say that this is a garage you rent on a public space. The internet is open and I can do requests to any server. If you don't want your system to answer me, make sure it does not.
If I am in front of an ATM on the public street, it doesn't give me money without authorization. Make sure your server does the same.
Streets are generally open. My house is on a public street - that doesn't entitle anyone to attempt to operate my garage door, let alone exploit a security vulnerability in its software to gain access. That's just trespassing.
If the encryption info is derived from the password it can be done without visual encryption keys for the user. It is the case with Firefox Sync. They have no way to recover the data if you forget the password.
