react-grid-layout VS missionary

You can find additional information about the React-Grid-Layout in the repository and documentation.

This is react-grid-layout with some custom logic https://github.com/react-grid-layout/react-grid-layout

react-grid-layout looks like a good candidate, but it seems like it lacks a way to customize/add rules for positioning elements to prevent "stacks" of elements. Imagine a user models a brick wall and you want to prevent users from stacking bricks above each other (prevent bricks stack bond and allow something like running bond brick pattern)

I was looking to build a somewhat similar project with react and react grid layout.

Would it be possible to prototype something like this in figma? http://react-grid-layout.github.io/react-grid-layout/examples/0-showcase.html

react-grid-layout A draggable and resizable grid layout with responsive breakpoints, for React.

A lot of projects seem to like: https://github.com/react-grid-layout/react-grid-layout

I’ve done that before using react grid layout (https://github.com/react-grid-layout/react-grid-layout) to allow for moving and resizing components, and then a lot of custom code. Having a well thought architecture makes a lot of difference there.

I think the reactive query problem is more of a spectrum of tradeoffs, there's a middle ground between "full page refresh on nav" and "refresh all query subscriptions per user per tx". Truly realtime things like chat come from a streaming event source (not a database) and even in a chat app, most of the information coordinates on a page is slow moving. So really this is about regaining control over concurrent data flow so we can sample different views at different speeds. See technologies like https://github.com/leonoel/missionary.

I wonder if anyone can compare these to missionary?

related: https://github.com/leonoel/missionary

- https://github.com/leonoel/missionary

https://github.com/leonoel/missionary has excellent syntax, it uses a macro to extend regular clojure syntax with monadic join operator – basically turning clojure sexprs into do-notation

I recommend having a look at missionary - it is probably the most essential library in our application. But it depends on what type of application you are building.

Process supervision is what Missionary implements: https://github.com/leonoel/missionary

Agree - mostly the opinions are just dated, in 2005-2012 the pure FP world (especially Scala) was in rough shape but then in 2018 Maybe Not (the really controversial talk about "Maybe Sheep") it didn't seem like he had taken the time to understand haskell. I would love to see how his opinions have evolved since then, in the 2017 interview with fogus he said "If I had more free time, I’d spend it with Haskell". Haskell has especially come a long way in 2018-2022 with the popularization of functional effect systems which are extraordinarily powerful; for example https://github.com/leonoel/missionary (2020-2022) is the best Clojure effect system and is a leap forward over core.async (2013), but that 9 year difference is a lifetime in CS