6,148 karma · joined May 1, 2013
It was my introduction to typed FP concepts via this course (Part A) https://www.coursera.org/learn/programming-languages
export const Child2Animation =
Co.Repeat(
Co.Seq([
Co.SetState(Child2.Updaters.Core.a(replaceWith(1)).then(
Child2.Updaters.Core.b(replaceWith("")))),
Co.Wait(250),
Co.For(Range(0, 3))(
_ =>
Co.Seq([
Co.SetState(Child2.Updaters.Core.a(_ => _ * 2)),
Co.Wait(250),
Co.SetState(Child2.Updaters.Core.b(_ => _ + ".")),
Co.Wait(250),
])
)
])
);
> Not only is the code pretty self explanatory.Is it though?
(some-function-name arg1 arg2)
The syntax looks very pretty, and it's very easy on the eyes. I'm excited for this project and its goals.
Nix Doc are horrible but I've found that ChatGPT4 is awesome at troubleshooting Nix issues.
I feel like 90% of the time I run into Nix issues, it's because I decided to do something "Not the Nix way."
This is why SQL has endured for so long.
That mathematical base allows for efficient data manipulation across vast datasets.
To his point that no other languages strive to be spoken like, languages like ruby (and python to a degree )have successfully adopted a natural, english-like syntax, enhancing readability and developer productivity.
Emphasizing procedural over declarative concepts misinterprets SQL's core advantage: expressing complex data relationships and manipulations succinctly. Such perspectives miss the broader utility of making programming languages approachable and efficient for diverse tasks and user backgrounds.
Side rant: I just wish SQL was more composable.
the very occurrence of speculative bubbles, (to be pedantic; where asset prices soar well beyond their intrinsic values and eventually crash) is a strong argument against market efficiency.