> 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)
Not really true, if you have an iPhone, at least. URL previews are loaded on message open. A network request to the url they sent you. They know when you opened it
Previews are generated by the sender. The only network requests for the receiver are to Apple. Quoting from a January 2021 Project Zero blog post⁽¹⁾ on BlastDoor:
As an example, consider what happens when a user sends a link to a website over iMessage. In that case, the sending device will first render a preview of the webpage and collect some metadata about it (such as the title and page description), then pack those fields into an NSKeyedArchiver archive. This archive is then encrypted with a temporary key and uploaded to the iCloud servers. Finally, the link as well as the decryption key are sent to the receiver as part of the iMessage. In order to create a useful user notification about the incoming iMessage, this data has to be processed by the receiver on a 0-click code path. As that again involves a fair amount of complexity, it is also done inside BlastDoor: after receiving the BlastDoor reply from above and realizing that the message contains an attachment, imagent first instructs IMTransferAgent to download and decrypt the iCloud attachment.
Elastic’s own consultants will tell you this …
reply