They absolutely do accept then discard when it's flagged as spam above a certain confidence threshold (below that it "only" ends up in the spam folder).
I suspect because it's hard to differentiate between ones that actually respect the consumer vs ones that only say so, but are actually lying to your face.
That and not respecting the consumer is more profitable in the short term (only!), which means more marketing money, buying out other brands, lobbying to increase the barrier for entry, et cetera.
Plurality ("first past the post") voting systems always converge to a two-party system. There's even a theorem saying so, though of course the real world isn't always so polite as to behave the way the mathematics tells it to. Countries with better electoral systems don't so consistently seem to converge to a two-party system.
Caveat: it's per seat. Each seat gets two parties to pick from. There can be more than two parties in the government - some other force caused the US to agree on the same two parties in every seat.
When one party is secure in a seat and the second is weak, other parties can challenge each other for second place. For example libertarians could try to beat republicans in a place where republicans do poorly.
Little did they know that the UK effectively already had Norway's status and then some, what with all the special privileges they were granted in the EU.
(The British fisheries industry actually largely suffered due to Brexit, as British people don’t eat much fish, especially the fish available around Britain, and the industry was largely dependent on exports. But it’s the thought that counts, I suppose.)
Vectors & multidimesional arrays are something I'm 100% adding to my language's core.
It kind of started with vectors as the very first feature (I was sick & tired of libraries reinventing their own `Point`/`VectorN` in incompatible ways).
I know it's not the only problem (but it is IMO the main one), but this is why I'm a proponent of allowing operator overloading in languages.
Yes, you can't tell at a glance if `+` really still does what it should, but I find that problem no different from a library mis-naming a function and/or said function having strange side-effects.
`+` should do addition, period. No, not even concatenation if possible (I do find the lack of a separate concatenation operator to be a language flaw --- that said, I understand the use of `+` for concat in libraries targeting languages that offer no alternative).
I think the abuse (especially in C++ ... seriously, allowing overloading of the comma operator? --- and <iostream> working via bit-shifting streams by ${some_string} bits) gave everyone a bad taste and they kind of threw out the baby with the bathwater.
php has a separate `.` operator that concatenate and you get an error if you try to do it with a `+`. That's indeed better but most of the time you concatenate with `sprintf` anyway
Yes, and it's a surprising good part about PHP (a language that otherwise has an enormous collection of warts, to put it mildly).
I feel like the more dynamic and/or weakly-typed the language is, the more important it is to have a separate concat operator.
The worst ones being weakly-typed and dynamic. Consider `'5' + '10'` in JavaScript vs `'5' - '10'`.
I also very much dislike Python's `+` for concat, but at least it's more strongly typed.
PHP, Lua, and Erlang are three examples of dynamically-typed languages with separate concat operators (`.`, `..`, `++`; respectively), and they all are better for it.
That said, even statically-typed languages benefit greatly from it. Maybe if C++ had a concat operator, it'd never end up abusing `<<` for writing to a stream (yes, there's no opposite for reading, but maybe they wouldn't end up doing that in this case).
For example, D uses `~` in infix for concat. Even UnrealScript, a 1990s game-engine-specific language (which tend to be a mess in general) did this right (it uses `$` or `@` --- with `a @ b` being equivalent to `a $ " " $ b`, IIRC).
I shouldn't undersell it quite as much as I did, the original SSL concept comes from Taher Elgamal who was ex-RSA and had published the cryptosystem named after him. So it's not really true that there aren't any cryptographers in the room. However more importantly what TLS (and earlier SSL) wants to do is extremely hard and once Javascript comes into the picture it's ludicrously harder for this to deliver security than basically any system ordinary people have used. Several "But obviously I would never do that" scenarios you'd learn about in a cryptography class like "What if your adversary can control part of the messages to be encrypted?" or "What if your adversary can force you to transmit the same exact message thousands or millions of times?" are routine requirements of security for HTTPS because of how the Web works.
And for SSL in particular why would math people (which is what cryptographers are) even be interested? 30+ Years Ago Tim's hypermedia system is just a toy and while its name, "World Wide Web" does sound like a big deal it's not actually important to your everyday life. If you live in a big city and it has a "web page" on Tim's system it's probably knocked together by some IT nerd who works for the city and the actual local government have no idea what a "web page" even is.
Probably by the time TLS 1.2 shipped, the relevant IETF Working Group (also named TLS) could have reached out and asked cryptography researchers to help first and got some engagement because it's obvious this is a big deal, but that didn't happen until TLS 1.3
I really hate the whole thing about companies promoting using LLMs to change one-liner emails into this long multi-paragraph thing that ends up saying almost nothing ... just wasting everyone's time in reading them (with an extra sprinkling of hallucinations).
LLMs have created more billable hours for me as an attorney because the LLMs convince the client that they need to know more about irrelevant issues, how specific statutes may apply, and other such things. They may ask about specific procedural issues that they would otherwise have no idea about that I then need to explain in greater detail. It reliably bloats things that would be a .1 into .5 or more.
>They may ask about specific procedural issues that they would otherwise have no idea about that I then need to explain in greater detail.
My favorite part about LLMs is that their insufficiency as legal aids (Aides? Aids.) seems to be slowly cluing-in the general public as to how Byzantine and "inside baseball" our legal system has become. (This is a bad thing.)
It's a big part of why I'm strongly opposed to common-law systems (as opposed to civil law). All the case law, all of it becomes, well, law. And then you get the whole "legislating from the bench" critique, which, while valid critique, is only a big problem because it's a common-law system.
Yes, I realize many (most?) legal systems are actually hybrid, but they do tend to err pretty strongly into one direction or another.
reply