I’m still bummed that Python took this direction. Maybe introducing new keywords into the language for event loop concurrency was Python’s way of satisfying “explicit is better than implicit” but i can’s shake the feeling that callback passing and generator coroutines are a fad that is complex enough to occupy the imagination of a generation of programmers while offering little benefit compared to green threads.
But you still seem to be in agreement that the implementation of the language has a neccesary overhead... printing the operator that indicates code would require another escape sequence, and the overhead of the operator to identify code would mean that some compressible strings dont benefit from compression.
Im tempted to debate this... in any programming language you need to use some space to differentiate a literal from code to be executed. So, according to Kolmogorov complexity, wouldn’t the shortest program to print a random number (or 0) be larger than that number?
Blockchains will allow people to collaborate on training a shared model. At somepoint it’ll be able to predict what it should learn next better than the people training it.
Proof of work blockchains arent solving anything here, theyre a step further in the “do not trust” direction. However i think consortium chains may have potential.
The author talks about a piece of software as if it were a closed system, where disorder would inevitably increase. This is not the case, disorder in software can be decreased by doing work. However, the business requirements will inevitably become more complex over time, and there will come a point where the cost of adaptation of the software is higher than the cost of starting over with a design that better accomodates the current requirements. Inability to adapt is observed in ageing organisms also.
It seems like this comment is a little understated. Maybe the commenter could think more about how to catch the attention if the persons he/she wishes to target. /s
I havn't looked at the new video series, but when I was trying to get started with TLA+ using the Eclipse toolbox, i got stuck trying to define a behaviour spec for the model checker. Do you know of any good documentation for this? Thanks