You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's nice to see people similar to myself online, and you seem like a kindred spirit, so to speak.
Forgive my bluntness, but I think you should just cancel this BTree in favor of my sorted-btree library. Also, I see you're also concerned about AGI risks. I've been writing a story about AGI but have been having trouble completing it! Let me know if you have any thoughts.
Also, I see you've been working on a system of Binary Buffers, and I have created multiple extensible/flexible binary formats in my career. One of my efforts is open source and part of my Enhanced C# codebase, specifically a library called SyncLib which has been over 90% complete for the last two years -- I haven't been able to finish the first version of it because I've been too busy as a CTO trying to earn enough money to create a project to improve public fact-checking and epistemology. But I digress. I would like to share my design for a "standard" binary format. When I look at your library's README, I can't understand very much about it - like, what kind of format is it? Is it type-safe when reading? Does it store a schema or field IDs together with the data, like JSON or protocol buffers do, or is the schema stored separately for higher efficiency (like a database)? Anyway, most likely your binary format is "higher-level" than mine, because mine stores no schema information at all. However my format is designed to achieve very high performance and has some other nice properties, so it could potentially be used as a basis for yours, if you are interested. Edit: In other words, you could take the format of my core data types like "integer" and use those in your format, while still keeping whatever system of schemas you are already using. So have a look at the spec if that sounds interesting. Edit: please scroll down to "Data type interchangeability" and "Data encodings" for information about the "meat" of the format.
Also I have mulitipleblogs and stuff, etc, as you'd expect, but I mostly stopped writing because nobody was reading any of it. So good luck with that YouTube channel! I've subscribed!
The text was updated successfully, but these errors were encountered:
It's nice to see people similar to myself online, and you seem like a kindred spirit, so to speak.
Forgive my bluntness, but I think you should just cancel this BTree in favor of my sorted-btree library. Also, I see you're also concerned about AGI risks. I've been writing a story about AGI but have been having trouble completing it! Let me know if you have any thoughts.
Also, I see you've been working on a system of Binary Buffers, and I have created multiple extensible/flexible binary formats in my career. One of my efforts is open source and part of my Enhanced C# codebase, specifically a library called SyncLib which has been over 90% complete for the last two years -- I haven't been able to finish the first version of it because I've been too busy as a CTO trying to earn enough money to create a project to improve public fact-checking and epistemology. But I digress. I would like to share my design for a "standard" binary format. When I look at your library's README, I can't understand very much about it - like, what kind of format is it? Is it type-safe when reading? Does it store a schema or field IDs together with the data, like JSON or protocol buffers do, or is the schema stored separately for higher efficiency (like a database)? Anyway, most likely your binary format is "higher-level" than mine, because mine stores no schema information at all. However my format is designed to achieve very high performance and has some other nice properties, so it could potentially be used as a basis for yours, if you are interested. Edit: In other words, you could take the format of my core data types like "integer" and use those in your format, while still keeping whatever system of schemas you are already using. So have a look at the spec if that sounds interesting. Edit: please scroll down to "Data type interchangeability" and "Data encodings" for information about the "meat" of the format.
Also I have mulitiple blogs and stuff, etc, as you'd expect, but I mostly stopped writing because nobody was reading any of it. So good luck with that YouTube channel! I've subscribed!
The text was updated successfully, but these errors were encountered: