labiak · May 19, 2022 15:30
diff --git a/Metaprogramming in JavaScript b/Metaprogramming in JavaScript
 As I as I could see in recent years, dive more into JavaScript backend and frontend programming,
 JavaScript is a simple hierarchy composition language, so it best feet for metaprogramming.
 People don't like JS for dynamic typing and absence control of state and strict validation.
 We have flexible type checking instrument with declarative JSON configuration - jsonschema.
 Based of this instrument we can build API gateways using Swagger declarations that is extension of jsonschema.
 I propose a radically different approach to changing the state of an object and I understand that it require
 different way of thinking in way of transactions, not in way in integral algorythms.
 Instead of a microservice, I suggest using a simpler notion - an enzyme
	As I as I could see in recent years, dive more into JavaScript backend and frontend programming,
	JavaScript is a simple hierarchy composition language, so it best feet for metaprogramming.
	People don't like JS for dynamic typing and absence control of state and strict validation.
	We have flexible type checking instrument with declarative JSON configuration - jsonschema.
	Based of this instrument we can build API gateways using Swagger declarations that is extension of jsonschema.
	I propose a radically different approach to changing the state of an object and I understand that it require
	different way of thinking in way of transactions, not in way in integral algorythms.
	Instead of a microservice, I suggest using a simpler notion - an enzyme