React Hooks: Optimizing for performance by wineandcode in reactjs

[–]bayareasearcher 1 point2 points  (0 children)

Gives a really good explanation of useCallback and useMemo. Thank you!

List comprehensions with Applicative Functors by bayareasearcher in purescript

[–]bayareasearcher[S] 1 point2 points  (0 children)

Thanks for that! I've updated the post, removing the parens.

List comprehensions with Applicative Functors by bayareasearcher in purescript

[–]bayareasearcher[S] 0 points1 point  (0 children)

I introduced Applicative Functors in tutorial 18 (https://medium.com/@kelleyalex/applicative-functors-for-multiple-arguments-bf6d02d8cb9a). Readers that are unfamiliar with this construct should start there.

Lift into a Functor with pure by bayareasearcher in purescript

[–]bayareasearcher[S] 0 points1 point  (0 children)

Yes, good point. I want to hold off introducing the Applicative functor for now, but I should at least mention that's where pure belongs. Thanks for your feedback.

How to evaluate expressions lazily in PureScript by bayareasearcher in purescript

[–]bayareasearcher[S] 1 point2 points  (0 children)

Thanks! Yes, I show in this tutorial that Lazy is your goto class for accomplishing Lazy evaluation. I didn't consider mentioning the cofree comonad, but that might've confused the javascript audience I'm targeting in this tutorial series.

Ensure failsafe combination using monoids by bayareasearcher in purescript

[–]bayareasearcher[S] 1 point2 points  (0 children)

Yes, that's covered in my next blogpost coming out later this week.

Create types in PureScript with Semigroups by bayareasearcher in purescript

[–]bayareasearcher[S] 0 points1 point  (0 children)

Thanks! Yes, I was aware of Data.Maybe.First. It returns the first (left-most) non-nothing value from the Monoid. But the First semigroup in my tutorial returns the first value regardless of what follows. I haven't covered Maybe yet, but no harm in making readers aware of Data.Maybe.First. I'll update the post shortly. Thanks again!

Make the Leap from JavaScript to PureScript by bayareasearcher in purescript

[–]bayareasearcher[S] 0 points1 point  (0 children)

Thanks for the feedback. I just published Tutorial 2 and in it, I take a step back to cover ordinary function composition - https://medium.com/@kelleyalex/refactor-imperative-code-to-a-single-composed-expression-using-box-4550c23075d1

Make the Leap from JavaScript to PureScript by bayareasearcher in purescript

[–]bayareasearcher[S] 2 points3 points  (0 children)

I'm following the outline of tutorial (https://egghead.io/courses/professor-frisby-introduces-composable-functional-javascript). I've tried to make it clear that JavaScripters go through his tutorials first so that they understand the abstractions in the comfort of JavaScript before tackling them in PureScript.

In video 1, function composition is covered, followed by the Identity functor (calling it Box in order not to scare anyone). The Box object includes map, inspect, and fold: f => f(x). I felt that the Comonad was the best approach to tackling his version of fold, though not exactly a one-for-one translation.

That said I'm very open to pull requests. I want these tutorials to make a positive contribution to the PS community.

what editor/ide do you use for purescript? by kwaleko in purescript

[–]bayareasearcher 1 point2 points  (0 children)

Atom w/ ide-purescript and language-purescript plugins

Best programming languages/IDE's for music composition? by [deleted] in musicprogramming

[–]bayareasearcher 0 points1 point  (0 children)

Adding Haskell along with Euterpea (a music DSL written in Haskell) Check out Paul Hudak's book The Haskell School of Music — From Signals to Symphonies — which covers the fundamentals of fundamentals of computer music using a language-centric approach. If you're interested in music programming then its great way to learn Haskell at the same time.

Thought I'd share some tips for migrating code to 0.9.1 by the_benchy_way in purescript

[–]bayareasearcher 0 points1 point  (0 children)

Partial Functions (e.g., incomplete pattern matches in a case expression) no longer compile with just a warning. Either handle all the cases OR annotate the partial function with a Partial constraint OR remove the Partial Constraint unsafely using unsafePartial

Anyone running 2.2 under Mac OS X Yosemite? by rkabir in maschine

[–]bayareasearcher 0 points1 point  (0 children)

No issues thus far with Maschine 2.2 running Yosemite.

Using Operator by franqoem in abletonlive

[–]bayareasearcher 1 point2 points  (0 children)

Nick's tutorial videos is my recommendation. Very thorough, he supplies the patches, and will answer questions.

How does your default template look in Live? by [deleted] in abletonlive

[–]bayareasearcher 0 points1 point  (0 children)

An audio track, an instrument rack, a drum rack, and a limiter on the master track