> but I still get the benefit of noone but me having access to my received emails.
Other than every smtp relay hop and any network tap along the way that could keep a copy. Hope you're encrypting and not worried about the envelope. Email is fundamentally not private. Self-hosting doesn't help all that much (though it may keep it out of certain companies' hands, aside from the emails copied to or sent from that provider)
> I know things are super polarized now, but even 20 years ago, when mentioning a Congressperson regarding a particular social problem, they would specify if he was a Democrat/Republican.
When articles always mention party affiliation, people will judge the politician's behavior based on the affiliation, and not on his actions.
ParamSpec doesn't have the same objective as what they're saying. The sibling comment shows how you can get the proper types in TypeScript and use them as types for other functions. On the other hand, ParamSpec is a hack to properly forward function argument types to decorators.
It’s not my opinion, it’s a statistical fact. Php was a pioneer and it deserves its respect for that. Bit it never was a tool for example to create next kafka with, or at least build some api gateway etc.
Laravel and others “advanced wordpress” use cases is not a “serious software” from technical POV.
> Because it’s a) scripting language b) not even a good one.
> Even if modern versions somehow overcome those limitations - nobody would bet an expensive project while there are plenty of more relevant alternatives
No, b) is absolutely your opinion (how can "LangX is not a good scripting language" be "statistical fact"? Come on.)
a) -- depends on your definition of expensive, but, again, I point to the tons of new (and old) companies choosing python all the time, even if some other language is "better" (for whatever your definition of better is)
We agree that neither PHP nor python would be good fits for building a database or similar. Doesn't make my points wrong.
Your messaging client may helpfully request the url they sent you to show a url preview.
In an email, your client renders the html including img tags (yes, this can be disabled, and may not even be default for most people anymore; it’s still a thing)
Other than every smtp relay hop and any network tap along the way that could keep a copy. Hope you're encrypting and not worried about the envelope. Email is fundamentally not private. Self-hosting doesn't help all that much (though it may keep it out of certain companies' hands, aside from the emails copied to or sent from that provider)