Threads for stevenxl

  1. 1

    It always gives me joy to read about a successful monolith powered by Haskell + Postgres. It’s such a pleasant experience to develop using that approach, it feels like cheating.

    1. 1

      @enobayram - we’re hiring for a Staff Engineer if you are interested in working with us!

    1. 3

      I loved this post. Thank you very much Rebecca. I’m looking forward to the book. I would buy it now on beta but it seems that beta only includes the eBooks. I’m a dead-tree kind of person. I’ll keep my eye out for it!

      1. 1

        Fantastic post.i had to email the author to let him know how good it was.

        1. 3

          Incredible article. This is going to save me so much time, being new to redux and all.

          1. 3

            I’ll save you even more!

            Don’t use Redux. Write your own little framework where you pass messages through something like a stream that leads to something modifying your “state store” and then something rendering your app.

            Redux is simple in principle, but somehow accumulates massive complexity and reams of indirection around it. Reducers are too boilerplatey, sometimes you do want nested state, and you want more control over when/how rendering happens.

            Avoid all the dependencies you can. Even react-router.

          1. 2

            This looks great. I haven’t looked at the source code but are the paths human curated or an algo of some sort? I’m guessing with the amount of topics, it’s unlikely that a person has individually looked at each topic.

            I found spacevim throuhgh your search engine, so that’s pretty awesome.

            1. 2

              Thank you Steve. Actually all maps were human curated by me up until this point.

              However we are moving to a model where anyone can contribute by sending pull requests similar to GitHub awesome lists. We are also moving to D3.js render for smoother viewing and exploring experience.

              I hope you will enjoy using the search. It should be getting better and better every day especially with the help of community. :)

            1. 3

              It’s almost like a pipeline with structured exception handling… :P

              1. 9

                Those are not exceptions though. It does this on return values that are specific tuples.

                1. 1

                  Point. I meant in the general “huh, crap, that function didn’t take the happy path with the supplied arguments path” rather than literal PL construct of exceptions. My apologies. :)

                2. 2

                  It’s almost like a less thought out and less useful attempt at expressing monads.