Java World -v1.0
https://www.jrebel.com/blog/java-collections-cheat-sheet
Python World - v2.0
https://jakevdp.github.io/PythonDataScienceHandbook/03.02-data-indexing-and-selection.html
Microsoft World -v3.0
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-clear-collect-clearcollect
Why did we start from era of PowerFx v3.0
[5]
Transactional bots are like goldfish – they don’t remember previous interactions with the user and can’t maintain extended dialogue with the user.
Conversational bots are like elephants – they maintain the state of the conversation and carry information between turns of the conversation.
Larry Wall (of Google) highlights the following axes of language design in his survey:...
- Binding: Early or Late?
- Dispatch: Single or Multiple?
- Evaluation: Eager or Lazy?
- Typology: Eager or Lazy?
- Structures: Limited or Rich?
- Symbolic or Wordy?
- Compile Time or Run Time?
- Declarational or Operational?
- Classes: Immutable or Mutable?
- Class-based or Prototype-based?
- Passive data, global consistency or Active data, local consistency?
- Encapsulatation: by class? by time? by OS constructs? by GUI elements?
- Scoping: Syntactic, Semantic, or Pragmatic?
The reason why dynamic languages like Perl, Python, and PHP are so important is key to understanding the paradigm shift. Unlike applications from the previous paradigm, web applications are not released in one to three year cycles. They are updated every day, sometimes every hour. Rather than being finished paintings, they are sketches, continually being redrawn in response to new data...
In my talk, I compared web applications to Von Kempelen's famous hoax, the mechanical Turk, a 1770 mechanical chess playing machine with a man hidden inside. Web applications aren't a hoax, but like the mechanical Turk, they do have a programmer inside. And that programmer is sketching away madly
