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
After a call with Alvarado Cuihtlauac, I propose an index of the cookbook, the way I think about it. This index identifies some recipes that are already written, and others that I could write. It may be completed (I may lack some imagination)
I propose to review this index. How it would become with a new level of hierarchy ? What aggregation should be done, what decomposition should be done ?
I should add that the decomposition of compression (separing ZIP and Gzip) is motivated by what a reader would be interesting with... usually only Gzip or only ZIP (in a same way merging XML and JSON recipes would not be adequate). On the opposite, my Caqti/ppx_rapper article is large, but a reader would be more likely interested in all the queries. I think this guideline could be used to determine how to split articles.
Command line
Sys (Stdlib)
Cmdline
Compression
ZIP Decompression
Gzip Decompression
ZIP Compression
Gzip Compression
Concurrency
Lwt [Perhaps we should add Mutex and something like this... in a new article or in the existing article]
Eio [A decomposition should be needed : spawning task, mutex, etc.]
Fiber (?)
Parmap (?)
Cryptography
X509, Signature/vérif [signing/verifying needs reading a certificate... it is difficult to separate X509 and signature/verification]
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
After a call with Alvarado Cuihtlauac, I propose an index of the cookbook, the way I think about it. This index identifies some recipes that are already written, and others that I could write. It may be completed (I may lack some imagination)
I propose to review this index. How it would become with a new level of hierarchy ? What aggregation should be done, what decomposition should be done ?
I should add that the decomposition of compression (separing ZIP and Gzip) is motivated by what a reader would be interesting with... usually only Gzip or only ZIP (in a same way merging XML and JSON recipes would not be adequate). On the opposite, my Caqti/ppx_rapper article is large, but a reader would be more likely interested in all the queries. I think this guideline could be used to determine how to split articles.
Command line
Compression
Concurrency
Cryptography
Databases
Date & Time
Debugging
utopstatements]Encoding
File system
Garbage collector
Random numbers
Hash table et maps
(NoHashtblStdlibonly recipes)(NoMapStdlibonly recipes)(NoSetsStdlibonly recipes)Maths
Netwotking
Operating system
Sorting
comparefunction]Text processing
ASCII Text processing(NoStdlibonly recipes)Web programming
dunesnippet because of a specific preprocessor... dream_html could be preferred]Graphics
Messaging
Beta Was this translation helpful? Give feedback.
All reactions