I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?
Namespaces
We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they’re for, with a type attribute.
In memory message queues
Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.
I reckon we could power a medium sided country if we could generate energy from the programmers despair.
It uses XML-like syntax:
<fun> <name>sum</name> <in> <int>foo</int> <int>bar=0</int> </in> <out><int>foo+bar</int></out> </fun><fun> <name>sum</name> <in> <int> <name>foo</name> </int> <int> <name>bar</name> <default_value> <int>0</int> </default_value> </int> </in> <out> <int> <calculation> <numerical_operation> <operator_plus> <operand> <var>foo</var> </operand> <operand> <var>bar</var> </operand> </operator_plus> </numerical_operation> </calculation> </int> </out> </fun>How did you come up with such a ****ingly stupid syntax?!
It haunts me in my dreams
Thanks, I hate it.
They probably have experience with Spring
Make sure to make ample use of mixed content elements.
<statement><var>bar</var> = <int>0</int></statement>statement: comparison: - kind: libcompare.EQUALS comparators: - foo - bar whentrue: statement: streaming: - kind: libstreams.PRINT content: foo equals bar whenfalse: statement: streaming: - kind: libstreams.PRINT content: foo does not equal barGod I hate it
Lol, I’m sorry
Don’t apologize, it’s beautiful in its horribleness
Can you please link to a medium article on how this will help utilize AI blockchain so i can show it to management on Monday?
I like it, this is clearly very enterprisey and solution focused, but I would like to suggest a couple of amendments if I may?
Namespaces We should make full use of namespaces. Make the structural tags be in a language specific namespace (to be referenced in every function spec, obviously) but change the in an out params to use the parameter name as the tag, namespaced to the function they’re for, with a
typeattribute.In memory message queues Have all function invocations be marshaled as xml documents posted to an in memory message queue. Said documents should use a schema that validates the structure and a function specific schema to validate the types of arguments being passed. Namespace everything.
I reckon we could power a medium sided country if we could generate energy from the programmers despair.