I suppose you're not a native English speaker, btw: besides the dubious statement, probably "executor" is the word you wanted to use.

And the article doesn't even appear in their homepage.

And the author is somebody from a company that "provides you with quality RAM"

Flagged. How did this even get to HN ?

But, what bars are clearly off? I couldn't spot any.

Only the 2021 spec for usb pd supports 36v (common bike battery voltage) and more than 100W delivery. My bosch ebike charges at 36v 4A.

I also think that a small usb c connector could easily break when used in an ebike. But this should not prevent standardizing a “bigger usb c” to be used in ebikes.

> We'll support users and other third parties to detect Claude’s marks

This is the part that I fear most. What happens with false positives? Will I need to change arbitrary parts of my text if they are flagged as AI generated? Will I be forced to add mistakes?

And then, since LLMs are trained on existing, human-written, quality content, it may be that well-written text gets accidentally flagged more often?

And, if all the providers do this, and they use different watermarks, will I be forced to change things at random until I get a negative from all of those?

I very much think this will yield the wrong signal. There were already some academic plagiarism checkers around that would return false positives, and were blindly trusted by teachers and professors. I suppose AI checkers are all around now, and there will be more of those.

Proofreading is one of the best uses of LLMs that I can think about - I still write my text, then an LLM fixes some of my "errors" since I'm not a native speaker. It usually improves clarity. But now I risk my text to be classified as AI written with potentially bad outcomes.

I don't know whether I should blame the EU, though :-)

Why complain about those, then?

Diy is still possible. Looks like nas is becoming more specialized.

I feel that offsites work best when you let people interact on their own schedule, pace and topics. Trying to force hands via a lot of activities can kind of backfire.

Relationships happen. They are not programmatically built.

That's the problem. That's the risk that few (if any) hyperscalers want to take.

Of course, the C -> unsafe Rust -> safe Rust is more likely to happen than just going straight to (mostly) safe Rust (I doubt a 100% safe dbms would make sense).

Comments URL: https://news.ycombinator.com/item?id=48747267

Points: 2

# Comments: 1

This is a false equivalence.

A compiler is a predictable, testable, deterministic piece of software.

An LLM is not.

Sure, all abstractions leak; so, at some point in time, for some reason, you may need to check its compiled code ( cough cough gcc 2.96 ). But, if today your code compiles properly, it will properly compile tomorrow as well.

what is on the kindle will stay and keep working.

if you reset the kindle, DRMed content won't work anymore.

Did I claim something different? I just didn’t use that feature on other OSes.

I'm not sure what the author really wants to say. mmap is available in many languages (e.g. Python) on Linux (and many other *nix I suppose). C provides you with raw memory access, so using mmap is sort-of-convenient for this use case.

But if you use Python then, yes, you'll need a bytearray, because Python doesn't give you raw access to such memory - and I'm not sure you'd want to mmap a PyObject anyway?

Then, writing and reading this kind of raw memory can be kind of dangerous and non-portable - I'm not really sure that the pickle analogy even makes sense. I very much suppose (I've never tried) that if you mmap-read malicious data in C, a vulnerability would be _quite_ easy to exploit.