It's not though. Programming languages, like assembly before them, are deterministic. If you run the same C code again the same environment, it will do the same thing, and altering the code will alter the behaviour correspondingly. It's possible to reason about it. The same does not apply to LLMs. You can't reason about their behavior, when means you can't build anything non-trivial with them. All that is mentioned in the article.
What do you mean? That's literally just using the service as intended.
Why do you feel the need to install an app for a coffee shop?
And the conditions are still better than what the collective agreements would require?
That one was always available though
That said, many of our clients still don’t support utf-8 so its all ascii and non-latin alphabets are screwed.
Ah, yes, I heard about that sort of thing. Some bank getting a GDPR complaint because they couldn't correct the spelling of someone's name, because their system uses EBCDIC.
I assume you're gonna back that up with a double blind ABX test?
Rust does. But you get:
error: unknown start of token: \u{37e}
--> test.rs:2:30
|
2 | println!("Hello, World!");
| ^
|
help: Unicode character ';' (Greek Question Mark) looks like ';' (Semicolon), but it is not
|
2 | println!("Hello, World!");
That doesn't even make any sense, since it's not an absolute scale
And that's when they tell you what you did wrong. Sometimes they'll reject the password without telling you why, because of some rule they didn't list. For example, I set a password in a parking app (Flowbird) which had an unmentioned restriction against spaces and Swedish letters (dispite targeting the Swedish market). Also, it lets you set a fairly long password, but when you try to log in on their webpage they've set maxlength="32" on the password field. So if you have a longer password you have to edit the DOM and remove that attribute to log in.
LaggyKar
0 post score0 comment score
Reddit does have RSS feeds