21–30 of 34 posts
A similar tech is flatbuffers: https://github.com/google/flatbuffers
I've done this in Java to do cache aware reading to pretty great success.
So, I have to check that libraries don't do this if I am to rely on the idea that Julia offers safety?
if that worries you, I wouldn't look under the covers of almost any database you run, nor network stack you have. Graphics card drivers are WAY out. File systems too. Julia offers as much safety as most languages. You would be hard pressed to find a language which doesn't let you pull something like this. Julia wouldn't solve the 2 languages problem if there was a lot of things you would have to drop back to C to do.…
A similar tech is flatbuffers: https://github.com/google/flatbuffers
Flatbuffers is pretty great, one side benefit of these types of technologies is you can also use them to structure your memory accesses. I've done this in Java to do cache aware reading to pretty great success.
Earlier quoted context omitted.
Flatbuffers is pretty great, one side benefit of these types of technologies is you can also use them to structure your memory accesses. I've done this in Java to do cache aware reading to pretty great success.
Do you mind elaborating?
can someone explain to me why is this on the homepage? Not being sarcastic. I genuinely want to know why is Zero-copy deserialization in Julia relevant to most of hacker new's commmunity
Earlier quoted context omitted.
if that worries you, I wouldn't look under the covers of almost any database you run, nor network stack you have. Graphics card drivers are WAY out. File systems too. Julia offers as much safety as most languages. You would be hard pressed to find a language which doesn't let you pull something like this. Julia wouldn't solve the 2 languages problem if there was a lot of things you would have to drop back to C to do.…
Point taken. It would be nice to be able to query my code base to see if unsafe methods have been used (and where) in the executable.