@Jose_A_Alonso Hmm, interesting. To me, the benchmarks especially so. If it was only for normalisation, it's pretty clear that NbE is and always will be the winner. But if I understand correctly, NbE has limits; for example it would not be so simple to implement a transformation pass like GHC's Simplifier using NbE, where you apply peephole optimisations such as case-of-case, inlining etc. to the program while traversing it. I wonder if @AndrasKovacs has tried NbE for such a pass?
「 CakeML is a functional programming language and an ecosystem of proofs and tools built around the language. The ecosystem includes a proven-correct compiler that can bootstrap itself 」
fp-ts brought advanced #FunctionalProgramming to #TypeScript. Now a related project implementing an effect system for TypeScript (effect-ts) seems to have gotten a lot of VC money. Interesting... Docs look very polished, not sure how they will make money though.
@feld@abnv Okay, let me try to explain my thinking a bit -
A caveat - if I were to make this chart today, I would swap the positions of Erlang and Rust.
Keeping that in mind, I made this chart so that each axis broadly makes sense. Lawful languages tend to stick to rules and the only surprises are usually how much of a stickler for rules they are. Chaotic languages on the other hand, love their quirks / special cases. "Good" languages are usually languages with academic backgrounds, whereas "Evil" languages sacrifice some ideals for practicality.
With those definitions, the alignment for each language broadly makes sense to me. Lisp for example, is an academic language, yet a hackers tool, quirky, yet very regular. Hence true neutral.
#FunctionalProgramming will make you build better software, regardless of language. Some understated effects:
‣ Prefer params to global state
‣ Prefer data pipelines to fragile state mutation
‣ Prefer clear responsibilities for components
‣ Make dangerous side effects visible.
I'm looking for recent books or up-to-date text on #FunctionalProgramming with PHP. #PHP is changing rapidly and all the books I see are nearly a decade old. Any good recommendations? #FP
@Crell I did look at yours, but Stack Overflow errors have taught me the hard way that PHP has changed a lot recently. Isn't much of PHP different since you wrote the book?
@worldsendless There's a number of very cool improvements to the language, yes. Whether they impact the FP story is the question.
Enums are new. Readonly makes value objects easier, as does constructor promotion. The mixed type is nice in a few cases. Union types don't matter for FP, and neither do attributes.
The core FP story hasn't really changed in the last 4 years. Had any of the FP based RFCs I submitted passed, that would be different, but... They all got blocked.
「 The biggest reason I love Elm is that it changed my perspective on programming.
As someone who aspires to be a code craftsman, this is the biggest reason to learn Elm. Crazy story - I tried really hard to bring the Elm architecture with me when I started a project in Rust. It really makes you think about what goes into building deterministic systems 」 https://sufiyan.substack.com/p/why-i-love-elm?r=aaxsb&s=w
:thinkerguns: Why is Elm such a delightful programming language?
➥ Marcio Frayze
「 Elm is a pure functional programming language with immutable data structure, soundness type system, currying, and blah blah blah. But instead, the author preferred to highlight his real intention: to create a safe language that web developers feel pleasure in using it. The rest is a consequence of that! 」 https://dev.to/marciofrayze/why-is-elm-such-a-delightful-programming-language-2em8
I learned #FunctionalProgramming to escape the imperative programming languages, which in turn got me interested into #Compilers and #ProgrammingLanguages. Turns out, most of the real-world compilers are written in C and C++, so here I am back at square one.
After years of avoiding it for decades, I taught myself #Cpp in the last couple of weeks. So anyway, does anyone want me to write a series of #blog posts about making a #Lisp interpreter (https://github.com/kanaka/mal) in C++?
@abnv I am voting yes for the blog posts! The other irony of sufficiently high level functional programming is that you want it to seem imperative on the surface! Like cursors in reagent/cljs letting you imagine you have variables/registers even though it’s a single atom under the covers. I am sure the Haskell lens paradigm from whence cursors came is even more elegant. Monadic even.
I may have got a bit carried away writing a blog post presenting both a really practical way with a nice developer experience of handling asynchronous operations that might fail in TypeScript... and a "write your own monad in TypeScript" tutorial.
If you're interested in #FunctionalProgramming, #typescript, or both - please share. I think the techniques in this post can really make writing TS a lot more enjoyable, and the results more reliable.
This chapter took me a while and I need to reimplement it again. I think translate-codon should use a map . Having to wrap codons with codon-strings does not feel right , but I don't understand what partition returns.
Not sure about throw-away maybe a recursion is too much for this ? Maybe there are other built-ins I can use.
Using map more than once does not feel right. I think processing one rna a time would make it more simple.
